No support, no answers

  • Sorry, even a question is not answered. This plugin, in its default configuration, damages code generated by other plugins because it runs wpautop() and texturizes after processing shortcodes from other plugins.

    A question asked here to inform me how to check the offending setting is not answered.

    I will now have to put this plugin on my blacklist, i.e. i will inform my users taht this plugin should be disabled.

    A pity, it should not be needed to do…

Viewing 1 replies (of 1 total)
  • Kenika

    (@kenika)

    This seems to be a serious issue. I’m also having trouble since I installed the plugin. I definitely want to keep it as I also already spent days in implementing it on every single side of my blog. But the issues are so strong that my blog is – since yesterday’s updadte of this plugin – not available anymore! I didn’t change any settings, didn’t install any new plugin etc.
    Since I updated: no more blog.

Viewing 1 replies (of 1 total)
  • The topic ‘No support, no answers’ is closed to new replies.