2.8 Breaks Front End Rendering of ACF/Gutenberg Blocks

Looking at the changelog and prismatic-core.php, it seems the new decode style that is being implemented (“Improves escaping of code content”) is likely the culprit and escaping the HTML comments that initialize the ACF Blocks. Turning on wp_debug offered no assistance, since it’s not technically erroring out but rather escaping and not executing the actual block code.

As an aside, if this helps, the blocks render/preview just fine within the dashboard, it’s only when viewing it on the front end of the site.

• This reply was modified 3 years, 5 months ago by Chee Studio.

Thanks for reporting this, definitely want to get it fixed up asap. In order to do so, I need you to provide the steps to recreate the issue on *default* WordPress install. So once ACF and Prismatic both are active (and no other plugins), what are the steps to recreate the issue?

OK I just did a totally vanilla install and was able to re-create the issue. It stems particuarly when using the ACF WYSIWYG (which makes sense). Other fields do not seem to be affected. I noticed this since the blocks that were galleries or a collection of other fields without WYSIWYG fields, were working fine. To recreate:

1) Follow this guide in registering a custom ACF block –

https://www.advancedcustomfields.com/resources/blocks/

(OR)

https://www.advancedcustomfields.com/resources/acf_register_block_type/

2) Create a WYSIWYG field, go add the new block to a page and populate it with some test content

3) Load the page and you’ll see the escaped content being rendered, rather than the block markup/content.

Alright will go thru all of that next opportunity. Thank you again for reporting, please let me know if any related infos, etc.

If it helps in the exploration of this issue, we’re also finding that the latest update to Prismatic is mangling code added via the Divi Builder plugin (within Divi’s ‘code’ module). We rolled back to 2.7 and the issue was no longer present.

@copernicus Thanks. Hopefully resolving the ACF issue also will resolve the Divi issue, so that’s where I will focus my efforts for now. If you or anyone wants to provide steps to recreate the Divi issue on *default* WordPress, I will be glad to investigate as well.

Hi @specialk – I am having similar issues as @chee-studio. When do you expect this to be fixed?

@daniellelake

Not sure, I try to update my plugins for each major WordPress release (e.g., 5.7, 5.8, etc.). So should be soon, depending on 5.8 release.

• This reply was modified 3 years, 5 months ago by Jeff Starr.

Update: I *think* this issue is resolved in the next version (2.9) of Prismatic. Please test with the next version of the plugin and let me know the results. Thank you, @chee-studio, @copernicus, and @daniellelake for reporting.

@specialk YES – regarding the issue with the Prismatic plugin interfering with code added via the Divi Builder’s “Code” module – the new version solves/fixes that.

Thank you!

• This reply was modified 3 years, 4 months ago by Copernicus.

Ah that’s great news, thanks for letting me know @copernicus.

@specialk Gutenberg/Block issue has been resolved, as well! THANK YOU!

Although I am very curious as to what it was… ??

@chee-studio You’re very welcome, thank you for reporting back. Basically the issue came down to unintended double-escaping of code output. Certain characters getting escaped twice was breaking layout and other issues on the front-end.

But all that’s behind us now, thanks to help from you and others ??

Hey, thank YOU, Jeff, for maintaining such a great plugin and being so darn responsive.