Alright, so I made a instance with the 0.6.4 gem and was able to replicate that we used to get feedback. The thing is, the pertinent view code is the same.
Which got me thinking that it might have something to do with Rails 2.0? Does anyone know if the error message handling was changed? Another possible problem might be that the templates are not using the form_for helper, and are instead just outputing form tags. Perhaps there's some magic state underneath it all that's set by this tag? I'll look into this some more after lunch. -Andrew On Jan 18, 2008 10:57 AM, Andrew O'Brien <[EMAIL PROTECTED]> wrote: > From what I've found out, the generic error messages you're talking > about come from > Admin::AbstractModelController#announce_validation_errors (in > app/controllers/admin/abstract_model_controller.rb). Neither the > layout for all of the admin controllers or the individual templates > for any of the actions call the standard error_messages_* helpers, > which (unless I'm missing another better way to access them) would be > the best way to access the validation error messages and report them > in the view. > > Looking through a couple of revisions, I haven't actually found any > where the errors are reported that way, so I'm a bit at a loss for why > it would be working with the gem. > > I can, however, verify that the demo site shows the > less-than-desirable behavior. > > -Andrew > > On Jan 18, 2008 12:01 AM, Chris Parrish > > <[EMAIL PROTECTED]> wrote: > > I want to bring a bug to the attention of the newsgroup that I haven't > > been able to track down. John has asked that I post this here in hopes > > that one of you might be able to identify this issue and submit a patch. > > > > In some cases Radiant is failing to provide validation error messages to > > users. Instead of providing specific messages tied to the offending > > fields, they only get the one error message across the top of the > > screen. When that's their only message it comes across like "Oops, you > > goofed. Now let's see if you're smart enough to figure out where. Mwaa > > haa haa haaa!" (well, ok different users read things differently). > > > > Now, this doesn't happen in every installation. I notice a relationship > > depending on whether I'm running radiant via gem or with radiant > > installed in my project's /vendor directory (running from gem works > > fine, installed in /vendor doesn't). Please note: this is an > > observation and a starting point but I haven't proven anything so far. > > > > By the way, the Radiant Demo (http://demo.radiantcms.org) is missing > > these error messages. > > > > My ticket is here: http://dev.radiantcms.org/radiant/ticket/601 > > > > -Chris > > _______________________________________________ > > Radiant mailing list > > Post: [email protected] > > Search: http://radiantcms.org/mailing-list/search/ > > Site: http://lists.radiantcms.org/mailman/listinfo/radiant > > > _______________________________________________ Radiant mailing list Post: [email protected] Search: http://radiantcms.org/mailing-list/search/ Site: http://lists.radiantcms.org/mailman/listinfo/radiant
