Pre-existing field group missing fields with ACFE enabled

Hello,

Thanks for the feedback!

What you experience is not the normal behavior. I would suspect some conflict with a custom code/hook in your theme or third party plugin. Looking at your UI screenshot, it seems like there something weird going on in a Sub Field of your Header JS / jQuery repeater.

Note that you can see the faulty JS code by clicking on the link in the console error '[' (at post.php?post=23196&action=edit:4400:21).

Regarding the admin-ajax request sending 403 (Forbidden) , this isn’t normal either. I don’t know if it is related to the JS error above, but it suggests you have some PHP errors breaking the Ajax request. I would recommend to enable the WP_DEBUG & WP_DEBUG_LOG constants in your wp-config.php file to check your PHP errors.

You can read more about how to setup a favorable environment for debugging WordPress & ACF in our guide here.

In order to quickly isolate the issue, I would recommend clone your website on a development / staging environment using Duplicator, or your hosting backup solution. Then try to disable all your plugins one-by-one (at the exception of ACF Pro & ACF Extended) until you find which one cause the issue.

If the problem persists, try switch to the native WP Twenty Twenty Two theme, to make sure you don’t have any custom code in your theme which would break the feature.

Let me know if you found something!

Regards.

Ok, it took a while but think I got it. I guess ACFE doesn’t like certain characters in the placeholder text.? This was the placeholder text for two of the subfields. The first line causes the failure, the second line works:

Hello!

Good job tracking down the issue!

What Field Type was it? So I can check it out.

Edit: Okay I managed to reproduce it. Entering this tag in placeholder/default value setting in Textarea/Code Editor will throw JS error and break the page output.

The issue come from to the “Data” feature. It’s the “Data” button added at the bottom of each field settings (next to “Close Field” button, which allow developers to see the field configuration/array).

It’s only reproducible in sub fields tho (repeater/group), top-level fields aren’t concerned. Please allow me some time to tackle that issue down. I’ll come back to you later.

In the meantime, please remove the <script> tag from these fields placeholder/default value.

Thanks!

Never mind, spoke too soon.

I don’t think you have to worry about this field. I was using the “other” code field that no longer exists (it’s one of the reasons I was checking out your plugin).

Thanks for your help.

• This reply was modified 1 year, 4 months ago by PthPndr.