@elliot Please consider adding this as it is now more important than ever with the ability to create blocks. “Add to Gallery” is just too confusing for some clients when a given custom block is called something else (eg. Slider).
You can also check this new plugin https://wordpress.org/plugins/acf-flexible-layouts-manager/ which is really awesome and do exactly what you need, I guess.
Best,
I have two different collations in my DB. Should I use the same? Which is the best collation to use?
I don’t use to change this and in general all my WordPress are working fine…
Hi @jonathan,
My collation is utf8_general_ci. Could it give any problems? I use to work with it as my server’s WP auto install set this collation by default. I can’t see utf8mb4 you mention in the dropdown.
Thanks
I uninstalled and removed ACF. I tried this with a previous version of ACF and this don’t work. After updating to the latest version still not working. Also, I tried to create another WYSIWYG field with different name and doesn’t work either.
Yes, in main post content editor this works fine. It only happens in WYSIWYG editor of my ACF’s field 🙁
Yes, I have WordPress latest version too.
I already had debug enabled and no error appear when I save the post. With debug disabled it happen the same. Thanks
Hi Jonathan,
I tested it with twentyfifteen and only ACF Pro 5.2.8 enabled and it’s still removing all my content when I try to save a WYSIWYG field. Any ideas of how can we debug this?
Thanks
Yes, they are built in from 4.2. You can try copy/pasting one emoji from here https://codex.wordpress.org/Emoji
Hi @jonathan
The whole thing gets removed when I save the input with emojis. If I try to save the input without emojis everything works fine.
Thanks
Same here, if I have my WordPress installation in Spanish and I add fields in English some of them are automatically translated. I deduce that this translations come from WordPress main PO language because only common words are translated. Is it possible to avoid this?
Same here. The strange thing in my case is that it’s only affecting in one repeater. I have two repeaters in different flexible content fields and only one of them stopped working.
This was working fine before the update. Now, after rolling back to 5.0.9, this working fine again…
Hi @jacobdubail,
I had the same error in my backend, but I realized that in my case the problem was due to Location Map field add-on. With this add-on activated, Google Map field was not working fine.
I migrated my Location Map fields to the new Google Map field and then deactivated Location Map add-on. Now, my maps are working fine.
Hope this helps!
Hi,
I have some questions about the integration of ACF and WPML. I’m a theme developer and I would want both plugins to integrate perfectly.
Translation management let’s us configure WPML to choose if we want to translate ACF’s custom fields or not. Also, it’s possible to include an XML file with the theme to tell the theme what to do in each case automatically.
In the translation management table, I can found field_name and field_key (with underscore) values. I understand what field_key does, but I’m not sure if we need the field_key values to be copied or not from one post to it’s translation. Any one can clarify me this point?
Thanks!
Welcome to the Advanced Custom Fields community forum.
Browse through ideas, snippets of code, questions and answers between fellow ACF users
Helping others is a great way to earn karma, gain badges and help ACF development!
We use cookies to offer you a better browsing experience, analyze site traffic and personalize content. Read about how we use cookies and how you can control them in our Cookie Policy. If you continue to use this site, you consent to our use of cookies.