When trying to access content with no permission to access, I just get a white page with "403" in top left corner.
Help?
Backdrop LIVE
April 3-4, 2025
An interactive online event for anyone interested in Backdrop CMS. Everyone is welcome.
Recent topics
Posted 18 hours 24 min ago by RS Snyder (theflightrs) in How-To and Troubleshooting
Posted 2 days 23 hours ago by (Egmund) in How-To and Troubleshooting
Posted 3 days 1 hour ago by (Z4N8r) in How-To and Troubleshooting
Posted 4 days 1 hour ago by (dd123) in How-To and Troubleshooting
Posted 4 days 18 hours ago by (dd123) in How-To and Troubleshooting
Recent comments
Thank you for sharing your final solution. This may be very helpful for future visitors trying to do the same.
Views Accordion as primary navigation
I think this is good enough. Thanks for the surprise, @yorkshirepudding! Here's the CSS i use for future references. (Works on black, very minimal): /* ========== ACCORDION...
Views Accordion as primary navigation
Glad to hear it helped
Views Accordion as primary navigation
On top of that, i turned on "Use group header as the Accordion header" like: Excluded the taxonomy term Now: Another important setting: No autoheight (...
Views Accordion as primary navigation
In the View, under Format, click Settings next to where it will say Views Accordion for you: Set grouping field Nr.1 to be the Taxonomy Term: Name
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.