spotter698

I look forward to using Page Builder by SiteOrigin for many years to come.

Thanks Andrew, that’s an awesome support response.

I have installed your beta release and everything is working well now.

OK, I deactivated all Plugins one at a time and found that when SiteOrigin Page Builder (Version 2.11.3) is deactivated, everything works fine.

Do I need to advise SiteOrigin of this issue, or do you?

When I create a new Post using the Classic Editor (Version 1.6) I get “the text contains 0 words”.

When I open an old Post using SiteOrigin Page Builder (Version 2.11.3), the previous positive result with a Green light turns Orange/Red and says “the text contains 0 words”.

I haven’t tried to create a new post with SiteOrigin Page Builder as yet.

Apologies, I am using the Classic Editor for the posts which are showing up as errors now. But when I go back to edit previous posts using Page Builder by SiteOrigin, they also show the No Word Count error, even before changing anything.

Site Health is Good

I am using Page Builder by SiteOrigin, and have done so for over 12 months. This error is only new.

I will run the Health Check & Troubleshooting plug and advise further.

Sure, will do, even though it’s the same issue.

I’m getting the same error.

“The text contains 0 words. This is far below the recommended minimum of 300 words.” This happens, even when I have over 300 words. Doesn’t appear to be counting properly.

1. I don’t have any JavaScript errors.

2. Clearing the cache does not correct anything.

3. I have logged in using MS Edge, Firefox and Chrome and get the same response for all browsers.

Hope you can help.
Steve

My website hasn’t been changed for months, and I was just adding some new posts.

Don’t worry, I did a total restore of the website. Everything is working fine again. Thanks for your support/advice.

Apologies, this all occurred due to the fact I developed the website with a Temporary Domain Name, but just changed it with a Search/Replace plugin, so that the plugins and links worked under the new Domain Name.

Hope this makes sense.
Steve

Hi,

Thanks for your response. It’s very unusual, because this has been happening for potentially the last 10 versions of this plugin, but not hosted by the one single company. My sites are hosted across various hosting companies (e.g. Siteground and Hostpapa to name 2), and on different occasions I get this same error code.

Unfortunately, it is not consistent and sometimes it works fine, other times it doesn’t. This recent update, 2 out of 10 updates failed on the first run. Yes, they were both with the same company (Siteground) on this occasion, but it’s not always the case.

Anyway, I’ll keep an eye on it, but I thought I’d let you guys know, just in case.

And to answer your question, No I haven’t had this issue with any other plugin.

Regards,
Steve

Thank you. Your team provided the following resolution :-

“I am happy to inform you, that our development team has resolved the problem on your website. Could you please have a look? I should note, that we have made a custom change, as jQuery(document).ready function does not work with your website theme.

Please be informed, that there has been made a custom change, which indeed, will be cleared out in case of updating Photo Gallery plugin. The following file was modified by our developers:

/photo-gallery/js/bwg_frontend.js

You can create a backup of this file and replace it with the original file in case an update of Photo Gallery is installed.”

Not me. I’ve tried to upgrade for each new release up to Version 3.0.5, but it wrecks my site. I then have to roll back to Ver. 2.5.6

Version 3.0.6 has been released, but I haven’t tested as yet. I just haven’t got the time to waste.

Let us know how you go.

Word is on the MageeWP support page that all is OK now after updating to :

OneTone 3.03
OneTone Companion 1.0.9

Can anyone confirm this?