Shortcode error on all views in gutenberg

Hi @bchpdigital

Can you confirm that you’re running the latest version which is 3.0.3 ?

Yes the error only occurs when un 3.0.3
When rolling back to 2.4.7 the error does not occur

Hi @bchpdigital

Okay, thank you for confirming.
Can you please tell me more about your WP setup, like what other plugins are active, which theme you currently have active and perhaps (if possible) provide a copy of your log file with lines that contain acf views ?

Hi @bchpdigital

We’ve released a new version this week, please update and see if your issue is resolved.

We’re closing this ticket for now, as there’s been no reply in a while.
Feel free to write if you still need help.

Hi, the changes fixed the red error code from appearing. However, the now the fields just appear blank.
My custom templates are loading, so the other styling and other static content is loading correctly. However, any fields with {{ }} are not loading into the front end.

I believe it might be down to the ACF Field Group fields.
So, not the ACF Field Groups, but the “Group” field type within that.
I have lots of data within these groups, and since the update, these are not appearing front end, and I assume they were causing the errors.

I’m not sure if it will let me share a link here.
I have kept the broken site version on my stg here:
https://bchp24stg.wpenginepowered.com/holidays/camping-holidays/grass-tent-pitch-4/

There should be values loading in by “Check In”, “Check Out” and “seasons end”.
As you can see, the “per night from” value is still correctly loading, as this is NOT in an ACF group field.

Hi @bchpdigital

We’re glad to hear the error was resolved.

Regarding your ‘Group’ field type not showing.
Display of ‘Group’ and ‘Repeater’ field types is only possible with a Licensed Advanced Pro plugin.
If you’re using a Licensed Pro version, and the problem persists, then please contact support.

Thank you

Yes, this is with the pro version. It was working fine up until these updates. Rolling back the plugin updates does solve the issue. I didn’t change anything on my end. I shall use the form.