Forums

Can it be done? Could you allow the admin to change the debug level for troubleshooting purposes?


Aaron

Hi Aaaron,

Sorry, I don't understand the question - what do you want the DeBug to do?

There is a DeBug option in ChronoForms that the Admin can turn on and off; and there's always the Joomla DeBug too??

Bob

Hi Bob!!

Thanks for the reply. Usually with debugging on a system there are different levels of debugging (what is displayed in the UI) for troubleshooting purposes. So if I turn *on* debugging for the ChronoForms, I only see the data that is POSTed from the FORM in the UI. Is that all that is available for debugging? I find that I have to create duplicates of FORMS to test out scenarios before I put it in my live FORM.

For instanace, if I rename a FORM in the ChronoForm UI, it form breaks... it would be nice to see some error level returned so I have somewhat of an idea on how to resolve the issue... Another example is when I am using the FORM to submit a .mp3 to the server. The form completes, the /dir is writeable, yet the file is not being uploaded successfully and there is no error returned....

I'll see what the combination of Joomla's debug + ChronoForm's debug come up with

It just seems a little harder than I thought to get the integration of the form to work because I either can't find the thread that helps or that the Debug is not really helping either. Either way I'm still plugging away because this is super fun!!!!


Thanks Bob,

Aaron

Hi Aaron,

Yes that's correct, there is only limited debugging built in. We show you the progress steps, the $_POST (and $_FILES in the latest release) and 'dummy' versions of the emails. If you aren't seeing the 'progress steps' messages it may be that your template doesn't support Joomla 1.5 system messages.

There isn't a great deal else that could be built in by default. It's pretty straightforward to add some extra diagnostic code in the Form HTML or OnSubmit boxes if you need it though.

Bob

In addition, you could always enable php's native error reporting, or use your own error/exception handler - if you are having problems with "500 Internal error" messages. Be careful with this on production sites however, as you might reveal sensitive information to a 3rd party (I personally prefer a custom error/exception handler that sends a complete error report to a dedicated email account).

Thanks for the replies and help guys!!


Aaron