Support

Account

Home Forums Search Search Results for 'Wysiwyg'

Search Results for 'Wysiwyg'

reply

  • Hi @dynamyc

    In your first comment, you say that the output is the same, as in, the shortcode is not being converted at all.

    I don’t understand the importance of this div.
    Perhaps you can ask the shortcode plugin developer as I am not sure how I can be of much help on this one.

    Thanks
    E

  • Hi @Nitruc

    I would suggest that you use firebug / inspector to actually debug the CSS. Perhaps your style rules are being overridden by ACF or WP?

    You can test this using firebug / inspector

    Thanks
    E

  • Sure, I’m attaching three images. One shows the public view. The pink area is the ACF WYSIWYG content, the green is the default WP WYSIWYG (there are no images in there).

    The other images show the admin screens for these fields. I can insert a class manually in the ACF WYSIWYG editor, that just becomes cumbersome when there are multiple images. I was hoping to streamline the process by having a class inserted automatically for any image added to that field.

    Any help would be appreciated.
    Public Screen
    WP WYSIWYG
    ACF WYSIWYG

  • Yes, I have a plugin installed for shortcodes.

    What I’m more interested is to make a specific plugin shortcode to work. This is kind of urgent.

    For what I should look inside the plugin files ? Or what I need to modify in order to work?

    I see the button for it inside the WYSIWYG field but the output is like this:
    <div id="countdown-1385051206"></div>

    So is doing something but the div is empty.
    Should I ask the developer of the plugin?

  • Hey @elliot,

    I actually have tried using .acf_wysiwyg iframe too, that was my mistake that I didn’t mention it above. But what exactly would I use if I wanted to set the height to 15px? I tried:

    .acf_wysiwyg iframe {
    	min-height:0;
    	height:15px;
    }

    But it seems like WordPress won’t allow the WYSIWYG field area to be anywhere near that short. It won’t even let me click and drag the bottom right corner to make it shorter than what looks like around a height of 100px. I ended up hacking it a bit more using this to get what I wanted:

    .acf_wysiwyg iframe {
        height: 15px;
        min-height: 15px;
        overflow: hidden;
    }
    
    .acf_wysiwyg .wp-editor-container {
    height:70px;
    overflow: hidden;
    }

    Let me know if there’s a better way of doing this. Also, where exactly should I be editing this code? Right now I’m just using a custom function in my functions.php file that adds the custom css to the admin’s head.

  • Hi @shawn00m

    Thanks for the question, but could you please demonstrate the differencce between the normal and ACF WYSIWYG value via screenshots?

    Thanks
    E

  • Hi @dynamyc

    Could be either. Do you have a ‘button’ shortcode plugin installed? Is it part of your theme?

    Easiest way is to search your website folder for “shortcode”

    Thanks
    E

  • Hi @Nitruc

    Using firebug I can see that the CSS rule needed to modify the height is:

    
    .acf_wysiwyg iframe {
    
    }
    

    Please note that there is a min-height rule which will need to be set to 0 to allow for your height attribute to work.

    Please use firebug / inspector as you can modify the CSS on the fly and test as you go!

    Hope that helps.

    Thanks
    E

  • The shortcode is working in the normal content editor, which is strange because some shortcodes are working inside the WYSIWYG fields.

    The code which I’m using to output the WYSIWYG value is this:
    <?php the_field('fieldname'); ?>

    I don’t know where to look to see what code I’m using for registering the shortcode, should I look in the plugin files or inside my theme files?

    Thanks!

  • Thank you, this is what I needed:

    
    add_filter('tiny_mce_before_init', 'wpse3882_tiny_mce_before_init');
    function wpse3882_tiny_mce_before_init($settings) {
        $settings['theme_advanced_blockformats'] = 'p,h1,h2';
        return $settings;
    }
    
  • Hi @PerS

    Thanks for clarifying.
    I know that this is possible using a filter on all WP WYSIWYG called ‘tiny_mce_before_init’, but this will be applied to all fields, not specific ACF fields…

    I found this article on stack exchange which may be a good starting point:
    http://wordpress.stackexchange.com/questions/3882/can-i-add-a-custom-format-to-the-format-option-in-the-text-panel

    Good luck

    Thanks
    E

  • Hi @pixaro

    I see, so this question is not specific to the WYSIWYG field? That is where your question became confusing.

    I would create a layout in your flexible content field called page_break.

    Then in your template, within the flexible content loop, create a counter variable which starts at 1 and gets increased each time the page_break layout is used.

    Then, you can look at the $_GET param “page” and match it to your counter variable value. If the value does not match, use a ‘continue’ statement to ignore the current loop’s layout.

    Therefore, if you had &page=2 in your URL, your loop would only show layouts which appear after the first ‘page_break’ but before the second.

    I hope that helps

    Thanks
    E

  • Hi @webmasterID

    Can you check the source code on your page? Is the MARKUP for the nextgen gallery correct?
    Can you also check your console log for any JS errors?

    Perhaps also test the nextgen gallery in a WYSIWYG field which is at the root level (not in a flexible content field) for a comparison test.

    Thanks
    E

  • Hi @revconcept

    Perhaps you will need to refresh the plugins page. You should see an update like so:

  • formatselect is the pull down list in the editor with h1,h2,h3 ..

  • Thank you! You are always so fast with this stuff. I don’t see an update available in the admin though.

  • Hi @PerS

    Could you please elaborate a bit more on what ‘formatselect’ select is? I’m not familiar with this.

    Thanks
    E

  • Hi @revconcept

    Thanks for the screenshot. This issue has just been fixed and you can download the an update for the repeater field through your normal plugins wp-admin page.

    Thanks
    E

  • Hi @pixaro

    I have not yet tested this, but have a feeling that you could make it work as expected.

    You can hook into the WYSIWYG value through the filter called ‘acf_the_content’. This is a replica of the already WP documented ‘the_content’ filter.

    Using this, you could use some PHP to look for and explode the value based on ‘‘. Then, using a the current paged query parameter, you could customize which part you return as the value.

    Hope that helps

    Thanks
    E

  • Hi @psejersen

    Looking at the source code within the div with id=”producenter_omraader_facts”, I can’t see any br tags…

    Can you attach a screenshot of the field group edit page showing the WYSWIYG field will all settings open?

    Also, can you attach a screenshot of what the WYSIWYG field looks like when you input a value?

    Thanks
    E

  • Hi @dynamyc

    Thanks for the screenshot. I ti s now clear to see the issue.
    Usually, the WYSIWYG toolbar does not look like this. I think your theme is customizing the toolbar by overriding the button choices.

    The kitchen sink is the button on the top row, second from the right and it toggles the second row of buttons. This is not the issue as I can see all the rows are open.

    I think you will need to search through your theme for a filter such as ‘tiny_mce_before_init’ and see if there is some code which is changing the buttons.

    If this is a purchased theme, perhaps you can also contact the developer and ask them how to allow ACF to add the ‘html’ code button to the WYSIWYG toolbar?

    Thanks
    E

  • Here is a screenshot:
    screenshot

    Regarding to your answer:
    1. I don’t understand what do you mean by “kitchen sink”
    2. I don’t have any tinyMCE plugin installed

  • Hi @kamullis

    Are you able to provide some login details for me to see this error myself?

    You can mark the reply as private.

    Thanks
    E

  • Thanks @elliot looks like I’m getting an error in the input.min.js file from the 4.3 update

    The error is:
    Uncaught TypeError: Object [object Array] has no method ‘getBody’

    I’ll see what I can do to fix it. Still pretty much a novice when it comes to js though…

    Wish me luck 😉

  • Thank you! 😉

Viewing 25 results - 1,051 through 1,075 (of 1,299 total)