When trying to access content with no permission to access, I just get a white page with "403" in top left corner.
Help?
Weekly office hours
Bring your questions to our weekly virtual office hours, every Wednesday. Everyone is welcome.
Recent topics
Posted 3 days 19 hours ago by (ian) in How-To and Troubleshooting
Posted 4 days 11 hours ago by (clarkac) in How-To and Troubleshooting
Posted 1 week 2 days ago by Erik Wesselius (zilvervos) in Other
Posted 1 week 4 days ago by (Chrys) in How-To and Troubleshooting
Posted 1 week 6 days ago by (Chrys) in How-To and Troubleshooting
Recent comments
Thanks for the response, Herb! Since I posted that I did some more testing and have posted this issue https://github.com/backdrop-contrib/tfa_basic/issues/33 In fact, if both email...
TFA - how to setup fallback options 'per user'
I'll test this tomorrow to see if I can replicate the problem and report back. It's not "per user" so it should be working.
TFA - how to setup fallback options 'per user'
As I work through things I flush the caches after every change I make. As far as I can tell I have the custom module in the correct place (/modules/custom/fix_zero_search) and the file...
custom module not showing up in modules list
If you haven't already, flush all the caches. If it is in the modules folder whether directly or in a custom folder it will show up. If not, something else is wrong with your site; check...
custom module not showing up in modules list
Awful idea! That's not how modules get installed! The number in db indicates the installed state and schema version. You're not supposed to fiddle in the database directly. There's an...
Comments
Barney:
It sounds like you are saying that if a user does not have access to a page, they are getting a blank page with absolutely no content other than a simple "403" message in the upper left hand corner.
I'm assuming that you would prefer that they get a page that has the formatting for the rest of your site, but instead of content they get an sensible "access denied" message.
I don't have a quick answer for you, but a few questions might help:
1) Is the problem the same for unauthenticated users as well as authenticated users (assuming that they are both trying to access pages that they should not have access to)?
2) It sounds to me like the problem is with the layout. Do you have a fall-back (default) layout specified here: /admin/structure/layouts ?
Yes..that's right, but oddly, I restored an earlier database, and noted the issue disappeared ..and then when I restored the latest database, the issue did not return.
Since the restored databases exclude cache tables, I suspect it was cache related.
Thanks a million for helping...very grateful.