Never mind - I found the answer in a separate thread: apparently my
global msg tags were "wrong"
BEFORE:
<lift:snippet type="msgs">
<lift:error_msg>
<strong>Error! The details are:</strong>
</lift:error_msg>
<lift:error_class>error</lift:error_class>
<lift:warning_msg>
<strong>Whoops, I had a problem:</strong>
</lift:warning_msg>
<lift:warning_class>notice</lift:warning_class>
<lift:notice_msg></lift:notice_msg>
<lift:notice_class>success</lift:notice_class>
</lift:snippet>
AFTER:
<lift:Msgs showAll="true">
<lift:error_class>error</lift:error_class>
<lift:notice_class>notice</lift:notice_class>
<lift:warning_class>error</lift:warning_class>
</lift:Msgs>
<lift:snippet type="msgs">
On Jan 15, 3:16 pm, stephanos <stephan.beh...@googlemail.com> wrote:
> Are you sure it's a template issue?
> I mean the other forms (e.g. login form) work properly..
>
> Taken my limited knowledge of lift I suspect the "S.error(xs)" line of
> the MetaMegaProtoUser testSignup() function to be responsible. Maybe
> the error() function has a bug for List[FieldError]?
> Link:http://scala-tools.org/mvnsites-snapshots/liftweb/lift-persistence/li...
>
> Can anybody comment on this/confirm that?
>
> PS: I saw this in 1.1-M8 and 2.0-M1
>
> Cheers,
> stephanos
>
> On Dec 30 2009, 9:01 am, Marius <marius.dan...@gmail.com> wrote:
>
> > Any example of such situation? For more complex forms probably users
> > would specify their own forms. Since you know that field's unqueId's
> > you can just put the msg tags in the page manually.
>
> > In Record there is a more flexible way as users can specify a form
> > template ... se MetaRecord.formTemplate. I'm not sure if Mapper has
> > something similar.
>
> > Br's,
> > Marius
>
> > On Dec 30, 4:25 am, Naftoli Gugenheim <naftoli...@gmail.com> wrote:
>
> > > It would be nice if they did that.
> > > How would you tell Lift where to put the notice, in cases where it's not
> > > directly adjacent to the field?
>
> > > -------------------------------------
>
> > > Marius<marius.dan...@gmail.com> wrote:
>
> > > IMO <lift:msg id="..."> should be generated by the same code that
> > > generates the form fields so that the field errors to appear nearby
> > > the field itself. I assume you are using ProtoUser.
>
> > > Looks like a bug to me.
>
> > > Br's,
> > > Marius
>
> > > On Dec 28, 2:36 am, tiro <tim.romb...@googlemail.com> wrote:
>
> > > > Just discovered this issue (1.1-m8): Thesign-upform will not display
> > > > field errors by default. The user therefore gets the impression that
> > > > the application has simply stopped responding. The validation I
> > > > checked (and this may be the only one) was the unique e-mail address
> > > > validation. If the e-mail address has already been used before, it
> > > > sends a FieldError to S.error. Displaying the message would require a
> > > > specific call to the Msg-Snippet for that field afaik; but this call
> > > > is not generated by the localForm method.
>
> > > > For now I will explicitly call the snippet for the email field in the
> > > > surrounding template, so that the message will be displayed above the
> > > > whole form.
>
> > > --
>
> > > You received this message because you are subscribed to the Google Groups
> > > "Lift" group.
> > > To post to this group, send email to lift...@googlegroups.com.
> > > To unsubscribe from this group, send email to
> > > liftweb+unsubscr...@googlegroups.com.
> > > For more options, visit this group
> > > athttp://groups.google.com/group/liftweb?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Lift" group.
To post to this group, send email to lift...@googlegroups.com.
To unsubscribe from this group, send email to
liftweb+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/liftweb?hl=en.
