Still no answer? This puzzles me, support was always great with ACF Pro.
WPML has released a minor update to address this issue. It did so, partly. We get no longer that JSON-like stuff and the “Array array” output.
But: Changing fields in one language messes up fields in another language. I’m not sure what role ACF or the bridge plugin plays in that regard, but it’s a complete mess, a nightmare so to speak.
I’m really reaching out to the ACF team for some insight on this.
Cheers.
Any updates on the topic? We had to roll back plugin versions and lost quite some data. Not sure when we can get back into regular upgrade path and how to deal with the issue in general. Corresponding request send to WPML.
Note: After reading another recent bug, I’ll have to add:
this JSON-like data in the fields also has escaped quotes, didn’t copy it correctly cause I wasn’t aware it mattered.
[\”_wp_page_template_default\”:\”default\”,\”_edit_lock\”:\”123456…\”
Luckily I was able to figure it out this morning. For whatever reason WPML + ACF Pro needs a wopping 1GB of PHP memory limit with all accompanying settings upped to infinity (PHP / Apache / nginx timeouts etc.)
But then it works. Most of the time.
This doesn’t work at all. I found that even ex- / importing field groups, without touching / manipulating the JSON file, results in WordPress throwing an error message, field groups missing all together, and a messed up database.
What a mess, WPML is such a piece of crap. Open for suggestions.
As it still is a top result in Google:
The original code still works for the most part. What throws an error is this line:
function my_acf_upload_prefilter( $errors, $file, $field ) {
WordPress expects one parameter only here, so do this instead:
function my_acf_upload_prefilter( $file ) {
Same boat as OP. 3 big projects are currently in development with the rushed GB release suddenly surfacing. Not sure where to go – GB is “controversial” to say the least. Will WP even continue using it as it’s editor?
Also I cannot relate on the statement that GB better reflects a website’s content structure. True for blog posts, false for all other types. This single-column / stripe-like style of content doesn’t fit for any website I’ve seen other than a blog post. All websites I know use content in a 2D (dimensional) fashion, remember CSS Grid?
On top GB output goes against ALL best-practices in web development. WP isn’t a web app, not sure why they try to push it there, makes no sense to me. Makes no sense for SEO. Ask React-guys about SEO and they mumble “Google erm can search JS…” and run away.
My conclusion: I’m going with the classic editor and the modular approach that we’ve developed using ACF Pro (best WP Plugin on the planet). Funny enough, we’ve been using that block-style template structure on the PHP side for years, even called them blocks. Each ACF area has it’s own blocks/content-block-xy.php.
Sorry for the late reply – this worked perfectly, many thanks for your quick help!
