Re: [Radiant] Radiant tag errors

2008-10-25 Thread Joe Van Dyk
On Sat, Oct 25, 2008 at 9:59 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: On Sat, Oct 18, 2008 at 6:41 PM, Jim Gay [EMAIL PROTECTED] wrote: On Oct 18, 2008, at 3:17 PM, Joe Van Dyk wrote: On Fri, Oct 17, 2008 at 7:09 PM, Jim Gay [EMAIL PROTECTED] wrote: On Oct 17, 2008, at 10:04 PM, Joe Van Dyk

Re: [Radiant] Radiant tag errors

2008-10-18 Thread Manuel Meurer
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.

Re: [Radiant] Radiant tag errors

2008-10-18 Thread Joe Van Dyk
On Fri, Oct 17, 2008 at 7:09 PM, 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

[Radiant] Radiant tag errors

2008-10-17 Thread Joe Van Dyk
Right now, when an editor messes up a radiant tag, a 500 page gets rendered. Would it be possible to display the page content, except for the radiant tag that had the error, and show the error message in place of that tag? Joe ___ Radiant mailing list

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Manuel Meurer
What exactly do you mean by messes up a radiant tag? Do you have an example? Manuel On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: Right now, when an editor messes up a radiant tag, a 500 page gets rendered. Would it be possible to display the page content, except for

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Joe Van Dyk
Err, sure: r:asdf / On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer [EMAIL PROTECTED] wrote: What exactly do you mean by messes up a radiant tag? Do you have an example? Manuel On Fri, Oct 17, 2008 at 7:00 PM, Joe Van Dyk [EMAIL PROTECTED] wrote: Right now, when an editor messes up a

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Manuel Meurer
From radius.rb #284 # Like method_missing for objects, but fired when a tag is undefined. # Override in your own Context to change what happens when a tag is # undefined. By default this method raises an UndefinedTagError. def tag_missing(name, attributes, block) raise

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Joe Van Dyk
What if the user types in: r:children:each (forgets to close the tag) r:assets:link id=title / (uses title instead of id) r:snippet / (doesn't specify the name) Instead of the exceptions bubbling up to the top and just seeing a 500 error page, wouldn't it be better to catch those errors and

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Manuel Meurer
As I said, I am pretty happy with Radius' tight validation, but I am sure there is a way to fix this, probably as easy as defining your own Radius Context and overwriting a couple of methods. Poke around in radius.rb a bit, it's commented very well. Manuel On Sat, Oct 18, 2008 at 12:52 AM, Joe

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Jim Gay
In what environment are you testing this? When doing r:asdf / in development I get a StandardTags::TagError page In production I just get a message undefined tag 'asdf' On Oct 17, 2008, at 3:31 PM, Joe Van Dyk wrote: Err, sure: r:asdf / On Fri, Oct 17, 2008 at 12:28 PM, Manuel Meurer [EMAIL

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Jim Gay
With r:children:each and no accompanying end tag, I get a Radius::MissingEndTagError page in development. In production I get the message end tag not found for start tag `children:each' On Oct 17, 2008, at 6:52 PM, Joe Van Dyk wrote: What if the user types in: r:children:each (forgets

Re: [Radiant] Radiant tag errors

2008-10-17 Thread Jim Gay
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