I don’t think that for this solutions is a problem support ClassicPress. Consider that 1.x is based on 4.9 with only few things changed (php minimum, composer support, rebranding) and probably bugfixes and performance improvements from 5.0.
In few words the best from the 2 worlds so this tools because support also old wordpress version should not have issues with them also because they use the wordpress internals that are the same of classicpress.
InfiniteWP checks the WP theme and plugin repositories to look for updates. I can add a CP site to IWP and track updates right now without issues. When (and if) there are CP-only themes and plugins that aren’t housed in WP repositories, they won’t be included in the update search unless (a) there are central CP repositories and (b) IWP decides to check those repositories as well.
1 Like
I use InfiniteWP to manage over 40 sites (a few of my own, and many client sites). I’ve converted a few to ClassicPress now.
It works fine, what I did notice, in one case, I needed to deactivate and activate it again in the IWP panel to login directly from InfiniteWP to the website’s admin panel (passing by the “login screen”). This was with a website that has gone from Wordpress 5.0 to ClassicPress 1.0.
On other sites, that were converted from Wordpress 4.9 to ClassicPress 1.0., I didn’t need to de-activate/activate the plugin.
Anyway – IWP works fine so far. To my relief 
I had contacted both iControlWP and BlogVault (as already mentioned), that both allow such site management (plugin updates, etc.) from a central place.
For the time being, no commitment from iControlWP, mainly due to additional workload it would mean and uncertainties about the prospects of CP; in case, CP gains a strong following and iControlWP gets a number of requests, I understand that it might be considered.
As already mentioned in another thread, BlogVault promises to support ClassicPres. And they seem serious about it. See the attached screenshot of my BlogVault panel: the site on the top has been switched to CP. In the listing, it shows as being on WP 4.9.9, but not in need of update. The site below (as well as the other ones) are still on WP: they are listed as being on WP 4.9.9, but in need of update (yellow), which shows that BlogVault recognizes the CP site as different.
I have written to support suggesting that CP sites might be listed as such, instead of being shown as WP 4.9.9 - but I could understand that they would prefer to wait until the stable v. 1 is out.
The real test will be if the core icon will turn yellow at the time CP updates come.
I would say that such management tools have saved me many hours of work, and allowed to keep an overview on the status of some fifteen sites. Definitely, I could no longer see myself working without them in the long-run. Not even mentioning the safety provided by those external, easily restorable backups.
1 Like
Noticed something interesting with InfiniteWP this morning (might’ve been this way all along):
If I look at site details for a ClassicPress site, it shows WordPress v4.9.9. That part I already knew.
What I noticed today is that CP sites are not included in the list of sites that need WP core files updated.
This isn’t v1 related, but MainWP still isn’t recognizing CP core when checking for updates, just WP.
Details:
- MainWP Parent site is on CP.
- All children sites on CP.
- MainWP Parent site does scan all the plugins on Children just fine, just not CP core.
Not sure if this would be an easy fix, but needed imo.
1 Like
You’d need to contact MainWP to ask about this I think. It’s the same with InfiniteWP and they’ve told me that if there is enough interest they’ll add support for CP.
3 Likes
My last couple of updates have been picked up by ManageWP just fine. The most recent one, I used ManageWP to update, and everything worked.
1 Like
So ManageWP is updating core files? Interesting. I’ll have to give it a try. If InfiniteWP don’t move on this I may switch.
1 Like
Correct me if I’m wrong but I think ManageWP is a remote hosted service?
So you can’t maintain localhost or private sites with it, only live sites.
To manage sites on a local server, you have to use either InfiniteWP or MainWP, because they’re self-hosted solutions and therefore you can install them on your localhost server.
This may not be an issue for everyone but will be for some I’m sure (including me). I’m hoping MainWP will jump on the CP bandwagon.
Public stats showing how many CP installations are out there would help with this I think.
1 Like
I don’t think you can manage localhost with it. But it helps with cloning websites and transferring them to and from localhost.
This is coming soon! Our process to collect this data came online a few days before the release of 1.0.0, and I’ll be working on analyzing it next week.
8 Likes
Excellent news James - I think there’s a lot of us that this will be helpful for.
1 Like
MainWP
If you’re interested in MainWP support for ClassicPress I’d recommend hopping over to the MainWP forums and letting Dennis know your interest. Especially if you’re a MainWP Pro customer.
He’s trying to gauge the ClassicPress roadmap and the size of the community to see if it’s worth his while to spend resources to support “another CMS” as he put it.
2 Likes
Problem: there are still no CP usage stats, 2 years later.
1 Like
They are coming. Hopefully soon.
2 Likes
Maybe we’re not all on the same page regarding what “soon” means. 
Emphasis added, but, that was back in March of 2019. 
I have spoken with James recently. He said that with all the additional help with the core development, he has time to work on compiling usage stats from the logs. So fingers crossed 
3 Likes
This has changed since it was written back in 2018. WP added support for a plugin header field called Update URI, so the core logic can be used on an external repo. They are supposed to add it for themes in the next release.
2 Likes
Looping back to some of the discussion here (for anyone coming directly to this link), we did get updated usage stats: ClassicPress Usage Report - September 2021