Mezzanine returns 200 for non-existent subpages.

[klebed]

Hi!

I've found strange bug with lastest mezzanine instalations. It is not handling 404 for subpages of subpages.
Example:
/ - will return 200 and show main page (right behaviour)
/fjshdkjhfkjds/ - will return 404 (right behaviour)
/existent-page/ - will return 200 and show existent-page page (right behaviour)
/existent-page/glkjfdgkljfd/ - will return 200 and show existent-page page (wrong!)
/existent-page/glkjfdgkljfd/kjlksajjsk/ - will return 200 and show existent-page page (wrong!)

and so-on.
was checked with multiple projects on newly created virtualenvs.

[stephenmcd]

Thanks for the report.

[klebed]

WOW! That's was fast! =)
Frankly speaking i've tried to look into code, but due to lack of experience in mezzanine failed to determine where problem is.
Thank you so much!

[AlexHill]

Hmm. I guess it's hard to argue that this is not a valid bug, but I was making use of it – using the part of the slug following the page's slug as a kind of query string in a page processor (in the same way as a third-party app mounted in Mezzanine's page tree might).

One way to allow this kind of thing would be to run the page processors before calling the page view. That way you can just skip Mezzanine's page view by returning a response from your processor. Does that sound reasonable Steve?

[klebed]

Hi, Alex! You can allways catch request before it go to a page processor, and direct it to whatever you want. But default behaviour should be straightforward, because otherwise it becomes confusing. If page not exist, CMS should return 404, because it is a special code for non-existent content, it's a standard.

[stephenmcd]

Alex that sounds like a great solution

[AlexHill]

OK, I'll submit a patch shortly. It has the added bonus of not generating a response for the regular page view if it's never going to be seen.