I had a problem in a Hobo 1.0 app, where error messaged did not show up in 
a custom tag.

This actually did work fine, until the app was upgraded to Hobo 1.0.3.

I thought this may just be a version issue - so am in the process of 
upgrading to Hobo 2.0, however, the issues still seems to exist.

I have a homepage  which has been moved from Front Controller to another 
custom controller I have.

Within that homepage, I have a check that the current user has accepted 
some terms and conditions (a boolean flag on the user model) if it returns 
false, the I call the custom tag which lives in application.dryml - 
<acceptTerms>

Within that <acceptTerms> tag - I have a portion of a form, which allows 
the user to accept the terms and conditions, and change the flag to true - 
which will then allow the main homepage to show (and bypasses this custom 
tag. 

So the functionality all works well - but when the user does not 'check' 
this checkbox, to accept the terms - and tries to continue, the error 
messages should show up, (within the tag I have <error-messages /> in an 
appropriate location, as with any other form) - but they do not show.

(The error messages are defined with a validation method on the user model 
- :after_validation :check_accepted, :on => :update)

As I said, they used to show in hobo 1.0.2 - but in hobo 1.0.3 and hobo 2.0 
they are nowhere to be seen.

Could this have something to do with the tag containing a field for the 
User model, when the tag is called initially in a different model? 

Thanks for suggestions in advance

Pete

-- 
You received this message because you are subscribed to the Google Groups "Hobo 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to