I agree, Jim.
You should only see the 500 page in development mode.
In production mode, the message of the thrown error is shown directly
on the page instead of the rendered tag.
No need to poke around in page_context.rb, unless it's important for
you to have the same behavior in development mode.
On Sat, Oct 18, 2008 at 4:09 AM, Jim Gay <[EMAIL PROTECTED]> wrote:
> On Oct 17, 2008, at 10:04 PM, Joe Van Dyk wrote:
>> This is in production mode. I'm using the radiant exception notifier
>> plugin, which lets you put up your own 500 page.
>> I'm using Radiant to build a website that lets some non-technical
>> people update it. I'm trying to make it as easy as possible. It
>> doesn't seem right, if one person makes an error on a snippet that's
>> being used by every page, to not show the rest of the page's content
>> (and replace the snippet or tag with the error message). That would
>> let them easily figure out where the error occurred and would give
>> them clues to how to fix it.
> From my past experience and this recent test, that is what *should* be
> What does the 500 error say?
> Radiant mailing list
> Post: Radiant@radiantcms.org
> Search: http://radiantcms.org/mailing-list/search/
> Site: http://lists.radiantcms.org/mailman/listinfo/radiant
Radiant mailing list