Fran Ontanaya

Thanks for the feedback! I’ll keep trying to optimize it on the next upgrades.

It should take only a few minutes, tops. That means it’s probably stuck. Possible reasons could be:

* The site is on shared hosting with very little resources and the stats worker is timing out.
* The site is on an older version of PHP and/or WordPress.
* Something is failing when processing one of the posts.

It could be some conflict with the registering of CSS / JS for the plugin, since the front end was still working. There’s a few changes on 4.5.0, but all else being equal I wouldn’t expect it to be fixed.

I haven’t done much testing on very large blogs either.

I’ve changed how execution time is handled on some parts for 4.5.0, but apart from trying to raise it (if the server allows it) in the stats page there’s no permanent fix yet.

The issue is that on a blog with a lot of posts the plugin can take a long time to collect all the data, and I haven’t modified it yet to do this in small chunks for the stats page.

I haven’t ever tested Word Stats on multisite — I’m afraid I may not get around to support it in the short term.

It’s probably picking up posts from all sites, since the queries make no distinctions.

Shorcodes are filtered out on the non-live side on 4.5.0. I’ll look into inline HTML attributes/styles later on.

I’ve changed this on 4.5.0. Stats still won’t be displayed when data collection is not finished, but the submenu won’t be hidden.

Hi! As you may have noticed I haven’t had the time to push new updates. I will definitely be busy till February, I’m afraid it’ll remain non-functional until then.

There’s a couple options in the Settings page to ignore words (and to ignore common English words specifically), though some people reported it not working in the live stats under the edit post box.

Multiword matching isn’t available yet, but I’ll add it to the To Do list. It’ll have to be a white list so users tell the plugin which multiword keywords to look for, otherwise it may take too long to process.

Try wrapping each word like this: ^php$ (that shouldn’t be the problem, but still…)

It can possibly be something wonky on the javascript side. For now the live counts are a port of the counting algorithm into JavaScript. If I get around to push the next version it will use only the PHP algorithm for everything and that should fix this kind of issues.

It can be changed in the settings page, although someday I’d like to have more advanced settings so people can say, for example, status post formats should have 300 words max, but standard post formats can have any length, etc.

Until we find the cause, an option could be to disable wp-cron running on page loads and instead use a real cron job to trigger wp-cron every few minutes:

https://wpdailybits.com/blog/replace-wordpress-cron-with-real-cron-job/74

I’ll add manual running to my to-do list.

Probably not, but I’ll think about it. After activating it, does it display the yellow message that says, “Word stats collection is scheduled (x posts left). Stats will be available in a little while”?

The simplest reason for it failing would be that the script is timing out before it finishes its task of processing even a single post. Do you have very large posts, or is the blog hosted in a slow server?

I’m very interested in your issue, since it shows only in one of the blogs, so I’d like to know any differences between both you can think of.

Thanks. Don’t forget to rate the plugin!

No, it’s fine to send me questions here.

There’s the shortcode [wordcounts] and a widget to display the total counts, but I haven’t done anything regarding public display of stats ever since.

It’s included in a list of near 200 items I want to implement, but, being currently unemployed and bootstrapping a little startup, I have to either wait till I can put time in Word Stats or make new features commercial. :/