We’ve just released Gravity PDF 6.12.6. This update tackles several edge-case bugs, and also improves the system report information you supply when opening a support ticket on GravityPDF.com.
Here are the key highlights of this update:
We fixed potential display issues for the File Upload and List fields in the PDFs.
Rich Text Paragraph fields that include HTML with a lot of CSS class names now use less memory when displayed in PDFs
Prevent a fatal PHP error if Gravity Forms logging is enabled in a read-only filesystem
The PDF Background Processing queue is now flushed whenever the feature is turned off or on
As always, we recommend keeping your plugin updated to avoid potential issues. You can find the full changelog below for all the details.
How to Update Gravity PDF
You can update automatically using WordPress one-click update feature, or download the latest version on GravityPDF.com and manually install.
If you have any questions or need assistance with updating, our friendly support team is happy to help.
Changelog
Housekeeping
- Move Gravity PDF system status information to the bottom of the report
Bugs Fixed
Add additional guards for expected value when displaying File Upload field in PDFs (prevents PHP notice)
Cleanup Background Processing queue when setting is toggled on/off
Add additional guards for expected value when displaying List field in PDFs (prevents PHP notice if the first row in a list is empty)
Ensure Gravity PDF system status information is in English when copied to clipboard
Fix fatal error when Gravity Forms logging is turned on, but the directory where log files are saved is not writable by the web server
Resolve memory problem generating Core PDFs if a Rich Text Paragraph field contains more than 10+ classes (elements with more than 8 classes will have extras removed)
Fix ‘translations loaded too early’ PHP notice if any plugin requirements aren’t met
Pass the filtered ‘use_value’ and ‘use_admin_label’ arguments when determining if the product table is empty
