Support

Account

Home Forums Search Search Results for 'Wysiwyg'

Search Results for 'Wysiwyg'

reply

  • It’s happening with all plugins disabled as well, even if I remove the wysiwyg sub-field, but without js errors. I’ll do some debugging in the next few days and get back to you.

  • Hi @Bondra

    Thanks.

    It is possible that the shortcode plugin is only made to insert into the main WYSIWYG editor. I would contact the shortcode developer and ask them if the plugin is compatible with ACF or any extra WYSIWYG editors on the page.

    Thanks
    E

  • Hi @mountainthemes

    What do you mean by ‘display this syntax highlighter inside the wysiwyg textarea output’?

    Thanks
    E

  • Hi @mlohscheidt

    I’m not sure I understand the issue.
    The have_rows function will load the repeater field’s data and check that there are rows available. The WYSIWYG sub field values will also be loaded, and the values will be formatted (shortcodes will be run).

    Perhaps the issue is with your shortcodes. Normally, a shortcode filter would modify the content, not echo out some HTML.

    Is it possible that you can change your shortcode filters to return the value instead of outputting it?

    Thanks
    E

  • Heya!

    This is the output:

    acf.fields.wysiwyg.toolbars = {
        "full": {
            "theme_advanced_buttons1": "bold,italic,strikethrough,bullist,numlist,blockquote,justifyleft,justifycenter,justifyright,link,unlink,wp_more,AtD,fullscreen,wp_adv",
            "theme_advanced_buttons2": "formatselect,underline,justifyfull,forecolor,pasteword,removeformat,charmap,outdent,indent,undo,redo,wp_help,code",
            "theme_advanced_buttons3": "",
            "theme_advanced_buttons4": ""
        },
        "basic": {
            "theme_advanced_buttons1": "bold,italic,underline,blockquote,strikethrough,bullist,numlist,justifyleft,justifycenter,justifyright,undo,redo,link,unlink,fullscreen"
        }
    };
  • Thanks too Elliot!!! I was trying and searching the forums across the net for a solution for my hassle about a custom excerpt function for a acf wysiwg field for weeks. The combination of add_filter(‘acf_the_content’, ‘wpautop’); and
    the_field(‘wysiwyg_field’, false, false); saved me. Drove me crazy 😀

  • Hi Elliot,

    Maybe editor wasn’t the right word, because visual composer is more a page builder, but I would like similar functionalities within a Advanced custom field like for example the wysiwyg field.

    My client doesn’t like (and doesn’t know how) to work with shortcodes and it would be nice to have the ability to drag and drop to make, for example, two text columns.

    Regards,

    Joeri.

  • Steps to reproduce

    1. Add multiple wysiwyg fields to a post type via ACF
    2. Edit post
    3. Put some content into the main content field
    4. Click on full screen mode in one of the custom wysiwyg fields
    5. Put some different content in full screen mode (in the custom wysiwyg)
    6. Click on full screen mode button again to go back to normal mode
    7. Behold the custom wysiwyg content you just added replace the main content field
  • Hi @Bondra

    The normal WP WYSIWYG is not availing in ACF due to limitations within the repeater field.

    If you are using the WYSIWYG field OUTSIDE of a repeater field / flexible content field, you can install an add-on I created that uses the WP WYSIWYG and offers the native visual / text tabs:
    http://www.advancedcustomfields.com/add-ons/wordpress-wysiwyg/

    Thanks
    E

  • Hi @Till

    Thanks for the info.

    For some reason, your toolbars are not being added to the wysiwyg JS object. Normally, an array of toolbars will exist at acf.fields.wysiwyg.toolbars (this.toolbars).

    On line 115 of core/controllers/input.php you will see:
    acf.fields.wysiwyg.toolbars = <?php echo json_encode( $t ); ?>;

    It is possible that this line of script is not being run due to a JS error on the page. Can you check for any JS errors?

    Perhaps also do some PHP debugging to make sure line 115 is correct data?

    Thanks
    E

  • Sure! See below. Need anything else?

    this.toolbars: undefined

    this.o:

    {
        id: "wysiwyg-acf-field-field_52ba5d6289438_0_field_52ba64a564a1b-52fd8bc9b44f6"
        toolbar: "full"
        upload: "no"
        __proto__: Object
    }
  • Hi @Till

    Thanks for the bug report. The full line is:
    if( acf.helpers.isset( this.toolbars[ this.o.toolbar ] ) )

    And it looks like the isset function is not working as per expected.

    Is it possible that your WYSIWYG field contains a ‘toolbar’ setting that does not exist anymore?

    Thanks
    E

  • Hi @richardsweeney

    Thanks for the info but I am still unable to replicate this issue on my end running the latest WP, ACF and repeater field. How are you with JS debugging? Are you able to look through the input.min file (search for the WYSIWYG part) and do some testing there.


    @tomfordweb
    – did you have any luck tracking down the issue?

    Thanks
    E

  • I’m having the same issue. I’m running WP 3.8.1, ACF 4.3.4 + Repeater Field 1.1.1. No console errors. The add media button appears (and works!) but no WYSIWYG.

    I’ve deactivated all plugins and reactivated only ACF + repeater. No change.

    WordPress is installed in a subdirectory, but that’s nothing new I guess.

    I’ve noticed problems on some other of my sites too. Did they already switch to Tiny MCE 4.0 in 3.8.1? Might that be causing the problem. I know the API has changed…

  • This reply has been marked as private.
  • Hi @flowbob

    It is most likely that you have a plugin which is adding the lightbox effect to WYSIWYG galleries. Is this correct?

    if so, all you will need to do is pass the ACF value through the the_content filter – this is how a plugin would modify the_content value.

    <?php 
    
    $wysiwyg = get_field('field_name', false, false);
    
    echo apply_filters('the_content', $wysiwyg);
    
     ?>

    Please note the extra false, false parameters are to prevent ACF from formatting the value because the_content will also do this.

    Thanks
    E

  • I’m having the same problem–the main content is being replaced with a WYSIWYG field. I have 3 custom WYSIWYG fields, using both Basic and Full toolbar, none of which allow images. Seems to be the same situation for me — the replacement happens after editing and updating the WYSIWYG in full screen mode. Will try to verify a pattern as well.

  • I found this previous post:
    http://support.advancedcustomfields.com/forums/topic/wysiwyg-field-showing-as-textarea/

    I’m going to give this a try and report back.

  • Hi @tomjhume

    The WYSIWYG field uses a filter called acf_the_content. It is much the same as the_content

    Thanks
    E

  • Hi @Coug

    ACF does create a hidden ‘WYSIWYG’ field in the wp_footer. You can will see a hidden div at the bottom of the page. If you change the display property of this div, you can then see the WYSIWYG field.

    Can you check to see if the image is being inserted into this field?

    Thanks
    E

  • The problem is that i’m not only getting image URLs, i’ve got a field with a WYSIWYG editor which gives me all kinds of content, so i can’t hardcode it in my template :/

  • Thanks Elliot. Maybe a feature for the future?

    Sure, a WYSIWYG field would work…though it’s a bit heavy-handed just to insert an image. You mention I might need to add another field to allow for custom size selection. Any chance you can steer me in the right direction for how to do that?

    Thanks as always for your amazing work and awesome support.

  • Hi @dadra

    I do agree, however, the image field only saves the attachment ID and no other data.

    You may need to add another field to allow for a custom size selection, or use a WYSIWYG field to insert the image with such data.

    Thanks
    E

  • Indeed, it appears the ACF Location Field add-on has a conflict…
    Deactivated everything but when i activate ACF Location Field, the WYSIWYG appears with no toolbar and the following text which i didn’t ever type:

    <p><br data-mce-bogus=”1″></p>

    Google Map Field (which i only recently realised was added) seems to be a replacement for the older ACF Location Field anyway, so maybe this isn’t a big issue.

  • I did so. Still no errors. I made a screenshot. The field in the middle should be a wysiwyg.

    ACF WYSIWYG

Viewing 25 results - 976 through 1,000 (of 1,305 total)