Symphony.

I'm getting ready to launch site for a client and I'm having issues getting a 404/Error page working with Symphony:

http://dev.songsforsaplings.com/

I created a page called Error and gave it a type of 404, hidden. When going to an erroneous page, like http://dev.songsforsaplings.com/foolish/ it just always shows the home page.

What am I missing? Any ideas?

Here is my master.xsl file:

https://gist.github.com/cf7edc8d0ac0514e1d7c

What am I missing? Any ideas?

URL parameters on the indexpage?

http://dev.songsforsaplings.com/about/zombie-jesus/ shows the 404 page.

These pages are built from a datasource and I know you can select Redirect to 404 page when no results are found but still not sure how to have that and the blank /music/ page without params both work.

Perfect, I removed the URL parameter on the home page and it works. Thanks a TON!

Any idea how to get a page like http://dev.songsforsaplings.com/music/weird/ to show a 404. I have a URL parameter called title but I still want to be able to just access http://dev.songsforsaplings.com/music/ without any url parameter. How does one make this work?

These pages are built from a datasource and I know you can select Redirect to 404 page when no results are found but still not sure how to have that and the blank /music/ page without params both work.

Should work as long as the title parameter is not required for the datasource, but not entirely sure at the moment.

The problem is that this page works in directing to a 404:

http://dev.songsforsaplings.com/music/weird/

But this page now also directs there (and it shouldn't):

http://dev.songsforsaplings.com/music/

When I direct page-data-single to a 404 it kills the whole site.

Have you considered using a Routing extension?

I usually (for example) route /blog/ to a /blog/page, and /blog/:title/ to a /blog/article/:title/ page, so I can handle things differently on both pages and still have a clean URL structure.

I may need to do that. I'll check it out. Thanks!

Actually, is this a routing issue? If someone created a /blog/ they would want it work with a URL param like /blog/a-new-article and also be able to go to the blog landing page, right? It seems like there would be an easy way to manage both and handle errors when a param wasn't found.

If someone created a /blog/ they would want it work with a URL param like /blog/a-new-article and also be able to go to the blog landing page, right?

Correct, but /blog/ and /blog/a-new-article/ are usually different pages (different html, different datasources, etc.), so it's generally a good idea to also use different pages in Symphony instead of using the same page with a parameter and handle everything in the template.

The routing extension could then be used to create the above URL structure, so you can still use /blog/a-new-article/ instead of /blog/article/a-new-article/ (that would be the actual Symphony page for articles with a parameter).

Solved it by passing values into the missions:single and music:single datasources:

$title:volume-1-god-and-creation

and:

$title:english

When I turn on 404 redirects, everything works.

You can see it here:

http://dev.songsforsaplings.com/music/

http://dev.songsforsaplings.com/music/sdjhfkdsjhf/

What you said makes sense though... my method is probably a hack.

Simply add {$title} in the Required URL Parameter when checking the box Redirect to 404 page when no results are found.

That's what I did. I actually did this:

$title:volume-1-god-and-creation

That way people can navigate to /music/ as well as stuff like /music/volume-1-god-and-creation/. Didn't know you still frequented these forums, Kirk. Awesome!