I have recently installed the Site Origin page builder plugin, version 2.1.4. I also installed the Black Studio TinyMCE Widget, version 2.2.5 to use as my visual editor on my pages.
When I add the visual editor widget to my page, it does not allow for any visual editing (bold, bullets, etc).
When I select DONE after editing, none of the edits show up.
After testing the deactivation of the plugins, I determined that the problem was caused by the combination of Wishlist Member plugin and Page Builder plugin.
The Wishlist plugin is crucial for the site, since it is a membershipsite, where access control is done via Wishlist.
Could you please look into this issue.
What I do as Workaround is deactivation of the wishlist plugins. Than make the adjustments and then activate the Wishlist member plugin again. This works for now, since the site is not yet live. But once we have members accessing the site, it is not possible to de-activate the Wishlist member plugin.
Ik hope you manage to solve tis quickly.
Cheers, Ron Scheerder
Conflict tussen Page Builder en Wishlist Member plugin
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hello,
I still did not receive any reply to this issue!!
Please respond asap, since we can't go live as long as this is not fixed.
Regards
Ron Scheerder
TOP Academy
Hi Ron
Sorry for the late reply. Here is some information on how our system prioritises support threads – https://siteorigin.com/about/forum-thread-prioritization/ – we’re working on a premium support offering for Page Builder that’ll ensure fast replies even if you aren’t using one of our premium themes.
I’ve made a note of this conflict, unfortunately they’re difficult for us to fix from our side. Have you contacted the developers of the Wishlist member plugin to let them know about the conflict?
One thing to check would be to see if it’s causing any JS errors. These errors in other plugins can cause Page Builder to stop working – which is why deactivating them fixes the issue. Here is how you can check.
http://codex.wordpress.org/Using_Your_Browser_to_Diagnose_JavaScript_Errors#Step_3:_Diagnosis