WordPress.org

Ready to get started?Download WordPress

Forums

Advanced Custom Fields
WYSIWYG Editor and Saving broken w/ 3.3 and 3.0.6 (15 posts)

  1. Bryce Corkins
    Member
    Posted 3 years ago #

    The buttons for the WYSWYG editors no longer load. If I switch the wordpress editor to HTML, sometimes one set of buttons will load, but I'm using multiple WYSWYG editors on my post-edit page and so this isn't very useful either.

    As well, any data I type into the WYSWYG editor is immediately lost when the post is saved.

    We're using ACF as a core component of a site that's supposed to launch January 1st, so if there's any way we could get a fix before then I'd be incredibly grateful.

    http://wordpress.org/extend/plugins/advanced-custom-fields/

  2. tydende
    Member
    Posted 3 years ago #

    hi sekatsim,

    i'm having the same issue with ANY custom fields plugins and wp 3.3

    see here
    http://wordpress.org/support/topic/more-fields-21-incompatible-with-wp-33?replies=22

    if you find a solution, please let me know and i'll do the same

  3. tydende
    Member
    Posted 3 years ago #

  4. Bryce Corkins
    Member
    Posted 3 years ago #

    So I guess we just wait then?

  5. tydende
    Member
    Posted 3 years ago #

  6. tydende
    Member
    Posted 3 years ago #

    try renaming the file wp-includes/js/tinymce/langs/wp-langs-en.js to en.js

    works for me

  7. Bryce Corkins
    Member
    Posted 3 years ago #

    Not working for me.. but it may be complicated by the fact that I'm using a custom post type with multiple WYSIWYG editors on the page. I'll keep an eye on that thread... hopefully someone else can resolve it while he's on vacation.

  8. managenet
    Member
    Posted 3 years ago #

    Maybe others know this already, but double check one thing that helped me - WordPress remembers the last selection of the 'Visual' and 'HTML' tabs on the main editor. The admin page with custom fields WYSIWYG editor only displays the WYSIWYG controls if the 'Visual' tab is selected on the default editor. Try and select 'Visual' tab and reload the page

  9. ambienthack
    Member
    Posted 3 years ago #

    In my case ACF broke standard WYSIWYG editor, but WYSIWYGs of custom fields worked fine.

    For me the solution was to add one line in advanced-custom-fields/core/fields/wysiwyg.php.

    After line -> $(this).find('.acf_wysiwyg textarea').each(function(){
    Add -> if ($(this).filter(':hidden').lenght) return;

  10. kjparish
    Member
    Posted 3 years ago #

    OK, Ambienthack's solution seemed to work for about a minute but now it's back to the same problem for me. I am seeing duplicated WYSIWG editors on every post page (I did not add a second one, so this is some kind of phantom editor).

  11. RevConcept
    Member
    Posted 3 years ago #

    I don't have the toolbar issue...I do have duplicates of the default WYSIWYG elements. The workaround has been "hiding" the default and adding a WYSIWYG from ACF. Fine for now...

    However, just realized today when I was walking my client through using the system that "save draft" deletes all of the ACF WYSIWYG content upon page refresh. Ahhhrrggg!

    "Publishing" and "Updating" don't seem to have issues. Just drafts.

    Please help!

  12. elliotcondon
    Member
    Plugin Author

    Posted 2 years ago #

  13. RevConcept
    Member
    Posted 2 years ago #

    This issue was corrected with the most recent version of the plugin. I updated mine and it's been fine since.

  14. Bryce Corkins
    Member
    Posted 2 years ago #

    Still broken for me. This is ridiculous. I've got a project that's been basically dead in the water for five months because I can't put more than one WYSIWYG editor on a page. Shouldn't this be a priority to the developers?

  15. tonywebster
    Member
    Posted 2 years ago #

    This issue has resurfaced for me in ACF 3.5.0, and updating to 3.5.1 didn't fix it. Any ACF WYSIWYG field in the WordPress page editor shows up as raw HTML with no WYSIWYG buttons above the field. While creating a site, everything was loading just fine, and suddenly this issue surfaced. The ACF configuration shows the fields should be WYSIWYG fields. Any assistance would be most appreciated!

    Advanced Custom Fields 3.5.1
    WordPress 3.4.2
    Firefox 16.0.2 and Chrome 24 on OS X 10.8.2

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic