Search Results for 'Wysiwyg'

• In reply to Repeater data does not appear

• October 14, 2016 at 2:36 am

Hi @James!

Thanks to return! 🙂

Well, let’s go to the explanation:

We have the “specific Follow up” that works perfectly.

I want the “Follow specific ups” of each “Phase” appears in the “Follow up General”. On here:

The code for the “general Follow up” appears is in my question above, but not given any returns.

Below forward you the JSON export area of my group camps, which already includes the “Phases” and “Follow ups”:

$phase_fields = array (
        'id' => 'acf_phases',
        'title' => __('Phases','psp_projects'),
        'fields' => array (
            array (
                'key' => 'field_5436e7cae06b2',
                'label' => __('Break projects into multiple phases with specific tasks.','psp_projects'),
                'name' => '',
				'type'	=> 'message'
            ),
            array (
                'key' => 'field_527d5dc12fa29',
                'label' => __('Phases','psp_projects'),
                'name' => 'phases',
                'type' => 'repeater',
                'sub_fields' => array (
                    array (
                        'key' => 'field_527d5dd02fa2a',
                        'label' => __('Title','psp_projects'),
                        'name' => 'title',
                        'type' => 'text',
                        'column_width' => '',
                        'default_value' => '',
                        'placeholder' => '',
                        'prepend' => '',
                        'append' => '',
                        'formatting' => 'html',
                        'maxlength' => '',
                    ),
					array (
                        'key' => 'field_527d5dea2fa2c',
                        'label' => __('Description','psp_projects'),
                        'name' => 'description',
                        'type' => 'wysiwyg',
                        'column_width' => '90',
                        'default_value' => '',
                        'toolbar' => 'full',
                        'media_upload' => 'no',
                    ),
					//START FOLLOW UP
					array (
						'key' => 'field_57c8e3d4d2c8d',
						'label' => __('Follow up','psp_projects'),
						'name' => 'follow_up',
						'type' => 'repeater',
						'instructions' => 'Insira aqui as informações e detalhamento em relação a este projeto.',
						'column_width' => '',
						'sub_fields' => array (
							array (
								'key' => 'field_57c8e41bd2c8e',
								'label' => __('Data de atualização','psp_projects'),
								'name' => 'data_de_atualização',
								'type' => 'date_picker',
								'date_format' => 'yymmdd',
								'display_format' => $date_format,
								'first_day' => 0,
							),
							array (
								'key' => 'field_57c8e4d9d2c8f',
								'label' => __('Nº do processo','psp_projects'),
								'name' => 'n_do_processo',
								'type' => 'text',
								'column_width' => '',
								'default_value' => '',
								'placeholder' => '',
								'prepend' => '',
								'append' => '',
								'formatting' => 'html',
								'maxlength' => '',
							),
							array (
								'key' => 'field_57c8e4f9d2c90',
								'label' => __('Unidade','psp_projects'),
								'name' => 'unidade',
								'type' => 'text',
								'column_width' => '',
								'default_value' => '',
								'placeholder' => '',
								'prepend' => '',
								'append' => '',
								'formatting' => 'html',
								'maxlength' => '',
							),
							array (
								'key' => 'field_57c8e50ad2c91',
								'label' => __('Desde','psp_projects'),
								'name' => 'desde',
								'type' => 'date_picker',
								'date_format' => 'yymmdd',
								'display_format' => $date_format,
								'first_day' => 0,
							),
							array (
								'key' => 'field_57c8e523d2c92',
								'label' => __('Situação','psp_projects'),
								'name' => 'situacao',
								'type' => 'text',
								'instructions' => 'Ex.: "INFORMANDO BOLETIM DE DADOS TÉCNICOS"',
								'column_width' => '',
								'default_value' => '',
								'placeholder' => '',
								'prepend' => '',
								'append' => '',
								'formatting' => 'html',
								'maxlength' => '',
							),
							array (
								'key' => 'field_57c8e54ed2c93',
								'label' => __('Detalhamento Kallas','psp_projects'),
								'name' => 'detalhamento_kallas',
								'type' => 'textarea',
								'instructions' => 'Ex.: "Estão sendo informados zoneamento, largura e classificação viárias, gabarito e outros dados para prosseguir posteriormente para análise técnica"',
								'column_width' => '',
								'default_value' => '',
								'new_lines' => 'wpautop',
								'placeholder' => '',
								'prepend' => '',
								'append' => '',
								'formatting' => 'html',
								'maxlength' => '',
							),
							'row_min' => '',
							'row_limit' => '',
							'layout' => 'row',
							'button_label' => __('Adicionar Follow up','psp_projects'),
						),
							//END FOLLOW UP
							
			),
                'row_min' => '',
                'row_limit' => '',
                'layout' => 'row',
                'button_label' => __('Add Phase','psp_projects'),
            ),
        ),
        'location' => array (
            array (
                array (
                    'param' => 'post_type',
                    'operator' => '==',
                    'value' => 'psp_projects',
                    'order_no' => 0,
                    'group_no' => 0,
                ),
            ),
        ),
        'options' => array (
            'position' => 'normal',
            'layout' => 'default',
            'hide_on_screen' => array (
            ),
        ),
        'menu_order' => 3,
    );	

How can we do so that the “Follow up General” to work successfully? Call it as in my question has not worked.

Already, thank you very much for your help. 🙂

• In reply to Removing Paragraph Tags from WYSIWYG Fields?

• October 9, 2016 at 10:48 am

Hi,

Not sure if this will work for you, but it worked for me..

//Remove WPAUTOP from ACF TinyMCE Editor
function acf_wysiwyg_remove_wpautop() {
    remove_filter('acf_the_content', 'wpautop' );
}
add_action('acf/init', 'acf_wysiwyg_remove_wpautop');

This will remove it from all ACF WYSIWYG fields, but you should be able to target this to just one field..

The difference between this function and the others I saw in this thread, is that the action is added on ‘acf/init’

• In reply to ACF conflict with Visual Composer plugin

• October 5, 2016 at 2:11 am

For more than one year that I look this solution and while it is not a substitute for ACF by Custom Field Suit only for compatibility with Visual Composer in the WYSIWYG editor.

Is there anyone working in this fix?

• In reply to Custom Scripts

• October 3, 2016 at 12:18 pm

Hi @mdurchholz

Yes, it would affect all WYSIWYG editor. If you want to do it only for certain field, you can use the acf/load_value filter instead. It should be like this:

function my_acf_load_value( $value, $post_id, $field ) {
    
    remove_filter('acf_the_content', 'wpautop' );

    return $value;
}

// acf/load_value/name={$field_name} - filter for a specific value load based on it's field name
add_filter('acf/load_value/name=wysiwyg_editor', 'my_acf_load_value', 10, 3);

I believe the text area field won’t convert special chars like <>. I’ve just tested it on my installation and it executed the script correctly. Maybe it has something to do with your theme, plugins or database encodings.

To check if it’s your theme or plugins fault, could you please try to reproduce the issue on one of the WordPress’ stock themes (like Twenty Sixteen) with other plugins deactivated? If it disappears, then you can activate the theme and plugins one by one to see which one causes the issue.

To check if it’s your database encodings fault, you need to get in touch with your hosting provider.

I hope this makes sense 🙂

• In reply to Custom field type plugin assets

• October 2, 2016 at 1:20 am

Take a look at the WYSIWYG field in ACF. There is some conditional logic in it that only loads the WP uploader where it’s needed. It’s the only field in ACF that I know of that does something like this and probably your best bet at getting an idea of what you’re looking for.

• In reply to Custom Scripts

• October 1, 2016 at 12:33 am

Wouldn’t that script stop all wysiwyg editors? I only want it for one area. Is there a way to modify it to target one specific field group?

Also, is there a way to stop the textarea fields from changing my <> characters into HTML entities? I’d prefer to use the textarea rather than adjusting the WYSIWYG editor.

• In reply to Custom Scripts

• September 30, 2016 at 1:12 pm

Hi @mdurchholz

For the text area field, you should be able to set the New Lines option (PRO version) or Formatting option (Free version) to “No Formatting”.

For the WYSIWYG field, you should be able to remove the <p> tag like this:

function my_acf_add_local_field_groups() {
    remove_filter('acf_the_content', 'wpautop' );
}
add_action('acf/init', 'my_acf_add_local_field_groups');

I hope this helps 🙂

• In reply to ACF Pro v5.4.5 breaks TinyMCE / TypeError r is null

• September 27, 2016 at 9:33 pm

I just tested this on a site with only ACF installed and running a bare 2015 theme and there does not appear to be any problem with the wysiwyg editor or TinyMCE.

Try deactivating other plugins and see if you can determine were the incompatibility is.

• In reply to Basic textfield with simple formatting options (bold, italic, links, …)

• September 21, 2016 at 7:57 am

I just found this, maybe you should give the author of this plugin some input https://github.com/lukechapman/acf-inline-wysiwyg

• In reply to Minimum number of characters in a text field

• September 16, 2016 at 10:34 pm

Actually now I see that the soution doesn’t reallt work for me. I’m trying to apply this validation on a wysiwyg field and the strlen always returns 0 characters.

Itamar

• In reply to Uncaught TypeError: Cannot read property 'body' of undefined

• September 15, 2016 at 10:43 am

Hi guys

Issue update:

I’ve logged into a few users websites, but am unable to replicate the issue!
– The WYSIWYG editors load just fine

The only time I’ve been able to replicate the issue is when I screen-shared with another user to view his wp-admin. He was running windows and the wp-admin page took quite a while to load.

I’m starting to think the issue may be due to the computer / browser load times.
Maybe my mac is loading the page too quickly and the issue never triggers.

Can you please be sure to note your details:
ACF version:
WP version:
OS:
Browser inc version:

Thanks
Elliot

• In reply to Uncaught TypeError: Cannot read property 'body' of undefined

• September 15, 2016 at 10:29 am

Hi guys

Thanks for all the comments.
I’ve just had some luck replicating the issue and will most likely have a fix out today.

Yes, the issue is triggered from the acf.fields.wysiwyg.add_events function

• In reply to Wysiwyg-editor sometimes strips line-breaks

• September 13, 2016 at 3:57 am

@jannej

I’m currently searching for a solution to a similar issue. My problem is specifically the <br> and <br /> tags. They are still in my WYSIWYG editor on the admin side, but do not render on the page 100% of the time. I’ll post up here if I find something that helps.

• In reply to Wysiwg editor text not visible proper on frontend

• September 6, 2016 at 4:50 pm

Hi @pshahwpcodal-com

The value in the database is correct. The paragraph tags you saw on the backend are generated by the content editor, but the real data doesn’t have it.

The WYSIWYG field has a feature that will convert a new line into a paragraph tag automatically, but it seems not working on your site. Maybe there’s a function that prevents it. Could you please try to reproduce the issue on one of the WordPress’ stock themes (like Twenty Sixteen) with other plugins deactivated? If it disappears, then you can activate the theme and plugins one by one to see which one causes the issue.

As a workaround, you can add the paragraph tags like this:

echo wpautop(get_field('short_description_2'));

I hope this helps 🙂

• In reply to Wysiwg editor text not visible proper on frontend

• September 6, 2016 at 3:01 pm

Hi @pshahwpcodal-com

Could you please share the example of the text you’ve entered in the WYSIWYG field and the result in the database? Don’t forget to use the code wrapper if you want to share it here.

Also, could you please share the URL to the page where you show the field?

Thanks 🙂

• In reply to WYSIWYG Source Code Button

• September 6, 2016 at 2:42 pm

Hi @wyclef

First, you need to copy the “tinymce.code.min.js” to anywhere you see fit. For example, you can put it in your child theme: “wp-content/themes/your-child-theme/js/tinymce.code.min.js”.

After that, you need to register this file to tinyMCE like this:

add_filter( 'mce_external_plugins', 'my_acf_mce_external_plugins', 20, 1 );
function my_acf_mce_external_plugins($plugins){
    // global
    global $wp_version;
    
    // WP 3.9 an above
    if( version_compare($wp_version, '3.9', '>=' ) ) {
        
        // add code
        $plugins['code'] = get_stylesheet_directory_uri() . '/js/tinymce.code.min.js';

    }
    
    // return
    return $plugins;
}

Then, you need to add the button to the toolbar like this:

add_action('acf/input/admin_footer', 'my_acf_enable_code_plugin');
function my_acf_enable_code_plugin() {

    ?>
    <script type="text/javascript">
    (function($) {
        
        $(document).ready(function(){
            acf.add_filter('wysiwyg_tinymce_settings', function( mceInit, id ){
                
                // Add code to toolbar
                mceInit.toolbar2 = mceInit.toolbar2 + ",code";

                // return
                return mceInit;
                
            });
        });
        
    })(jQuery);    
    </script>
    <?php    
    
}

I hope this helps 🙂

• In reply to Set WYSIWYG Height

• September 5, 2016 at 12:46 pm

Hi @silverdarling

You should be able to do it like this:

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

function my_acf_modify_wysiwyg_height() {
    
    ?>
    <style type="text/css">
        .acf-field-1234567890abc iframe{
            height: 600px !important;
        }
    </style>
    <?php    
    
}

Where acf-field-1234567890abc is the element ID of your WYSIWYG field.

Thanks 🙂

• In reply to TinyMCE error

• September 5, 2016 at 9:12 am

Hi @magicstick

Thanks for the reply.
There is still too much ambiguity around this issue.

Can you please create a support ticket with a more details description of the issue:
http://support.advancedcustomfields.com/new-ticket/

– does the issue occur editing a post?
– does the issue occur editing a user?
– does the issue occur editing a acf_form()?
– What is needed to replicate the issue? A simple wysiwyg field? Or within a repeater?
– have you disabled all other plugins / themes to test conflict?

Thanks
Elliot

• In reply to TinyMCE error

• September 2, 2016 at 6:24 pm

Hi Elliot. My issue with tinymce seems to have persisted unfortunately. See my above post.

Just to confirm my scenario for debugging:

• If visual editor is default tab it’s not working (switching to text tab works)
• If text tab is default, I can switch to visual tab and it works.
• It’s a form in a user Add/Edit form. However I am pulling the acf_form to a front end template page and behavior is the same.
• I’ve tried deactivating all my plugins apart from ACF. No change.
• I’ve tried removing all other jQuery based fields from my field group. No change.
• WYSIWYG working fine on pages flexible fields. (don’t get that at all)

Let me know if there is anything else I can do to help debug from my end. I’m out of ideas here.

• In reply to TinyMCE error

• September 2, 2016 at 5:51 am

Can I just add more fuel to the fire here, maybe my info will help identify any issues.

What I am experiencing is on acf_forms frontend. If The user is defaulted to the ‘visual tab’ on the WYSIWYG editor when the page loads the WYSIWYG fails to fully instantiate. However if the user is defaulted to the ‘text’ tab and then clicks on the ‘visual’ it loads fine.

See attached screen grab of my console error when you click on the ‘visual’ tab when the WYSIWYG when you the page load brings in the ‘visual’ tab as default

Screen-Shot-....jpg

• In reply to Set WYSIWYG Height

• September 1, 2016 at 4:40 am

Height of wysiwg is hardcoded in wysiwyg.php

Path\wp-content\plugins\advanced-custom-fields-pro\fields\wysiwyg.php:
  255  		
  256  		// get height
  257: 		$height = acf_get_user_setting('wysiwyg_height', 300);
  258: 		$height = max( $height, 300 ); // minimum height is 300

You can’t easily change that with css because it produces inline css , viz –

<textarea id="acf-editor-gtg6gtg6gtg62" class="wp-editor-area" name="acf[field_gtg6gtg6gtg62]" style="height:300px;">wysiwyg content here</textarea>

Good thing is that wysiwyg.php looks like its primed to go for adding wysiwyg height via admin interface.

• In reply to Image Captions in WYSIWYG

• August 26, 2016 at 7:21 pm

Bump!

My captions for images added into wysiwyg fields have suddenly stopped appearing. A few days ago they were fine, I think, but today they are suddenly gone. In fact, WordPress is no longer wrapping the captioned images in a <figure> tag so the whole layout has gone awry. It is basically treating captioned images as uncaptioned images. I am not 100% sure it is not due to something I have done, but if anyone can give advice would be v grateful. All my plugins and theme etc are up to date. THe site is not live, it is on mamp, still being built.

If I add an image in the standard (non acf) wysiwyg, captions do appear.

UPDATE

I think I may have found the cause. Plugin called wp typography, if I deactivate it, the captions reappear. Not sure yet, maybe there is a compatibility issue.

• In reply to TinyMCE error

• August 26, 2016 at 5:08 pm

I deactivated all plugin’s except ACF and now it works. Then I activated all my plugins one by one and every time I checked if the WYSIWYG fields where back to normal and after checking all one at a time it now (looks) like its working again.

Maybe this will fix your issues as well?

• In reply to Uncaught TypeError: Cannot read property 'body' of undefined

• August 26, 2016 at 6:05 am

I am getting one JS error with ACF 4

Error: Syntax error, unrecognized expression: #wp-wysiwyg-acf-field-wysiwyg_(copy)-57bf4a104c01f-wrap

and this error is cause by the way I created the test group I used, but it doesn’t seem to be breaking anything.

• In reply to TinyMCE error

• August 26, 2016 at 5:51 am

Thanks for your help,

I am trying to make it work with qtranslate (I have qtranslate-X and acf qtranslate). So I disabled qtranslate and the ACF WYSIWYG field works well even if the error still appears in js console. But when I reactivate qtranslate, all the WYSIWYG fields are missing the toolbar.