Drag and Drop
Drag and Drop columns is a new feature in Gravity Forms 2.5 which all Core and the majority of Universal PDF templates support out of the box. That is, the PDFs will automatically display fields in columns to match the form layout.
If you upgrade to Gravity Forms 2.5, all your existing forms will be in Legacy Mode and you have to turn it off to enable Drag and Drop columns.
The primary reason for Drag and Drop columns not working in PDFs (aside from those listed in the Developers section) is your using an outdated template file.
If it's a Universal template, login to your GravityPDF.com account, download the latest version of that template, and reinstall via the Template Manager. If your license has lapsed, you will need to purchase a new one.
If you're using a Core PDF, your template overrides are outdated and don't include the new CSS required to support Gravity Forms 2.5 columns. You can double-check this in the Gravity PDF-section of the System Status page. The solution is to either:
Delete the template override file via the PDF Template Manager. Gravity PDF will then load the new Core template shipped with version 6. Only use this method if you haven't made any direct modifications to the Core template you are deleting.
Using FTP, or your host's File Manager, modify the Core template override file(s) in the PDF Working Directory and add in this new CSS: https://github.com/GravityPDF/gravity-pdf/blob/development/src/templates/zadani.php#L49-L97
If you previously relied on CSS Ready Classes in your form but have since disabled the Legacy Markup setting, Gravity PDF will ignore any CSS Ready Classes in favour of Drag and Drop columns. To fix, you can either enable legacy markup again, or update your form to use drag and drop columns instead.
gf_list_inline CSS Ready Classes are not supported by Gravity PDF.
Due to their design, the following Universal PDFs don't support columns:
Columns are usually enabled by default (depending on the template), but can be disabled through various means:
- Modify a Core/Universal template file and set
$html_config['meta']configuration array. The associated column CSS may also be deleted.
- Use the filter
gfpdf_field_container_classto override the default HTML container wrapper. The associated column CSS in the template may also be deleted. Note: the filter may not be located directly in the template file, and could be added anywhere WordPress hooks are supported.
If any of the above is implemented, you need to rollback those changes to get columns working again in the associated Core/Universal template file(s).