WP Workbench does not add some WordPress forks

Virtualmin
1
SYSTEM INFORMATION
OS type and version Ubuntu 24.04.3 LTS
Webmin version 2.610
Virtualmin version 7.50.2 Pro
Webserver version Apache

I just installed WP Workbench, I have 32 Wordpress sites on my server, 13 of them didn’t import. I tried both Refresh Instances and Import Instances. I do not see any option to manually import via GUI, I read you can do virtualmin detect-scripts --domain … --dir … which also did not bring in the site. Is there another way to force the sites to import or something I’m possibly missing here?

2

Virtualmin generally detects things to import based on ownership. Who owns the sites that didn’t import?

3

How do I know who the owner is?

4

That is really odd! It should work despite anything with the latest WP Workbench 2.0.7.

You shouldn’t really use it because WP Workbench uses that feature internally in a more advanced way.

For sites that do not import, is there a WP-CLI command under the WordPress installation or domain home? Can you check it?

Also, what does the “PHP Options” page show for those WordPress sites that do not import?

Lastly, can anything useful and related be found in the ~/logs/ directory?

5

There was a previous question about the owner, I’m not sure at what level the ownership would apply here as there isn’t really a corolation to ownership of these sites, they are all hosted for customers. I believe all sites were originally created by the same user, but they would all have different ownership.

As to your questions. I do have the latest version as I just installed it and ran updates.
For the manual run, was just an attempt to get it to work.

I have not manually installed WP-CLI anywhere and running wp-cli or wp via cli returns not found. So I don’t think that’s the issue since other sites do work.

PHP Options is setup the same between working and non working sites.

One site is a direct copy for development, the development copy works and the non-dev site does not. This makes it even more strange.

As for logs, there does not appear to be any WP-Workbench longs in /var/log or ~/logs otherwise the access, error and php logs look normal and I don’t see any wp-workbench events in the logs either.

One other note, on the one with a normal and dev site, the Refresh instances function does find both sites, but it only adds one, it’s possible this is a bad example it might just be seeing this as a duplicate and not handling it properly. However, I do have other sites unrelated to this example that are running Wordpress but not being added or found in the Refresh or Import functions.

6

By “owner” I mean what user owns the site in the filesystem and database. Nothing to do with who the site is for. I’m only ever talking about technical details.

But, Ilia knows much more about how WP Workbench thinks about who owns a site and how it can be imported that I do, so he’s the one with the most useful questions and answers.

7

I think I found the issue, but not sure how to fix it. The sites that aren’t loading used “custompress” web app instead of Wordpress. I think these were setup LONG ago, so it was probably an old version of the wordpress installer.

So the question is, how do I update Virtualmin to see these as having Wordpress?

Thanks

1 Like
8

Ah, we never claimed to support “custompress”. :wink:

I think it depends on how long ago and how much it diverged from WordPress as to whether it can actually be managed by Virtualmin and WP Workbench in a reasonable and safe way.

9

You probably need to remove custompress and use WordPress instead. :slight_smile: If I understood correctly, custompress hasn’t been supported for over 6 years. We can’t support obsolete software.

10

I wouldn’t expect you to support custompress, and yeah those sites are that old. But my question is, if I remove custompress and install WordPress I assume I’d have to redo the sites or would it be safe to do this without losing data?

11

That question shouldn’t be addressed to us because we’ve never heard of ‘custompress’ before and don’t know anything about it.

12

Yeah, I wouldn’t want to make any suggestions about something I have no experience with.

If there is a way to convert a custompress installation into a regular (and up-to-date) WordPress installation, that would be where I’d probably want to start. (You know, after making sure I have good, recent, tested, backups. Since changing CMS seems like a dramatic/risky thing.)

13

You might get better help from Word Press centric sites. It seems at some point custompress was an add on that did things the basic WP software now does so it was no longer needed. (That’s from just a quick read of the github repo page.) I doubt it can now be backed out if any of the features were used.

Did WP continue to update or are these sites are frozen as of 6 years ago? If so, you have little choice but to update them anyhow.

14

It is normal WP and updates, etc. But your on the right track, I believe we used custompress to install WP with the latest version or otherwise something the built in function didn’t do, might not have even been an option at that point.

I’ll just plan to reload the sites with WP function and restore sites in the future. At least I now know why they were not detected.

1 Like
15

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.