David R. Woolley

Nevermind – I’ve now been able to change the “HTML” name in the HTML fields to something more descriptive of the particular item. I’m not sure why my earlier attempts to do this failed to stick, but it’s working now.

How would I change the name of the fields? I notice that with an HTML field open, I can click into the place in the upper left corner where it says “HTML” and edit it to say something different, but what I type there doesn’t stick when I save changes – it always reverts back to “HTML”. So maybe that’s not the field name.

When I open the field options, I don’t see anything that’s labeled a name.

What am I missing?

Dan, I sent you a couple of emails last week but didn’t hear back from you.

Here’s some information I received from the Formidable folks:

“Alright, I looked into our JavaScript and we have this line of code:
jQuery(document).on(‘submit.formidable’,’.frm-show-form’,
frmFrontForm.submitForm);
This code watches for a submit event within a Formidable form. The
back/next buttons are triggering a submit event since they have no
type attribute specified.

If the PDF Embedder author adds type=”button” to all the buttons in
the PDF Embedder, then this will resolve the submit issue.”

I’m hoping this is the solution to the problem. Can you make this change to the PDF Embedder plugin?

Ticket submitted.

We have a Starter account with you. If we need to upgrade to a higher level to have you look into this, let me know.

Thanks for the reply, Dan. The reason we have the PDF embedded within the form rather than separate from it is that our application is a series of writing prompts to assist a user in writing reflections on their life to pass on to their families. We have a workbook that includes writing examples and prompts, and people will likely spend a considerable amount of time writing and rewriting in response to those prompts. Formidable is a good choice for this because it allows people to save a draft of whatever they’ve written and come back to edit or add to it later. Even though there are a dozen or so areas for the user to write in, ultimately it will all be of a piece and we don’t want them to have to manage a dozen different pieces of in-progress text. So it’s inherent in the application that the entire thing be held within a single form, and PDFs containing writing prompts be interspersed between the form fields.

This is all just by way of explaining why it’s set up the way it is.

Anyway, I appreciate your advice and will take this up with the Formidable developer. Your suggestion about where the failure might be could be helpful in that conversation.

Demonstration of the problem: https://new.thinkofit.com/pdf-form

This is a very bare-bones setup of WordPress 4.5.3. The only active plugins are Formidable, PDF Embedder Premium Secure, and Weaver Xtreme Theme Support.

Also, it makes no difference whether the “submit form with Ajax” option is enabled or not; the problem occurs either way.

Another detail I should have mentioned: When I put a simple hand-coded HTML form on the page with PDF Embedder, there is no interference. That is, clicking the PDF Embedder’s page flip buttons does not cause a form submission in this case. So it is definitely an interaction with Formidable, not an issue with forms in general.

Did you ever find a solution for this? I’m looking for something similar.

I’ve got this plugin going semi-successfully, although it seems there might be some clashes with the 2013 theme.

It would be helpful to see a site where this plugin is being actively used. Can you suggest one or two to look at?

Updating the plugin seems to have solved the problem. Thanks!

Thanks. Also, I was wondering if you recommend a particular theme (or themes) that work well with this plugin?

Success! Thanks for the fix.

Hello? tap tap tap Is this thing on?

The question is, is Advanced Page Manager compatible with FORCE_SSL_ADMIN or not? And if not, can you make it compatible?

After more experimentation, I’ve found that the problem occurs because we use an SSL certificate on this site and have this setting in wp-config:

define(‘FORCE_SSL_ADMIN’, true);

It’s an e-commerce site, so security is important.

When I activate the plugin on our development site which is exactly identical except that FORCE_SSL_ADMIN is turned off, it works fine.

So my question is, if I turn off FORCE_SSL_ADMIN just long enough to let the plugin do its initial thing, will it then keep working with FORCE_SSL_ADMIN turned on? Or is this a show stopper?

How did I overlook that??? This is exactly what I need. Thanks!