Forms: 3rd-Party File Attachments
Exposes file upload/attachments to the regular service mapping of Forms 3rdparty Integration . From discussion at https://github.com/zaus/forms-3rdparty-integration/issues/40.
Exposes file upload/attachments to the regular service mapping of Forms 3rdparty Integration .
From discussion at https://github.com/zaus/forms-3rdparty-integration/issues/40.
- 01Unzip, upload plugin folder to your plugins directory ( /wp-content/plugins/ )
- 02Make sure Forms 3rdparty Integration is installed and settings have been saved at least once.
- 03Activate plugin
- 04Choose how the files will be attached — either: as server path
- 05as url
- 06as base64-encoded bytes
- 07as raw contents
- 08Map to the desired file detail, where “[field]” is the corresponding input field name as you would normally map: [field] — the filename
- 09[field]_attach — the transformed attachment from the previous step
- 10[field]_mime — the file’s actual mime-type
- 11[field]_size — the file size
Frequently asked questions.
How do I perform the appropriate transforms in custom hooks
Using F3i_Files_Base::Transform($value, $how) where $how is: * path * url * base64 * raw
Gravity Forms input ids cause conflicts
Use the ‘label’ option to instead reference file uploads via the field label. You can also set the Advanced > Admin Field Label to use a shorter/non-display label than what users see on the form.
ex) If your upload field input_5 has a very long label “Choose one or more files blah blah blah” you would reference details like Choose one or more files blah blah blah_attach unless you set an admin label like “FileUpload”, in which case you’d map to FileUpload_attach . You can also use this to attach to different upload fields across forms — normally they might not be able to share the input_id, but if you give them the same admin field label then you only need to map the service once to that admin label.
