Prismatic Plugin conflicts with ACF plugin Code

Glad to help. I don’t know if there is a fix or not, as I do not use ACF on any sites. But I would be glad to investigate if you want to provide steps to repeat the issue on *default* WP setup. That way I can follow along locally and see what’s happening, etc. Please send fewest possible steps and keep them as simple as possible. Something like:

1) Activate only Prismatic and ACF
2) Visit the plugin settings or whatever
3) Perform some task or action, etc.
4) Etc., until the issue appears

Let me know if any questions about this.

In the meantime, if you need to restore previous functionality, you can roll back to the previous version of Prismatic.

Thank you for reply!

Here are the steps which we have followed to arise this issue.

1) Activate only Prismatic and ACF PRO
2) Create custom block for any page using ACF PRO.
Please see this URL for reference.
https://www.advancedcustomfields.com/resources/blocks/

3) with Prismatic 2.7 all pages were rendering all blocks correctly but after updating plugin It started showing me HTML text. Please see below URL.
https://technicalsupp.wpengine.com/download/

Let me know in case you need more information from my side.

Thanks in advance!

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

Hey thanks! Do the steps work with free version of ACF? I don’t have ACF Pro to test with.

I don’t think so because only ACF pro plugin provides us Custom block types.

Please let me know what I can do for you to move forward to fix this issue.

Thanks

Basically I can’t support pro plugins. All the work I do for Prismatic is free. I make exactly zero dollars from this plugin. If the issue happens with literally any free plugin I can investigate and try to resolve. That’s not possible for paid/pro plugins.

Update: I *think* this issue is resolved in the next version (2.9) of Prismatic. I have not tested with ACF Pro, but I think the ACF conflict was related to the 2.8 code-escaping bug. Now that that issue is resolved should also resolve the issue reported above. Please test with the next version of the plugin and let me know the results. Thank you, @vandnakapoo.