Forums

I'm using 3.1 RC5.5.

I have a fillable form (http://saeurope.petersenuploads.co.uk/index.php?option=com_content&view=article&id=224&Itemid=82) which shows the confirmation screen after the form is submitted. This is correct, but when I then submit the confirmation page, it returns to the initial form, and doesn't submit (no email sent, nothing added to DB).

Looking at the confirmation screen the the URL of the POST is index.php?option=com_chronocontact&task=beforeshow&chronoformname=lensorder&Itemid=82

Which looks like it has the wrong task assigned to it. Is that correct? How do I get the page to submit? Is this a plugin order issue?

Thanks

Hi petersen,

The url is correct (if misleading). There are some serious bugs with the Confirmation page plugin that seem to block the emails and database save :-(

Bob

Ah ok. Does this mean that I should avoid it? Is there any way to get it working without DB/Email enabled?

Hi petersen,

I'm afraid that it's best not used with Email or DB save at the moment.

Bob

There may be a fixed version in the forums somewhere - I forget :-(

Thanks Bob. I'll have a hunt around.

Hey I know this thread is super old but I happen to be currently using an ancient ChronoForms (3.2) and am running into the same problem. But I think I found the problem.

What I needed really was just a page to nicely show some information based on their submitted info so they could print it before I send them to the next form where they fill in their contact info and do a final submit. So I figured I'd just axe the Confirmation page thing since it wasn't working, and just put my code for display in the OnSubmit boxes, along with another <form> tag with the action pointed at my second form and a bunch of hidden inputs containing the entire $_POST array, and a submit button. After all, that's pretty much what the Confirmation page does I assume.

But! When I did this, my second form loaded the first form. Turns out there's a gremlin in the $_POST array: chronoformname. When CF reads that post value, it loads the form associated with it (probably because there's some code using $_REQUEST instead of $_GET to conditionally load the proper form).

So if anyone else is in this spot still, hunt around in the Confirmation page source and kill that value before you generate the hidden inputs.😛