Debug info still showing after switching OFF

Hello,

My multipage form chain persists in informing me on the POST data from the previous form, even after switching off the debug parameter.
I verified that in all child forms plus the mother form on the general tab the debug param is OFF, as well as in the associated plugin params (Multipage and redirect in use).

Is there another place where I might have set the debug option to ON ?



Thanks, Wim

Hi Wim,

I can only see the strap line on any of the form links - no debug info but no form either.

Please will you (a) post a screenshot of the debug info you see and (b) check the Plugin Debug option is actually showing No selected after you save (I found a bug this morning that can mean that neither option is selected in some circumstances).

Bob

Hi Bob,

this is what I get on the second and further form pages:

[attachment=0]Picture2.jpg[/attachment]

and the Debug radio button in the Multiform plugin config is checked at No

Wim

Hi Wim,

That certainly looks like the output from one of my debug messages - the code generating it will be something like

$mainframe->enqueuemessage('$_POST: '.print_r($_POST, true));

I've just looked in the current reease of the multi-page plugin and don't see it there. Please will you take a look in your code boxes and comment it out if you find it there.

Bob

Hi Bob, no luck here, I checked all my form codes but didn't find the snippet you mentioned. Could it be somewhere else ?
Thanks, Wim

Hi Wim,

Hmmmm it must be somewhere (or something like it) . . .

Not in the OnSubmit Before Box??

If not, then I suggest that you email or PM me a SuperAdmin login and I'll go and hunt it down.

Bob

Hi Bob,

Stupid as it may be, I ran into the same problem as 3 years ago (see above). You fixed it at the time, but unfortunately I can't find my notes from back then. Do you maybe remember where the problem was?
Thanks a lot!

Hi Wim,

I think the fix is in this post. There's also a fixed version of the file somewhere in the forums . . .

Bob

YES! That was it. I've added the fix to my documentation this time . .
Thanks again!