Support

Account

Register Login

Home › Forums › Search › Search Results for 'Wysiwyg'

Search Results for 'Wysiwyg'

reply

  • Thanks John.

    I’m using the latest version of pro.

    I was calling acf_form outside the loop as far as im aware. Its a strange one. If I call acf_form() with an empty array, it displays the the fields on the page with a the contents correctly. But when I try and pick out the wysiwyg specifically, the form displays the editor but its contents are empty.

    Having said that, there was an important bit of info I forgot to provide: Im running wordpress on a localhost using wamp. Does this have any bearing on how acf_form works?

  • What version of ACF are you using? I just did a test and when I include a wysiwyg field in acf_form() that is a sub field of a repeater and the content added in the back end is shown in the front end.

    Or it may be because you’re trying to show the form in the loop that’s getting the field keys. Try storing all the field keys in an array and then use a single acf_form() call to display all of the fields.

  • Hi @soojooko

    Thanks for the bug report and very clear explanation!

    The issue here is due to a ‘some what’ miss-use of the conditional logic functionality.

    If a field is hidden by conditional logic, ACF will not save it’s value when the form is submitted. This is why the hidden fields do not update correctly, and why a new field simply overrides existing data.

    I think you may be interested in the flexible content field. You can use it in the same way as a repeater, however, each ‘layout’ is collapsible. This means you can minimize the interface and toggle open/close the WYSIWYG editors without using conditional logic.

    Thanks
    E

  • To be honest, I don’t know why it’s not stripping the <p> tags of when they aren’t in tabs. Does the same thing for me but this is the default operation of the WP WYSIWYG editor.

    I use TinyMCE Advanded on all my sites, one of its features is to stop this from happening.

  • Hi all, a year and a half later, I’m weighing in to add one bit of advice that worked for me:

    I kept getting </div></p> and similar phantom paragraph tags whenever I used shortcodes in an ACF WYSIWYG field. I extended @jt-mtl’s add_filter solution a bit and it worked for me. 

    $array = array (
    '<p>[' => '[',
    ']</p>' => ']',
    ']<br />' => ']',
    '<p><div' => '[',
    '</div></p>' => ']',
    '</div><br />' => ']'
);

    You could add any other markup to the array if you want to. Divs were all I needed, so I stopped there. Hope it helps!

  • Hi @donpro

    In order to make use of some of the ACF 4 Custom fields you have to purchase the related add on. For instance the Flexible Content Field but as for the WYSIWYG field it is available for use and you should check to ensure that there is no plugin conflict that could be affecting the working of this field.

    Please deactivate your current theme and all the installed plugins to ensure the behavior is not arising from a conflict.

  • Any shortcodes that work in the standard WP WYSIWYG editor in WP should work in an ACF WYSIWYG field. Since these filters are applied in the gallery shortcode then they should still be called if using that shortcode.

  • Hi, I don’t think the tinymce editor is created by another plugin. I’m just using ACF’s own Wysiwyg Editor fields. I’ve attached two screenshots to illustrate the problem:
    source code button

    source code pop up

    Its hard to edit code with no formatting like that. I’d like the line breaks and indentation of the code.

  • We just had the same problem with a transition from ACF+Repeater, etc., to Pro. All our field groups but one were duplicated. The one that was not duplicated had only a single text field; each of the others had repeater, WYSIWYG and/or related post link fields.

    The bad news is that in at least one case, there are two fields missing from one of the repeater fields in the older version of the field group. The portal_box field in field_group #5209 has only three fields; the one in field_group #5255 contains all five of the fields that should be there. (See attachments.) As a result, part of the portal box is not displaying.

    We have no multi-language support. Here’s a list of our active plugins:
    ManageWP – Worker (v4.1.6) by ManageWP
    Gravity Forms (v1.9.9) by rocketgenius
    Admin Quick Jump (v1.4) by James Kemp
    Advanced Custom Fields Pro (v5.2.6) by elliot condon
    Advanced Post Types Order (v3.6.2) by Nsp Code
    BackWPup (v3.1.4) by Inpsyde GmbH
    Categories Images (v2.5) by Muhammad Said El Zahlan
    Cookies for Comments (v0.5.5) by Donncha O Caoimh
    Duplicate Post (v2.6) by Enrico Battocchi
    WordPress Editorial Calendar (v3.5) by Colin Vernon, Justin Evans, Joachim Kudish, Mary Vogt, and Zack Grossbart
    Enable Media Replace (v3.0.3) by Måns Jonasson
    Google Analytics by Yoast (v5.4.2) by Team Yoast
    Google Calendar Events (v0.7.2) by Ross Hanney
    Gravity Forms – Placeholders add-on (v1.2.1) by Joan Piedra
    Gravity Forms MailChimp Add-On (v3.6) by rocketgenius
    Image Watermark (v1.5.0) by dFactory
    McWebby Magnific Popup (v00.01.00) by Donna McMaster
    McWebby Custom Post Types (v00.02.01) by Donna McMaster (declares post types)
    Media Tags (v3.2.0.2) by Paul Menard
    Members (v0.2.4) by Justin Tadlock
    Simple Sitemap (v1.65) by David Gwyer
    Sucuri Security – Auditing, Malware Scanner and Hardening (v1.7.9) by Sucuri, INC
    Category Order and Taxonomy Terms Order (v1.4.2) by Nsp-Code
    ThreeWP Activity Monitor (v2.12) by edward mindreantre
    WooCommerce Bulk Discount (v2.3.1) by Rene Puchinger
    WooCommerce Dynamic Pricing (v2.9.6) by Lucas Stark
    WooCommerce (v2.3.10) by WooThemes
    WooThemes Helper (v1.5.5) by WooThemes
    WordPress SEO (v2.1.1) by Team Yoast
    WP Migrate DB Pro (v1.4.7) by Delicious Brains
    WP SEO Humility (v0.1) by Donna McMaster

    Must-use Plugins:
    ManageWP – Worker Loader (v) by ManageWP
    McWebby Debug Log (v0.1.0) by Donna McMaster

    field-group-....png
    field-group-....png

  • Thanks @elliot this lead me to the solution.

    i can share now this code:

    function my_acf_input_admin_footer() {
?>
<script type="text/javascript">
acf.add_filter('wysiwyg_tinymce_settings', function( mceInit, id ){
	
	// do something to mceInit
	mceInit.setup = function( ed ){
	ed.on('init', function () {
         // Note these lists may not be complete & that other tinymce plugins can add their own shortcuts anyway.
                var ctrls = [ 'u', '1', '2', '3', '4', '5', '6', '7', '8', '9', 's', 'k', 'Alt+F', 'P' ];
                var modKeys = [ 'c', 'r', 'l', 'j', 'q', 'u', 'o', 'n', 's', 'm', 'z', 't', 'd', 'h', 'o', 'x', 'a', 'w', '1', '2', '3', '4', '5', '6', '7', '8', '9' ];
                // Overwrite shortcuts with no-op function. Key sequences will still be captured.
                for (var i = 0; i < ctrls.length; i++ ) {
                    //this.addShortcut('ctrl+' + ctrls[i], '', function () {}); //use if tinyMCE <=4.1.7
                    this.addShortcut('Meta+' + ctrls[i], '', function () {});
                }
                for (var i = 0; i < modKeys.length; i++ ) {
                    //this.addShortcut('alt+shift+' + modKeys[i], '', function () {});//use if tinyMCE <=4.1.7
                    this.addShortcut('access+' + modKeys[i], '', function () {});
                }
    });
	};
	// return
	return mceInit;
			
});
</script>
<?php
}

add_action('acf/input/admin_footer', 'my_acf_input_admin_footer');

    can be inserted into function.php or a own plugin and should work. and provide the disable of tinymce shortcuts. (at my example it removes: headings, underline, and more. bold and italic shortcuts would still work)

    I will update this post with the other options that wish to use. as soon i tested it

    EDIT:
    TinyMCE <= 4.1.7, and >= 4.1.8 use different code

  • Hi @mediawerk

    It is possible to modify all tinymce settings through the JS filter:
    ‘wysiwyg_tinymce_settings’

    You can see how to use this filter here: http://www.advancedcustomfields.com/resources/adding-custom-javascript-fields/

    Thanks
    E

  • To add to the above, I thought it might help to post up some images showing the problem. I decided to use a text field instead of a WYSIWYG editer, to keep the images compact and clear.

    To begin with, I create 5 rows, each containing a c-logic checkbox and a text field. The checkbox determines whether the text field is visible or not. I save/update the page and the result looks like this:-

    Initial setup

    I then uncheck the checkboxes to hide the text fields and update the page again:-

    Hide text fields

    Then, I insert a new row between rows 2 and 3 and populate the new text field with “new row” :-

    Insert new row

    Now, if I press update and then make all the rows visible, I get the following:-

    Borked rows

    As you can see, the rows and their data have not moved down as expected. Row 3 has been wiped and replaced with the new row.

    Thanks

  • The fields were WYSIWYG.

    I did get this sorted out. In case anyone else has the same issue on a site hosted at WP Engine, I’ll put the fix below.

    In WP Engine’s control panel, under SSL, I had to use the following:

    Uncheck “Force http:// for non-SSL pages” – if this is checked I was getting a redirect trying to log in.

    Select “Use SSL for WP-login” – don’t select the one that includes WP-admin. WP-login only does keep WP-admin https too so I’m not sure what the difference is, but the one that includes WP-admin sets the “Site Address (URL)” to use https://, WP-login only does not.

    With these settings, the admin pages are still https, but internal site links in ACF WYSIWYG fields do not get automatically converted to https when resaving. This was happening on 3 sites at WP Engine so I don’t think it was a one off weird configuration or anything.

  • I’ve testing the wysiwyg field on category taxonomy and it’s working in both ACF4 & 5.

    My guess is that there is some kind of interference from another plugin.

    Do you have any other plugins on the site that effect the WYSIWYG editors on the site?

  • Here is the solution I have used to remove the stray p tags when using shortcodes in the ACF WYSIWYG (put that in your functions file).

    function wpex_clean_shortcodes($content){   
    $array = array (
        '<p>[' => '[', 
        ']</p>' => ']', 
        ']<br />' => ']'
    );
    $content = strtr($content, $array);
    return $content;
}
add_filter('acf_the_content', 'wpex_clean_shortcodes');?>

    So far, I have not had any problems with this solution.

  • Hi,
    Here is an almost similar thread on how to access acf field from the product category page.

    http://support.advancedcustomfields.com/forums/topic/custom-wysiwyg-field-in-woocommerce-product-category/

    I hope this helps.

  • Hi @elliot thank you for your input.
    I did follow your recommendation as a temp solution.

    Do you see this being implemented in a future release?
    Having the embed code in both the post’s editor and the ACF WYSIWYG field isn’t ideal.

    Cheers and thanks again!

  • @tmconnect like i say at opening post: modify only the toolbar is not enough for me. thats why your post dont help. and if you read carefully you will see that problem is made by ACF, thats why i also cant use tiny_mce_before_init filter. that work for/with default wysiwyg.


    @elliot     any toughts, comment or help for this problem?

    or is someone else able to help me, without to modify corefiles?

  • I’m having load issues using a repeater field with conditionals as stated above. The main problem is the JS load time crashes the browser, and I also get a lot of “connection lost” errors.

    I changed all text fields to text areas versus wysiwyg, and also elminated a couple of conditionals. This helped a little bit, but still not good.

    I’m thinking of rebuilding using the ACF Pro with the Flexible content. Can you tell me if you think this would solve my issue?

  • You can modify the toolbars with the acf/fields/wysiwyg/toolbars filter like this

    function my_toolbars( $toolbars ) {
	$toolbars['Full'] = array();
	$toolbars['Full'][1] = array('bold', 'italic', 'underline', 'bullist', 'numlist', 'alignleft', 'aligncenter', 'alignright', 'alignjustify', 'link', 'unlink', 'hr', 'spellchecker', 'wp_more', 'wp_adv' );
	$toolbars['Full'][2] = array('styleselect', 'formatselect', 'fontselect', 'fontsizeselect', 'forecolor', 'pastetext', 'removeformat', 'charmap', 'outdent', 'indent', 'undo', 'redo', 'wp_help' );

	// remove the 'Basic' toolbar completely (if you want)
	unset( $toolbars['Basic' ] );

	// return $toolbars - IMPORTANT!
	return $toolbars;
}
add_filter('acf/fields/wysiwyg/toolbars' , 'my_toolbars');

    Hope this helps

  • You can modify the toolbars with the acf/fields/wysiwyg/toolbars filter like this

    function my_toolbars( $toolbars ) {
	$toolbars['Full'] = array();
	$toolbars['Full'][1] = array('bold', 'italic', 'underline', 'bullist', 'numlist', 'alignleft', 'aligncenter', 'alignright', 'alignjustify', 'link', 'unlink', 'hr', 'spellchecker', 'wp_more', 'wp_adv' );
	$toolbars['Full'][2] = array('styleselect', 'formatselect', 'fontselect', 'fontsizeselect', 'forecolor', 'pastetext', 'removeformat', 'charmap', 'outdent', 'indent', 'undo', 'redo', 'wp_help' );

	// remove the 'Basic' toolbar completely (if you want)
	unset( $toolbars['Basic' ] );

	// return $toolbars - IMPORTANT!
	return $toolbars;
}
add_filter('acf/fields/wysiwyg/toolbars' , 'my_toolbars');

    Hope this helps

  • Maybe this alternate solution is a little bit faster. It simply change the default option of the colorpicker when there are acf fields on the page.

    
function change_acf_color_picker() {
  // Adds client custom colors to WYSIWYG editor and ACF color picker.
  $client_colors = array(
    "#222222",
    "#8dc4d5",
    "#e1523d",
    "#eeeeee",
    "#323232",
    "#ffffff",
    "#000000"
  );

  echo "<script>
  (function($){
    try {
      $.wp.wpColorPicker.prototype.options = {
        palettes: " . json_encode($client_colors) . "
      };
    }
    catch (e) {}
  })(jQuery)
  </script>";
}

add_action( 'acf/input/admin_head', 'change_acf_color_picker' );

  • I’ve solved this myself by adding the following to my theme’s functions.php:

    function acf_apply_content_filter_for_api($value, $post_id, $field){
     return str_replace( ']]>', ']]>', apply_filters( 'the_content', $value) );
}
function add_content_filter_ACF(){
   if(!is_admin()){
      remove_all_filters('acf/format_value/type=wysiwyg');
      add_filter('acf/format_value/type=wysiwyg', 'acf_apply_content_filter_for_api', 10, 3);
   }
}
add_action('init', 'add_content_filter_ACF');

  • Sorry to hijack this thread but I’m looking at the exact same issue. Civil footnotes is a basic plugin that allows content authors to write footnotes. The plugin hooks on to the_content and generates a list of numbered footnotes by searching for anything matching the (( this is a footnote )) pattern.

    Here’s the plugin: https://gist.github.com/Jolora/a947b856d3440f8cc029

    I was wondering if you could give a clue as to how I would go about getting this plugin to also search any WYSIWYG ACF fields, including those inside flexible content fields.

    Any help would be appreciated please. Thanks!

  • I’m in the same boat!! This plug-in is terrific!

    I’m having the same issue — and i’m trying to access the Image-URL via ‘meta:’ in a post-based slider. My workaround is create a custom field text type that cntains the URL text of the image — but I’d really like to use the wysiwyg image controls.
    Accessing it via the Meta tags only returns the image ID.

    Did you figure this one out?

Viewing 25 results - 801 through 825 (of 1,305 total)
1 2 3 … 32 33 34 … 51 52 53