By newdru on

Any reason why these don't work.

i creatd a node for the default 404 (page not found).

i confirm it exists.

however, when i type a bogus path on my url string.. i'm NOT presented with my redefined 404 page. Instead, i always get a blank page with 'Primary Links' as the breadcrumb (at least i think it's a breadcrumb)

any ideas?

thanks

⋅ Categories: Drupal 4.7.x

Comments

t4him’s picture

t4him commented

assuming the node you created was a page,

check the url path setting and confirm you did not add a path there.

If you are using clean url's you can simply type 404 in the url path setting of the page node, then type 404 in the admin/settings/error handling Default 404 (not found) page: field.

I'm sure you know this, just hitting the basics first.

newdru’s picture

newdru commented

Actually i have no idea what you're talking about.. :-)..

fwiw... i have not set up any kind of 404 page in apache or anything.

i simply created a drupal content story node to be my "not found page". it exists at node/99.

in admin/settings : Error handling i set the "Default 404 (not found) page:" to -> node/99 (so i AM adding a path there.. that's what i'm supposed to do but you seem to be telling me the opposite?)

fyi, i'm NOT using clean urls right now.. my sites are all in test and figured it was just as well to not bring one extra element into learning drupal.

t4him’s picture

t4him commented

maybe you do not have the path module installed. It Allows users to rename URLs. It is core but needs to be installed at admin/modules, but that's ok, you don't have to have it right now.

in admin/settings : Error handling i set the "Default 404 (not found) page:" to -> node/99

since you are not using clean url's then your might need to enter ?q=node/99 in that field.

jarvklo’s picture

jarvklo commented

I've run in to a very similar problem.
As soon as I enable a 404-page, the site starts returning parts of the front page document instead of the basic 404-message or the custom 404 page.

* Path installed - check
* No views, I experimented with them briefly, but I've gone as far as to disable the views module in order to hunt down this problem since I found documents fingering "Views" as a possible culprit
* "404" path tips - Tried that, http://example.se/404 shows up as expected (as does the node path to the "page" document if I use the URL http://example.se/node/222)
* If I leave the 404-page config field blank i get the basic "page not found" page again.
* if I configure ?q=node/222 as the 404-page URL I get an error page containing the text "2" and nothing else but the basic Garland theme layout code

Any ideas where I might start looking for a remedy for this, or what I might have done wrong ?

[edit] - 5.0 was released today, and that seems to have fixed my problem automagically - Thanks Drupal team!

markus61’s picture

markus61 commented

my page http://www.bruesselerplatz.de shows exactly the same issue as described by jarvklo except one little difference.
it was not fixed by upgrading to 5.0 :-(

so please don't "close" this caase.

markus

===================
markus schulte
markus@bp11.de
www.bruessselerplatz.de

jenlampton’s picture

jenlampton
she / her
commented

I was having the same problem: instead of getting my custom error page when I typed in an invalid path, I would get a blank page that said "Guru Blogs" as the title and "no articles found" as the body. This looked suspiciously like a view I had created, but was not using. I went and looked at the view i had named "gurublogs" and sure enough, the empty text read "no articles found". I changed the empty text to "no articles found - test" and sure enough, a bad path now showed that text. Weird! Ok - so I cloned the view to one named gurublogstest and deleted the gurublogs view. Now typing in an invalid path returned an empty page with the content "2". Then I went and deleted the view entirely, and the custom error page worked as planned. On my live site, I didn't want to delete the view entirely (who knows, maybe I'll need it someday) so I was able to get the custom error page to work just by editing the view, and un-checking the box under "page" for "Provide Page View".

I hope this helps some of you with the same problem!

*~ current project: www.customerthink.com ~*

landover’s picture

landover commented

if i create a new page with drupal and give it a path alias, say err403, i can enter that path alias at
/admin/settings/error-reporting
and that works.
what doesn't seem to work is (as some user pointed out today on irc too), to specify an external (non-drupal) page.
in that respect, the form at /admin/settings/error-reporting is rather misleading, since it even places a
http://your.site.domain/
left of the input field where you specify the page to use, suggesting that any valid url starting like that would work.

i tried putting a file access_denied.html in my drupal root dir. of course, entering http://your.site.domain/access_denied.html in the browser's url line displays fine.
nevertheless, when i tried entering access_denied.html or /access_denied.html in the form at /admin/settings/error-reporting, neither worked, which leads me to believe that only drupal pages can be used as error pages.

senpai’s picture

senpai commented

I have just confirmed this error, and I will be filing a report against core to have the informative text changed to reflect that Error Reporting paths must be internal.

UPDATE: http://drupal.org/node/122442 is the open issue, and has a patch attached at http://drupal.org/node/122442#comment-877437.

****
Joel "Senpai" Farris | certified to rock score

asaaheim’s picture

asaaheim commented

Hi all!
I too, experienced this very same problem.
However, if you all make sure that your views are accessed through whatever you state as their "URL" in the setting up of the view (as opposed to just using the view name to access them - in linking to the views an so forth), the 404 and 403 behaviour in Drupal general settings page should work as expected.

This was valid for me, on a Drupal 4.7, using views that provided page views.

Good luck all,
I hope this can be of some help!

Have fun - keep Drupal going strong!

A.S.

jabberwooki’s picture

jabberwooki commented

Same problem as what is described above.
I created a new page content. I put my custom error message in it and saved the node. The node's id is 480.

I went to the /admin/settings/error-reporting page, filled up the 404 Error form field with what follows :
/node/480

A test with a non-existant url always returned me the basic Drupal error page, not my custom page until ... I removed the beginning slash from the 404 Error form field, like this :
node/480

Hope it may help.