Forum Replies Created
-
Posts
-
Great news! Thank you.
We remain at your service.
Has the issue gone away after upgrading the plugin?
The developer requires ssh access in order to continue troubleshooting this issue.
We remain at your service.
Regarding the creation issue. “Creation in backend works perfectly fine.”
. Are you able to merge to PDF from the Admin page of the plugin?Regarding: “However, the PDF in frontend is 1kb of size and unreadable.”
. Do you have more than one layout configured, verify you using the correct layout_ID and if so, export the Template and upload it to this form for us to take a look.We remain at your service.
What is your oder number?
Your issue may be easier to troubleshoot, the other user’s installation freezes for 3-5 minutes. If possible, please complete this form to have us login to your installation to find and fix the issue.
We remain at your service.
This support request has been sent to our senior developer. Please allow 0-3 days for a status update.
This is not an issue we’ve seen before. Please backup your field map layout TEMPLATES, then, disable, delete, and reinstall the plugin and let us know if the issue is resolved.
We remain at your service.
Thank you for using the plugin!
Sure, it’s slick and easy! You can make the layout=id dynamic by using the Formidable Dropdown Field’s “Use separate values” option to provide the ID of the Field Map Layout, and pass the current entryID as a variable in the form’s redirect URL to a hidden field like this…
http://www.yoursite.com/redirectpage/?dataset_id=%5Bid%5D
Then, in your hidden field: [get param=dataset_id]Your PRO2PDF shortcode would look something like this, [formidable-download form=”oqzilp” dataset=[789] layout=[123 show=value]]
(Where [789]=hidden field and [123]=dropdown list of PDFs with Field Map Layout ID’s as “Use separate values”.)We remain at your service.
Thank you for using the plugin, we appreciate that you are enjoying it and finding more ways to use the shortcode!
[id] by itself will not work in a page/post. However, you can use [id] within the shortcode inside a view, and then publish the view’s shortcode in a page or post. Then, you can pass any entry_id through the URL to the view.
We remain at your service.
No, Indesign does not use standard PDF fields. However, we can take a look at the file to see if it’s possible to convert the form to a standard PDF form if you upload the PDF here.
We remain at your service.
Your activation code was emailed upon purchase to the email address on the account (webmaster@hdlbrokxxx.xxx.xx) and has been resent. Please check your spam folder and let us know if one or both emails were received.
Thank you for your support request, this issue was caused by the disabling of mbstring on your WP environment, and has been resolved on your server with the latest update (v2.30).
Thank you too, for using the plugin. We remain at your service.
Thank you. Your support request has been sent to our senior developer. Please allow 0-3 days for an update.
We remain at your service.
It appears the issue is being caused by one of more of the Repeatable Section Fields in your form. We’ve imported and tested your form on our server and all appears to work as expected, although this is a very large form of required fields, and numerous variables may be different from your installation to ours. Additionally, some of the required fields are causing odd errors in Formidable, which may be related or may not.
We’ve also spent a good deal of time dissecting duplicate Field Map Layouts on your site, however, have not yet found the cause of the issue.
Could you assist us in troubleshooting by creating a simpler version of one repeating section form and map it to your form to see if the function is causing the issue?
We remain at your service.
Please verify that you disabled, deleted and reinstalled Formidable Forms and the Formidable Signature Add-On Plugin with the latest versions. We have seen this issue before and found this to be the resolve.
We remain at your service.
The Template appears to be working.
Signature: http://formidablepro2pdf.com/fp2p/wp-admin/admin-ajax.php?action=wpfx_generate&form=kvktm&layout=1041&dataset=1097&format=pdf&inline=1&key=c87c7f32ccb48b6b3737eeb1bf578648Please deactivate and delete both Formidable Forms and the Signature Plugin and reinstall. You will not lose any saved forms or entries when you delete Formidable. from Formidable’s site
If reinstalling does not fix the issue, please also try disabling all other plugins to rule out a conflict, and then if the cause of the issue is not found and it’s possible for us to login to your WP installation, please complete this form so we may troubleshoot the issue on your server.
If not possible to login, let us know and we’ll continue further assistance.
We remain at your service.
Our apologies, the form has been updated to accept the file. Please try again.
This is likely an issue with your site’s CSS. Try adding the “Title” parameter, like this;
[formidable-download form=”4t3wc” dataset=[id] layout=”13″ title=”Download”]
or use the Class parameter like this;
[formidable-download form=”4t3wc” dataset=[id] layout=”13″ class =”my_button”]Or, with the PRO version you can also use the Label parameter – Outputs the URL only – unformatted;
[formidable-download form=”4t3wc” dataset=[id] layout=”13″ label=0]Let us know if these optional parameters fixes the issue. We remain at your service
Stefano, you never contacted us after the issue was resolved to let us know you were experiencing the issue again. This was caused by an excessive amount of tmp files being created in the /tmp folder. Did the issue begin after a recent update? Can you check the folder and let us know if it’s full of files?
Please complete this form if you would like us to log in again.
We remain at your service.
Yes, please complete this form to have us login and take a look at the issue.
We remain at your service.
Do not use the PDF signature field, it’s not compatible with the plugin. However the PDF text field should have worked if you select “Signature” under the format dropdown of the field mapping.
Please upload the Template file to this form.
To export a Template; From the PRO2PDF Admin Page → Templates → Export field map → Export
We remain at your service.
Thank you for your request for support regarding your recent update of Formidable to version (2.01.01), released MAY 5, 2016.
We have not experienced the issue you have described, in the past month, on the hundreds of installations running the PRO2PDF plugin, including several of our own.
If you have the Pro version of Formidable Forms installed, go to your WordPress Plugins page and deactivate Formidable. Then select ‘Delete’ or go to your web server (via FTP, SSH, SFTP, etc.) and delete the entire formidable folder. If you are using the free version, please delete and reinstall from WordPress.org here. You will not lose any saved forms or entries when you delete Formidable. (from Formidable’s site)
After reinstalling Formidable Forms, please check for the issue again and let us know the results.
If you would also like to reinstall PRO2PDF, be sure to first export your field map layouts before deleting and reinstalling the plugin.
Unfortunately, we have worked on this feature enough to say, this cannot and will not happen based on how Formidable creates and displays graphs and charts. PDFtk (our PDF engine) cannot merge javascript or html.
However, we are constantly looking for ways to integrate with another plugin to merge a saved PDF file into your PDF form, which would also allow us to merge graphs, charts, and even Formidable Views. We started evaluating PrintFriendly this week and we may have some success.
Currently, the only known workaround is to use Acrobat Javascript in the PDF form to create the graph/chart based on the merged data from the Formidable Form.
We remain at your service.
Oh my! Issue was resolved immediately after receiving your notification. Thank you so much for pointing that out!
Our apologies for disconcerting experience, you’re right, it was not on purpose!
Happy reading! We remain at your service.
This is an issue with the WordPress Multisite (WPMU) install. The plugin must be activated on each site locally, and will not work if it is WPMU Network Activated. Deactivate the plugin from the network, and activate the local site installation, then all should work as expected.