• Resolved simon_beanstalk

    (@simon_beanstalk)


    Hi there Andrew, great plugin, nice work.

    Just letting you know there’s an incompatibility with Visual Composer and Tiny MCE Advanced.

    I’ve got your plugin installed so that BBpress users have a great TinyMCE experience, but the backend of the affected site uses WPBakery’s Visual Composer, so I’ve fallen victim to this incompatibility.

    –The issue–
    Whenever an editor goes to edit something in the WP backend, Tiny MCE Advanced initialises, and strips some line breaks, even though ‘do not remove p and br tags’ is checked in Tiny MCE Advanced’s settings.

    Deactivating either plugin seems to resolve the issue (but obviously takes a lot of other backward steps).

    Thanks!

    https://www.ads-software.com/plugins/tinymce-advanced/

Viewing 14 replies - 1 through 14 (of 14 total)
  • Thread Starter simon_beanstalk

    (@simon_beanstalk)

    Plugin Author Andrew Ozz

    (@azaozz)

    Generally line breaks are ignored in HTML. In WordPress wpautop() replaces paragraph tags with two line breaks in the editor, and adds back the paragraph tags on display.

    When you enable the “Stop removing P and BR…” option in TinyMCE Advanced, you actually disable wpautop() in WP and are left with “standard” HTML code.

    From your description it seems that Visual Composer still depends on line breaks in the HTML. This is what makes it incompatible not only with TinyMCE Advanced’s option to “Stop removing P and BR…”, but also with disabling the wpautop functionality.

    If Visual Composer’s authors really made over $17,000,000 from it (500,000 users X $34), I’d guess they can afford to fix this incompatibility ??

    For now, I’d suggest not using the “Stop removing P and BR…” option in TinyMCE Advanced.

    Thread Starter simon_beanstalk

    (@simon_beanstalk)

    Hi Andrew,

    Thanks for the response. Really appreciate you taking the time :).

    I’m happy to report that unchecking ‘do not remove P and BR tags’ has seemingly resolved the issue… Which is strange because it didn’t resolve it last time I tried, however several plugins, including VisualComposer have been updated since then. I suppose it’s counter-intuitive that in this case ‘stop removing P and BR tags’ does the exact opposite – but your explanation in relation to wpautop() makes perfect sense! So I can understand why it’s called what it is :).

    Thanks again for taking the time out of your day to reply!

    Michael

    (@mixey)

    Hey guys, I’m glad to say that this is finally tracked down and fixed. It will be available in the next update (4.8.1). Thank you for the input!

    ygirod

    (@ygirod)

    @mixey: It seems it’s not completely fixed with 4.8.1. In Tabs element, when you change a tab, this tab goes OK but unfortunately the others goes with line breaks problems.

    pavelthq

    (@pavelthq)

    @yhirod, Thanks for reporting. We added in our bug repository and will be checked in bug fixes release.

    pavelthq

    (@pavelthq)

    @ygirod, Can you provide more details about this issue?
    How we can replicate (screencast would be great).

    Is this repeated in frontend editor? Or only backend editor issue?

    pavelthq

    (@pavelthq)

    We could not replicate this issue.

    Hi there, I can confirm: while using V 4.8.1 that came licensed with the theme BRIDGE , the paragraphs/breaks are ignored.

    did you get the bridge theme fixed?

    Hi there, I found out that there was a htaccess /that was in the folder to for safety reasons) blocking the Tiny MCE from working. I found out by using the Dev tools from Chrome…

    hope that helps…
    P.-

    Hey guys,

    I also experienced this issue. When I save this html on “text block” editor <p>first paragraph ...</p><p>Second paragraph ...</p> it works for the first time but two <p> tags seems to get merged into one like <p>first paragraph … Second paragraph …</p> whenever I made changes on page and save. I also tried this code which usually works with wordpress default tinymce `remove_filter( ‘the_content’, ‘wpautop’ );
    remove_filter( ‘the_excerpt’, ‘wpautop’ );` but no effect on this one.

    wow I didn’t read the above conversation carefully, “Stop removing the <p> and
    tags when saving and show them in the Text editor” removing that tinymce option fixed this issue.

    this is the location of the checkbox option
    Dashboard>Setting>TinyMce Advanced

    Cheers
    Zaw

    Hello sirs. I’m currently using Visual Composer 4.12.1 and the issue is still present. Can anybody else reproduce it?

    Steffi

    (@steffievolvcom)

    We have the same issue – using VC 4.12.1 and Tiny MCE plugins and changing that one setting did not do the trick. Could you please look into fixing this? Pretty major issue I would say when it affects formatting.

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Plugin conflict – Visual Composer and Tiny MCE Advanced’ is closed to new replies.