Hello,
you can configure the logs in logkit.xconf like that :
<category log-level="DEBUG" name="forms">
<log-target id-ref="forms"/>
<log-target id-ref="error"/>
</category>
but from my experience, i didn't solve many forms related bug using this
log.
not sure if this would help, but i noticed that when the form is
processed through multiple successive pipeline, error messages tend to
be lost in the process. A good thing to do when you can is to call the
pipe directly from the browser, and if you have to call it from flow to
pass some parameters, just create a small debug function in flow that
just init the buisness data, and call the form as directly as possible.
If you still don't get anything obvious happening, you can set up a view
that simply serialize to xml, and put a label="viewname" at the begining
of your form generation. then you call the url of your debug function,
with the cocoon-view parameter and you should be able to see the error
in your binding.
hth,
Marc
Thorsten Mauch a écrit :
I'm despairing. Since hourse I seek a bug in my binding. I enable debug more
for logging, but i still not see waht happend.
No Error Messsage apear. Ist it possible to turn on a "debug mode" CForms ?
At least i want to see if the xpath expressions are correct processed.
Also it would help if a expression can't be resolved a error is thrown
Thx Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
