Closed (fixed)
Project:
Customerror
Version:
6.x-1.1
Component:
Documentation
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Anonymous (not verified)
Created:
9 Feb 2010 at 16:48 UTC
Updated:
3 Sep 2019 at 10:52 UTC
Jump to comment: Most recent
Comments
Comment #1
el_reverend commentedSecond that. How can I get my blocks to reappear on a 404?
Comment #2
el_reverend commentedNothing since? Did anyone figure out a way to display block on a 'page' that does not exist? Could you use contexts?
Comment #3
el_reverend commentedI have found a solution with the 404block module. It works great with CustomError but needs some configuration if you are using the Context module to display your blocks, etc.
In my case I am using context to display various blocks for various regions, so I have no regular blocks assigned to regions, but this will also display any blocks when a 404 is invoked. Since contexts (at this time) cannot match a php expression I decided to set my block in admin/build/block and only show them when a php function return true.
Here is the code from the 404block module slightly modified:
Now I have my '404' blocks configure the drupal way and all other shown via the context module. Hope this helps others
Comment #4
gisleAs far as I am able to tell, this is not an issue for the Drupal 7 version of this module (i.e. links in the navigation block appear on the custom 403 and 404 pages produced by this module).
However, it may still remain an issue for the Drupal 6 version (I have not tested this version). If so this should be mentioned in the
README.txt, with a reference to the 404 Blocks module as a possible solution.See also: http://drupal.org/node/267163.
Comment #5
gisleNote added to README.txt of 6.x-1.2: https://drupal.org/node/2056029.