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.
Thank you, Martin and Olaf! I had a feeling that there might be something out there already :)
I will check all three options (I will look at porting modules) and report back which one...
The Views Watchdog module for Backdrop "extends the Views module and allows to create custom lists of log entries". On Github, there is also a Wiki page with information about available fields,...
Posted5 days 13 hours ago by Olaf Grabienski (Olafski) on:
Hi Irina
I have often wondered this. I have had Log Filter on my list of possible migrations for a while; this uses a JS library to do the filtering. I notice on the project page of this...
Posted5 days 14 hours ago by Martin Price | System Horizons Ltd (yorkshirepudding) on:
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.