Request for an option to turn off all blocks on the 404/403 pages
| Project: | CustomError |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | feature request |
| Priority: | minor |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
A suggestion for you which I hope is useful, but possibly a issue/bug?... not sure....
The 403 and 404 pages are pretty much stripped of all blocks from the common regions. For instance, my left navigation menus are stripped out.
However there seems to be an issue when you set up custom regions in your own theme. Imagine we have a block set to display in a custom region which should only display on page/*/page aliases. If we enter a URL with that structure, but for a node that does not exist... we will get the "Page not found" display, but with the block in that custom region.
Would it be possible for the module to check what regions are available in the current theme and remove all of the found block display regions, or maybe even have a check list within the admin options for the user to specify what blocks/regions still display on 404 or 403 pages? (The later might offer a lot more flexibility).
Many thanks,
Frank
#1
Why don't you just change your block(s) visibility features to NOT display them on the paths named "customererror/4*"?
That way no code needs to be modified anywhere.
#2
You replied too quickly! ;-) ... Was just about to report my balls up :-)...
Well, I really apologise - i've had a case of not doing what I normally preach and "RTFM". I hadn't installed things properly and once sorted, none of the problematic blocks were showing as I reported above. Sorry to waste a feature request post!
Great module which is now working perfect, and apologies again! (Hopefully i'll post something more useful next time!)
Frank