I purged all caches, synchronized all sites to the dashboard several times, but the dashboard continued to show that WordPress Core needs to be updated to 6.8.
On the Insight tab, the WordPress version distribution says all sites are on 6.8., and the Recent activities log lists the exact date and time of core updates to 6.8.
Update: I had updated all sites manually, and this was not reflected in the list of available updates in the dashboard. Now, after starting the updates in this dashboard list, the updates are shown succesfully as described in
Hey @Peter46
I was unable to reproduce this issue of MainWP Dashboard incorrectly reporting that Core needs to be updated even when on latest version.
If the issue reoccurs for you, please open a private Help Desk ticket and we will gladly look into this: https://mainwp.com/my-account/get-support/
To make it easier for everyone to follow the discussion around that issue of Site IDs being shown after Core updates, let’s continue troubleshooting in the thread @josklever opened.
Feel free to also provide answers to questions I asked Jos’ in my message here: Update status WP core shows site id - #2 by bojan
If you update a site to WP 6.8 outside of MainWP… MainWP does not detect this during the regular site syncs. If you manually sync an individual site, it will pick it up in the site view, but the overview page (and subsequent WP updates in ‘See Details’) does not pick this up.
As the OP pointed out, running the update from MainWP does then show the correct result… but this isn’t how it should work.
Same here. I’d like to add that the Events log does show all manual updates successfully completed. This includes Plugins, Themes and the WordPress update. However, the dashboard after several re-sync actions still show those items need updating. Frustrating when you have over 30+ sites to keep track of!
Thank you all for the additional details.
I was able to reproduce the issue by following these steps, and forwarded it to our development team.
The fix for this will be included in an upcoming Dashboard release.
Any idea when this fix will be released?
The fix for this issue was included in the v5.4.0.6 of MainWP Dashboard released on 04-22-2025.
Thanks again for reporting this to us.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.