Resolved Error when opening Wordpress Instances Overview in Plesk

[vic666]

Using wp-toolkit, I registered and installed a new instance into the folder EXAMPLE.COM/wordpress. Afterwards, I changed my mind about this and wanted to put the installation back into the root folder.

I was under the impression that should be easy enough to do, but apparently it's not. Yesterday, I started with this:

1. I logged into the WP Admin panel and manually changed the URL. After this, I could no longer reach the WP Admin site.
2. In the vhosts folder on the Plesk system, I manually moved all files from ../httpdocs/wordpress to ../httpdocs. Now WP Admin would work again.

Apparently, though, I missed something and that had an unexpected effect. Overnight, Plesk tried to update this WP instance and failed because it could not find the files.The log shows the following error message:

Website "/httpdocs/wordpress" (example.com): Failed to reset cache for the instance #4: filemng: Failed to change directory to /var/www/vhosts/example.com/httpdocs/wordpress: No such file or directory

This doesn't sound too bad by itself, clearly the name must be updated in yet another place, that's all. Or at least that's how it should be, instead, I can no longer access any Wordpress instances form the Plesk control panel, I get the following error:

InstanceProperties.php:
Return value of PleskExt\WpToolkit\Db\Dictionary\InstanceProperties::getLastUpdateProposition() must be an instance of PleskExt\WpToolkit\Model\UpdateProposition, bool returned

It seems that the failed update led to another error that does not seem directly related. This actually looks like a bug in Plesk to me.

So, I guess I have two separate issues now:

Most importantly, how do I get rid of this error message and back into my WP Toolkit overview?

Secondly, can you confirm that in order to change the installation path, the following steps are sufficient:

1. Change path in WP Admin panel
2. Manually correct path in /var/www/vhosts/mysite
3. In wp-toolkit.sqlite3, in table Instances, change "path" to reflect the new path.

 

[vic666]

Just some additional info: Only the admin profile is affected where the domain in question is associated. Customers can still get into wp-toolkit.

 

[Aleksey Filatev]

Thank you for the detailed report! We will reproduce and it as soon as we can and will give you an instruction on how to fix it before the official fix will be released.

Regarding changing the website path, it's quite a tricky thing to do it manually. But WordPress Toolkit provides the easiest way to do it - all that you need is to clone a website from one location into another.

 

[sds_Novo]

Hi, I've done your tricks and lost WP site. Running "instances-auto-update" task did not cause your error " Failed to reset cache for the instance ..." in log. Later this instance was indicated as broken, but detachin it and then scan fixed instance problem and site seems working good.
As Aleksey recommended simplest and reliable metod is to clone WP instance to existed domain.

 

[sds_Novo]

Hi, Custom activity with high priority created for this issue

 

[custer]

@vic666 WPT has the "Update site URL" feature that should be useful in your scenario. After manually moving WP from one directory to another, open the hamburger menu in the top right part of the website card and use the "Update site URL" option. This should change the URLs in WordPress based on the actual domain/path where WordPress is currently hosted.

 

[Mihail Boiko]

Hi. Thank you for your patience.
We have investigated the scenario you have described and found no way such issue could occur by operating the toolkit. We have supposed it caused by WordPress Toolkit database inconsistency happens during attempts to move website by altering WordPress Toolkit database manually. Anyway, there is a solution we will be glad to suggest to you: Open your WPT database and execute the query below.

DELETE FROM InstanceProperties WHERE name="lastUpdateProposition";

 

[vic666]

Hi all, sorry it took me a long time to reply. I just tried Mihail's suggestion, and this seems to have done the trick. Now, WP Toolkit would start again. It would show me a broken instance under httpdocs/wordpress (which no longer exists since I moved the files). I was able to remove this instance. The database and user were not removed because they are still in use by the httpdocs instance.

I then received an error saying "An error has occured when deleting WordPress website on "example.com" in /var/www/vhosts/example.com/httpdocs/wordpress: filemng failed: filemng: stat filed: No such file or directory. System error 2: no such file or directory.

Anyway, it seems this error can be ignored. Thanks for your support.