Molongui Authorship keeps track of the number of entries an author has written. Each time a post is added, edited or trashed counters are automatically updated for the involved post and authors.
However, when activating the plugin or changing post type configuration, post counters need to be initiated/updated globally. Depending on the number of posts and authors you have in your site, that is a process that might take a while. So the plugin runs it as a background task. And when it is running you will see a notice on your Dashboard like the one below:
The notice will be displayed on your Dashboard on every page load. Doesn’t matter if you dismissed it in the past.
Only once the process has finished, the notice will go away. Then you will get notified with another notice that will be displayed only once:
Wrong Count Displayed
Post counters are initiated when the plugin is activated. And that is a process that is run in the background. But it can only be run if the WP Cron is enabled. By default it is on all installations, but you might have disabled it.
So, if your post count values are wrong:
- Make sure WP Cron is enabled and able to run normally
- Go to Molongui > Authorship Settings > Tools > Authorship
- Locate the “Update Post Counters” option and click on the Run button
Once post counters are updated, you may disable WP Cron again, although it is not advised.
Data Updater Notice Doesn’t Go Away
Updating post counters is a process that usually takes only a few seconds/minutes to complete. So the notice letting you know the background task is running should go away in a short while.
However, and as stated above, it might take a long while. Even days. Why that much? Well, in order to prevent timeouts on sites with thousands of posts and authors, the update process is split into smaller chunks that are processed on low priority.
So, if your site has a lot of posts and authors, don’t worry if the notice doesn’t go right away.
What if your site doesn’t have that many posts nor authors and the notice is still there? Well, chances are that, while the task was running in the background, you, somehow, disabled the WP Cron or introduced some server configuration change that is preventing the WP Cron to run normally. So please make sure WP Cron is enabled and able to run normally.
Having WP Cron disabled will prevent the background process to run so post counters might display wrong values.
Please note that web server configuration might also be preventing the WP Cron to run. Even if you have it enabled! For instance, control access using HTTP Basic authentication kills WP Cron. In that case, the easiest solution is to install a plugin —like WP Cron HTTP Auth— that allows WP Cron to get around the password protection.
