Until now I was using ACF PRO without any problem. I did a general update last week-end and had a “critic error” on most of my sites. After checking, I thought it was due to ACF PRO, but, today, I had more time and I tested plugin after plugin on a small installation for seeing if it was not an incompatibility with another plugin. And I found Cwicly.
I tested in local on a fresh instal and everything worked well.
So, I passed “debug” on true for one online site and had the following fatal error:
Fatal error : Uncaught Error: Class “Cwicly\ACF” not found in /home/shadows/noir-et-blanc.photos/wp-content/plugins/cwicly/core/includes/dynamic/render.php:1136
Now, I changed the debug to false and ACF is deactivated
I just want to add when addressing this bug - that I am also receiving this “Uncaught Error: Class “Cwicly\ACF” not found” on my site - and deactivating the ACF Pro plugin does resolve the issue. However, my ACF Blocks no longer work when ACF Pro is deactivated.
When addressing this bug and testing - can the team make sure that ACF Blocks work again as part of the resolution?
You can potentially do it the other way around. If you have an ACF Pro license and have that installed on your site, you can disable the bundled ACF Pro in Cwicly setting the CWICLY_ACF constant to false as mentioned by Louis:
Thanks. I was mistaken. I was using ACF Extended for ACF Blocks and did not realize I could have this plugin activated without my ACF Pro Plugin. I tried activating only that plugin and it now works with the Cwicly bundled version (and my ACF blocks appear and I do not get the Uncaught Error).
Regarding your comment about the CWICLY_ACF constant being set to FALSE - I did see this thread this morning and never could get this to resolve the error I was receiving for the “Uncaught Error: Class “Cwicly\ACF” not found”. Tried quite a few times and never worked for me.