> The logging properties have undergone changes recently, but the general
> idea is that in the TR.props logging properties there are some
> properties that end in (or contain) "level" which is set to ERROR or
> INFO or DEBUG, etc. Make sure the appropriate one is set to DEBUG.
Excellent - I have this working now and am very pleased with the
functionality offered.
> > My last outstanding problem is that when a validation
> > error is picked up by intake and the form is redisplayed,
> > $entry is no longer in the context and thus the form is
> > displayed with no fields filled in. I'm sure I had this
> > working at one point, but I can't seem to repeat it.
> > Can you spot my hopefully obvious mistake?
> >
>
> I do not understand why $entry would be in the context the first time
> Login.vm is displayed but not the next time. Login.class's methods will
> be invoked in the exact same way every time. But you are instantiating
> a new Subject each time, I am not sure how it would contain the data you
> want. But the form fields should be showing the entered form text the
> second time anyway so what is in $entry should not matter, except that
> it have the same QueryKey.
I have managed to figure out what is causing $entry to be empty the
second time. The link on Index.vm that goes to Form.vm includes:
.addPathInfo("subjectid", $entry.SubjectId)
which provides the key to the Form action. When a validation
error occurred on Form.vm, this parameter was not available and
so $entry ends up being empty. If I add the same parameter to
the link that Form.vm submits to (which is itself, as required by
intake) the correct data is retrieved each time by the Form action.
I was half way through writing a whole bunch of stuff complaining
that the form is being reset each time a validation error is
encountered, but in fact it is not! What intake is doing is resetting
the "required" fields that I have deleted in order to cause validation
errors. If I change other fields so that they are still valid, the
changes are retained. This is pretty good - if the user deletes a
required entry, intake restores the original value automagically.
I am half inclined to point out an apparent inconsistency in that
other rules (well at least mask) retain the edited value, but this
too is I think desirable.
I am very pleased to finally have intake working on my form.
Every day I work out how to use another piece of turbine and
every day I am more impressed.
I think I now have enough knowledge to go away and build
my application. Well almost, I think I need to read a bit more
about the pull model before I jump in there.
Thanks very much John for your time and patience in helping
me with this problem.
Cheers,
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
