If the "Enable Markdown in HTML Fields" option in the pod-feed settings page is enabled, loading the GF form will result in a critical error. This is true even if there are no HTML fields actually configured.
I am including below a toy configuration that produces this behavior.
Expected Behavior
No errors.
Current Behavior
Loading a page containing the referenced GF form produces a critical error. In some conditions, I get a more verbose result:
Warning: Undefined variable $ajax in /Users/adamrice/Local Sites/burn-after-meeting/app/public/wp-content/plugins/pods-gravity-forms/includes/Pods_GF.php on line 4162
Fatal error: Array and string offset access syntax with curly braces is no longer supported in /Users/adamrice/Local Sites/burn-after-meeting/app/public/wp-content/plugins/pods-gravity-forms/includes/Markdown.php on line 1104
Possible Solution
???
Steps to Reproduce (for bugs)
Create a Pods data type
Create a GF form
Create a feed to connect the data type and form; check the "Enable Markdown in HTML Fields" option
Load a page containing the form or preview it from the GF admin page.
Form Upload
```
{"0":{"fields":[{"type":"text","id":1,"formId":1,"label":"Playa name","adminLabel":"","isRequired":false,"size":"large","errorMessage":"","visibility":"visible","inputs":null,"description":"","allowsPrepopulate":false,"inputMask":false,"inputMaskValue":"","inputMaskIsCustom":false,"maxLength":"","labelPlacement":"","descriptionPlacement":"","subLabelPlacement":"","placeholder":"","cssClass":"","inputName":"","noDuplicates":false,"defaultValue":"","enableAutocomplete":false,"autocompleteAttribute":"","choices":"","conditionalLogic":"","productField":"","layoutGridColumnSpan":"","enablePasswordInput":"","enableEnhancedUI":0,"layoutGroupId":"1d981780","multipleFiles":false,"maxFiles":"","calculationFormula":"","calculationRounding":"","enableCalculation":"","disableQuantity":false,"displayAllCategories":false,"useRichTextEditor":false,"errors":[],"fields":""}],"button":{"type":"text","text":"","imageUrl":"","width":"auto","location":"bottom","layoutGridColumnSpan":12},"title":"profile","description":"","version":"2.8.5","id":1,"markupVersion":2,"nextFieldId":3,"useCurrentUserAsAuthor":true,"postContentTemplateEnabled":false,"postTitleTemplateEnabled":false,"postTitleTemplate":"","postContentTemplate":"","lastPageButton":null,"pagination":null,"firstPageCssClass":null,"confirmations":[{"id":"65ee1fd0ec3ae","name":"Default Confirmation","isDefault":true,"type":"message","message":"Thanks for contacting us! We will get in touch with you shortly.","url":"","pageId":"","queryString":""}],"notifications":[{"id":"65ee1fd0ebe17","isActive":true,"to":"{admin_email}","name":"Admin Notification","event":"form_submission","toType":"email","subject":"New submission from {form_title}","message":"{all_fields}"}],"feeds":{"pods-gravity-forms":[{"id":"1","form_id":"1","is_active":"1","feed_order":"0","meta":{"feedName":"Pods Feed 1","pod":"user","custom_fields":[{"key":"","custom_key":"","value":"","custom_value":""}],"update_pod_item":"1","enable_markdown":"1","enable_current_user":"1","enable_prepopulate":"1","delete_entry":"0","feed_condition_conditional_logic_object":[],"feed_condition_conditional_logic":"0","pod_fields_event_year":"","pod_fields_playa_name":1,"wp_object_fields_user_login":"","wp_object_fields_user_nicename":"","wp_object_fields_display_name":"","wp_object_fields_user_pass":"","wp_object_fields_user_email":"","wp_object_fields_user_url":"","wp_object_fields_user_registered":"","feed_condition":""},"addon_slug":"pods-gravity-forms","event_type":null}]}},"version":"2.8.5"}
```
Issue Overview
If the "Enable Markdown in HTML Fields" option in the pod-feed settings page is enabled, loading the GF form will result in a critical error. This is true even if there are no HTML fields actually configured.
I am including below a toy configuration that produces this behavior.
Expected Behavior
No errors.
Current Behavior
Loading a page containing the referenced GF form produces a critical error. In some conditions, I get a more verbose result:
Possible Solution
???
Steps to Reproduce (for bugs)
Form Upload
Pods Package Export
Related Issues and/or PRs
Todos
WordPress Environment