Hi @hamergil
This must be a limitation with eh WYSIWYG javascript.
Thanks for the bug report. I will attempt to find out the issue and fix it.
Thanks
E
Bonjour Ayottepl,
Je constate que tu es français donc j’en profite pour te poser une question puisque j’ai un problème presque similaire : je suis en train de faire ma boutique sur Woocommerce et dans mon cas je voudrais ajouter une seconde description de catégorie tout en bas de mes pages de catégorie.
J’ai donc paramétré un champ Wysiwyg et créé la règle suivante :
Term est égal à Catégories
Dans mon template archive-product.php, j’ai ajouté le code suivant : <?php the_field(‘description_categorie_2’); ?>
L’éditeur Wysiwyg s’affiche parfaitement dans l’admin, je peux éditer mon texte et l’enregistrer sans problème, mais côté front-office rien se passe ! J’avoue que je suis débutante en php et je n’y connais pas grand chose (donc j’ai eu un peu de mal à comprendre comment tu as résolu ton problème :D). Si jamais tu as une idée pour mon problème je t’en serais grandement reconnaissante parce que comme toi je m’arrache les cheveux depuis des jours et des jours….
Bonne journée,
Elsa
Found it! The ACF Plugin folder was missing the JS folder… something must have happened in the transfer. Thanks for your help!
Hi @anagio
Perhaps this question would be better asked to the developer of the field type?
Just to clarify, this is not a core field type, but a 3rd party one.
Thanks
E
Hi @lee@infectiousstudios.com
Sounds like you have a JS error on the page. Please debug the issue via the console log.
You can use this guide to help:
http://www.advancedcustomfields.com/resources/faq/wysiwyg-field-appears-without-toolbar-buttons/
Thanks
E
Hi @eddiehead
This article should help you out:
http://www.advancedcustomfields.com/resources/faq/wysiwyg-field-appears-without-toolbar-buttons/
Thanks
E
Thanks mate.
I’ll add this to the to-do
Yep, that’s the one! I’ve attached a screenshot of the option, just to clarify.
Thanks,
Chris
Interesting! Just to clarify, you are talking about the user specific option to disable Rich Content Editing?
Thanks
E
Hi @aleish76
The remove_filter will not work with the current ACF 4.2.2, but will work with ACF 4.3.0 which you can find in github and will be released shortly.
Thanks
E
Hi Elliot,
It looks like it’s working correctly now. Thanks again for your help and for the quick troubleshooting. This is one of the best plugins for WordPress!
Hi @elliot,
I tried to unhook the filter as rockethouse suggested at the beginning of the conversation and it doesn’t seem to work for me. It should be as easy as putting this: remove_filter( ‘acf_the_content’, ‘wpautop’ ); in my functions.php, isn’t?
No joy though 🙁
Thanks for all your work.
Hi @topdrawinc
Thanks for your help.
I have tracked down the issue and have fixed the WYSIWYG blank issue and pushed to github
Thanks
E
Hi Elliot,
I’m not getting any JS errors in the console log when I edit a post where the WYSIWYG fields fail. Are you seeing the same behaviour on your end?
Thanks for your help!
Hi, new code fixes the problem… My custom role had the depreciated user_level capability missing. $role->add_cap( ‘level_1’ ); fixed the problem.
However I noticed that with the new code, WYSIWYG fields in both front-end and back-end show as empty. The field is being saved but the WYSIWYG field is being rendered as empty.
Thanks!
Hi @topdrawinc
Can you please open your console log and report any JS errors on the edit page where your WYSIWYG fields fail?
Thanks
E
Hi @ildaniel8
You can load the value without any formating like so:
the_field($field_name, false, false);
You can read-up on the docs if you wish, but the 2 false params will prevent formatting.
Thanks
E
Thanks again for the quick response. Unfortunately, I’m still having an issue with this. I downloaded the code from GitHub and tried it, and now all WYSIWYG fields are showing as blank when I load a post to edit it.
The existing data is still being saved, because the data is there when the edit post screen is loading. As soon as the WYSIWYG editor loads, everything disappears. I couldn’t test the drag and dropping since there is no data in the fields.
Can you please take a further look?
Thanks!
Used the WP WYSIWYG Plugin and it solved my issue.
Two birds with one stone really!
Hi @topdrawinc
Just fixed this today. You will find the fix in the latest code on github
Thanks again for the bug report.
Cheers
E
Hi @tomjhume
Can you open your console log and report any JS errors during the ‘add image to WYSIWYG’ proccess?
Thanks
E
Weird. Can’t replicate it anymore. Well, I’ll let you know if I can nail it down again.
Hi elliot,
Thanks for the quick response! I’m looking forward to the fix for this issue.
Cheers!
Just tested this out and got the same issue!
I’ll add this to the to-do
Hi @topdrawinc
Thanks for the bug report.
This should not be happening, as there is specific code to fix this.
What version of ACF + repeater are you using?
Thanks
E
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 Privacy Policy. If you continue to use this site, you consent to our use of cookies.