Conflict this morning 0.05am Page builder noted to have disappeared off posts and pages sending site into disarray.
The plugin was deactivated and reactivated to no avail. All plugins were then disengaged except page builder. One by one each was added back in , checking all was well between every new addition and that the page builder remained available in post and page.
Until the Yoast SEO plugin then the page builder disappeared.
Something happened in the wee hrs of to day and I don’t understand. I am using windows 10 if of any significance.
I cleared the laptop cache and temp files to find the site returned to it agreeable presentation as if nothing had happened. So making Yoast SEO inactive I cured the problem? or was there more to it , its hard to tell.
on first entering the site I had a server connection problem for the site so I will ask BlueHost if they have any ideas
What concerns me now is shall I switch on the Yoast SEO plugin or not help anyone?
We LOVE the page builder although this hasn’t been the first time it has given us conflict issues, all in a days work I suppose, keeping up with all that moves forward technically.
Many thanks Site origin for making it so easy for us non website builder types, nervous ones at that
Hi Doindubai,
Thank you for the kind words and I’m sorry you’re having issues. :(
This sounds like a Yoast issue – although that’s really uncommon. Can you please try temporarily enabling Yoast to see if the issue occurs? If it does, could you please send me the contents of your console (when viewing the issue)? Please refer to this guide on how to access your browser console.
Thank you Alex
I re installed toast this morning as it had a plugin update and all seems well for the moment
Good to know you are there
I am away from the desk for two days I will read the guide on return and be prepared to report back should problems have reoccurred
Thank you Alex
Monica
Hi Monica,
Great to hear that it’s currently working without issue. Let me know how you go mate. Please note that the article I referenced is only really applicable if the issue occurs again so please don’t feel obligated to read it.