Sometimes my controllers discover a user error: a URL pointing to a nonexistent database record, or query/form input that doesn't match what the form HTML would have allowed. The Pylons error system isn't quite what I want; I'd rather send back a regular page with the site decorations and a message saying "That record doesn't exist, try searching" or "You don't seem like a real human." -- with a 400-series status. Because just aborting with 500 makes it look like the site is buggy, and a text error message doesn't have the links to get them back on track. I could adjust the error template style but it seems like overkill when I can just do it in the controller. Is there any problem with just changing the status in the controller and returning an alternate template page?
-- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
