admin

Really good questions, thank you for asking!

Q: Is the completed PDF form saved somewhere or is the merge regenerated each time the form is downloaded?
A: Completed PDFs are NOT saved anywhere. You do have the option to automatically attach them to emails, which would ‘save’ them in an email account…

Q: If the merge is performed each time, are the merge setting files deleted after a period of time? Are they saved to MySQL?
A: The merge is performed each time by the shortcode, therefore ‘merge setting files’ do not exist. Rather, merges are managed by the Field Map Layout found in the plugin admin screen. The shortcode tells WordPress which Formidable Form, Dataset and Field Map Layout to use.

Q: Under the Settings tab, what is the Embedded Forms option?
A: Required to define a uniqueID to be used by the Plugin to merge a Formidable Embedded Form section to it’s main form.

Q: How long are backups stored?
A: Field Map Layout Backups can only be deleted manually by Admin users, not automatically by the plugin.

Q: The “select dataset to export” is either grayed out or reads: “This form does not contain datasets” – but the merge to PDF does work. ??
A: The PDF form will open, but not merged with any data. This functionality may be revised in the near future as the results are not expected, needed or desired… (we really didn’t notice it – thanks!)

Q: If we need to put “dataset=[ID]” in the shortcode – why not make that automatic?
A: The [id] is used by the Shortcode to merge the ‘current dataset’ while in a specific form or view, but doesn’t work in a email or static web page. There are many uses a site would want the Shortcode to have static or other dynamic data populating the “dataset=x” parameter. [id] is just another way to populate the parameter.

We remain at your service, and look forward to any further questions.

We created an update to our plugin – and – Formidable updated Forms and as well as the Signature Add-On, did you update all three?

We experienced issues with our signature mappings too after the Formidable updates, we had to completely remove and reinstall the Signature Add-on Plugin, then all was fine.

If all three plugins are updated (and working), we may need to take a look at your installation. If possible, email temporary login credentials to support at formidablepro2pdf dot com. If not possible, let us know if old datasets are merging at the correct size, or if they too have a size issue.

By “signature field” that is a PDF text field that you have mapped to a Formidable Signature field, correct? Or are you trying to map to a PDF Signature Field? To be clear, the Formidable Signature Add-On only maps to PDF Text fields, not PDF Signature fields.

We’re still working on the admin-ajax question…

Text alignment in PDF form fields is a function of the PDF form. Which program or app are you using to create the PDF form, as most of them default to centering from top to bottom?

Text alignment in PDF form fields is a function of the PDF form. Which program or app are you using to create the PDF form, as most of them default to centering from top to bottom?

Support for merging images to fillable PDFs is now available by updating the plugin to the newest version released today.

The function maps Formidable’s Image URL and File Upload (single) fields to PDF text fields.
. If the image height is more than the text field, the image height and width will be reduced proportionately to the max height of the PDF text field.

. If the attached file not an image, the file path will be merged to the PDF text field.

We remain at your service.

Issue resolved. It was a conflict with a plugin or the theme, we made a change to our plugin and created an update to resolve the issue.

Thank you for using Formidable PRO2PDF, we remain at your service.

The functionality appears to be by design by Formidable Forms where the UTC time is saved, not the local time. We are examining options to show the local time when merged into a PDF.

We will update you again soon.

More info here: https://formidablepro.com/help-desk/created_at-and-updated_at-field-in-db-formidable-tables-use-utc-not-local-timezone/

A couple of ideas come to mind…

. Formidable Form has a file upload field that may be used to organize and store the pdf on your server.

. Our development services can provide you with personalized customization of the plugin by adding an optional shortcode parameter that would save the PDF to a folder on the server, and provide organization of the PDFs if needed. If interested, please send an email to support at formidablepro2pdf dot com to receive a custom development offer.

Current Time gets data from the WordPress Timezone setting. You’ll need to adjust the Timezone from the WordPress Dashboard under “Settings => General => Timezone”.

Regarding current time within the user profile, that’s a question for the outstanding support team at WordPress.org.

We remain at your service.

We have added two more “UniqueID” counters to the “Webform Data Field ID” dropdown list. Update the plugin to use the counters.

1. Formdiable: Count Entry – provides a unique number for each user entry – starting at 1.
2. Formidable: Count PDF – provides a unique number for each PDF output – starting at 1.

The new Formidable: Count PDF counter may be reset by creating a duplicate of the field map layout – the counter for the new layout will start at 1.

The new Formidable: Count Entry counter cannot be reset as it actually counts the number of form entries.

Not sure. To create a “UniqueID” field, Formidable suggests using their Auto Increment shortcode [auto_id start=1], instead of the DatasetID.

I logged in and tested both Field Map Layouts and they are working as expected. You may have to wait a few seconds after selecting the Field Map Layout as there are 196 mapped fields that need to load and can causes a timeout, however that issue does not exist when using the shortcode to create the PDFs.

One day or less.