Conflict with livecomposer

  • Resolved m_demori

    (@m_demori)


    7 years, 11 months ago

    Hi,

    this plugin make livecomposer (https://livecomposerplugin.com) plugin unusable on edit mode. When is active randomly interfere with hidden textarea content used by the composer to maintain the page code.

    Tthere is a way to disable the plugin for some specific url? when the livecomposer editor start the url became something like:

    https://localhost/wp-admin/admin.php?page=livecomposer_editor&page_id=0000

    so if i can exclude the /admin.php url from plugin filter i can solve all problems.

    Here you can find a detailed report of that issue that I open to livecomposer error tracking https://github.com/live-composer/live-composer-page-builder/issues/632
    I send this report to livecomposer because at first I thought that the problem relies on editor but after disabling all plugin and re-enabling one by one I found that the problem is caused by CM Tooltip Glossary. One of the biggest problem is that this issue is pretty random, on most cases is related to URI that is “escaped” with / and sometime is relate to random <br /> added to hidden fields used by livecomposer.

    Thank you

    • This topic was modified 7 years, 11 months ago by m_demori.
Viewing 1 replies (of 1 total)
  • Plugin Author CreativeMindsSolutions

    (@creativemindssolutions)

    Hi m_demori,

    First of all I’m really sorry about your problems. From what I can see you’ve spent a lot of time and efforts trying to debug the issue.

    Unfortunately the plugin doesn’t have the ability to turn off the parsing on url basis. But it’s possible to turn off the parsing per page basis or to turn off the parsing of part of the page by wrapping with the [glossary_exclude] shortcode.

    Also the plugin is only using the_content() filter for the parsing, so with the right hooks it should be possible to temporarily turn off the parsing for the livecomposer and turn on afterwards.

    Best,
    CM Plugins

Viewing 1 replies (of 1 total)
  • The topic ‘Conflict with livecomposer’ is closed to new replies.