404 template

My install in the base install with no templates. Can someone post the 404 template for the ModX Host template? The one with the sitemap and descriptions on the page?

That’s no longer available after 0.9.2.1 (I assume you’re using an 095 beta). It was a simplified contact form tacked onto the bottom of a sitemap (Ditto page listing), a search box, and a contact form if you’d care to recreate it.

What I am talking about is part of the 0.9.5 beta. It’s the 404 page content in the sample website created on install.

It was in the system before I reinstalled without the sample data. I am just trying to avoid doing a complete install to get the content of the sample data 404.

this is the content of latest beta 404 page with MODx host template

There we go. I was missing the showDescription tag and didn’t notice it in the docs.

I like 2 things:

1. I enjoy how on a 404, the referring URL request is passed in. How is this accomplished via MODx?



2. Further, when I try and deliberately browse to a page that does not exist on my site, I am shown the 404 template, but the URL in the browser stays the same.

What this means for me is: Let’s say I try to browse to the /install directory even though it isn’t there. I go to http://www.mysite.com/install/ and I see the 404 template, but the URL is the same. And since I referenced it as a DIRECTORY, rather than a page name (e.g. /index.html) all of my relative pathing in my site is now off a directory, and everything is displayed wrong, unstyled, etc.

How do I get it to redirect to 404.html (404 is my proper alias, too, as I am using SEFURLs)

You don’t redirect to the 404 page, it gets forwarded now. This is the proper way to handle it. Doing a redirect would not allow the proper 404 response. Instead, your template/document that handles the 404 needs to work from any subdirectory in your site. This is the reason why I make use of the BASE tag in every template I design for MODx, and it also makes my templates work regardless of how I have my document folder structure set-up when using alias paths.

Quote from: OpenGeek at Nov 07, 2006, 02:06 PM

You don’t redirect to the 404 page, it gets forwarded now. This is the proper way to handle it. Doing a redirect would not allow the proper 404 response. Instead, your template/document that handles the 404 needs to work from any subdirectory in your site. This is the reason why I make use of the BASE tag in every template I design for MODx, and it also makes my templates work regardless of how I have my document folder structure set-up when using alias paths.

Interesting... I will implement now and report back.

Ah, it appears I am already using BASE.

I wonder why my style sheet is not acting relative to that, couldn’t be because is in my HEAD, prior to BASE declaration, could it?

I have also moved my 404 document into a subdirectory, but am not sure how that could be a solution? Unfortunately, it did not work for me :/

Quote from: pixelchutes at Nov 07, 2006, 02:28 PM

I wonder why my style sheet is not acting relative to that, couldn’t be because is in my HEAD, prior to BASE declaration, could it?

The BASE tag needs to go before any element that contains a src or href attribute or a style definition that uses @import