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 20 hours 38 min ago by (onyx) in How-To and Troubleshooting
Posted 23 hours 53 min ago by (Vicki L.) in How-To and Troubleshooting
Posted 1 day 14 hours ago by (robcoppard) in How-To and Troubleshooting
Posted 1 day 14 hours ago by (Egmund) in How-To and Troubleshooting
Posted 2 days 15 hours ago by Pavel (korontari) in How-To and Troubleshooting
Recent comments
The config>active directory has all the json files that were copied when Softaculous did the staging setup, so it isn't empty, and it does exist. I've had problems moving/copying config...
Softaculous Staging issue with Backdrop
Here's an idea on how to use a content type for reviews and associate each "Review" with its own "Target Page". 1. Create a “Review” content type that has a required field “Entity...
How to add a page that authenticated users can add reviews to?
Thanks @Enthusiast for your time and help with this. You've been most helpful. I'm still struggling to create the functionality I'm looking for. I suppose I want something like these forum...
How to add a page that authenticated users can add reviews to?
I've never used Softaculous, but I've seen this problem in my dev settings, when the config directory for a site is empty, but Backdrop database has already been installed. For example, when I...
Softaculous Staging issue with Backdrop
Yes, move the comment_perm to the /modules folder from the /files/coder_upgrade/new
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.