I have the following option enabled:
Present login form on access denied (403)

I would like to be able to customize the page title and message that is presented on that page.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

hunmonk’s picture

Status: Active » Closed (won't fix)

although it might seem like making this customizable would be easy and clean, i'm not seeing a way to do it that i'm happy with, so it's going to stay as is.

you can always hack the module to change that if you really want to.

cbutera’s picture

Priority: Normal » Minor

I did this already - but I run the module on 3 sites on one codebase. Just a feature request - not high priority...

ianchan’s picture

How did you hack the module? I'd like to suppress the "Please login message..."

EDIT: found it.. comment out line 828 in logintoboggan.module

jasonawant’s picture

Title: Custom Error Message on Access Denied Page » Custom page title and error message on Access Denied Page
Version: 5.x-1.0 » 7.x-1.4
Assigned: Unassigned » jasonawant
Issue summary: View changes
Status: Closed (won't fix) » Needs review
FileSize
3.54 KB

Hi,

I too needed to customize the 403 page title and error message displayed on the logintoboggan 403 page. There were other ways to do this, but I thought have these options backed in to logintoboggan better organized these customizations.

Here's a patch that provides these options on the settings form, stores them as variables, and uses them appropriately. The patch also includes them in the hook_uninstall() to remove the variables. Feedback welcomed.

This patch is against 7.x-1.4, the version I'm using on a project. I can create another against 7.x-1.x if the maintainers want this feature committed there.

elpino’s picture

I applied the patch manually to latest Dev branch, and works as expected.

sillygwailo’s picture

Status: Needs review » Reviewed & tested by the community

This works great for a client of ours as well.

elpino’s picture

This patch should really be commited. I just spent the last hour trying to figure out how I had implemented this functionality on another site before figuring out it was something I had manually patched. Also not the first time.

Just update patch to latest release.