Search results

We a working on this issue now and update will be published as soon as we can. Switching domain, on which WordPress installed, to PHP 5.4 or above will help to avoide issue. After refreshing, instance will not be broken anymore.

Hello, We confirm bug EXTWPTOOLK-1354, it will be fixed in neares update of WordPress Toolkit. I apologize for inconvenience.

Thank you for feedback! We will check this issue on the same configuration.

Could you please clarify, which version of PHP used on domains with broken instances?

Hello, Thank you for feedback! We just published an updated WordPress Toolkit, version 3.0.1 (WordPress Toolkit - Plesk Extensions), which includes the fix for this issue. I apologize for inconvenience.

Database structure looks good now. Legacy "ownerId" columns in Plugins and Themes tables replaced by "ownerGuid" by one of latest upgrade steps, as expected. But version of database structure is wrong. It should be a timestamp, like this: sqlite> select * from version; 1|2017121502000 Thats...

Looks like an issue occurs during previous upgrade for some reason and database of WordPress Toolkit is in inconsistent state right now (upgrade of database structure is the latest step of module upgrade, so it does not block it). Such error for sure will occur during all future upgrades. It...

Hello! Could you please clarify which version of WordPres Toolkit already installed and which version do you want to install?

Hello, I regret that I miss your question and did not answer it in operative manner. The directory /var/www/vhosts/<domain_name>/.wp-cli/cache which you can see in your subscription's home is the part of WP-CLI caching mechnism. As you can see, WordPress Toolkit uses WP-CLI for managing themes...

Hello, I would like to suggest you to use Plesk Migrator extension Plesk Migrator - Plesk Extensions to import domains from the list of supported hosting panels, like cPanel, DirectAdmin, legacy versions of Plesk, etc. If your websites hosted on those panels, you can easily import them at once...

Hello, Latest release of WordPress Toolkit (version 2.4.1) adds some features which could be useful: There is an option "Allow to copy wp-config.php during file synchronization" at Global Settings tab of WordPress Toolkit. Anyway, database connection and other things will be ajusted during...

Hello, Thank you for feedback! Glad I could help. Unfortunately, with this workaround you can not use new WordPress Toolkit feature: fast WordPress instances synchronisation with ability to copy only modified files, because it required rsync. We can investigate the root cause and, I belive...

I apologise for the inconvinience. Could you please check, is your source and target subscriptions located on the same node, or on different nodes? It could give us an idea there could be the root cause.

Hello, When copying content between different subscriptions WordPress Toolkit starts rsyncd under source subscription user and then starts rsync client under target subscription user. When started, rsyncd bind to localhost and listen on 11000 port (could be configured via panel.ini using...

Hello, You also can specify option 'disable-cleanup' as desribed at Managing Let's Encrypt Settings, which allow you to check validation URL manually. Probably there are specific redirection or URL-rewriting settings on your domain?

Hello! Could you please check, is update of this plugin available directly from WordPress instance?

Hello, Thank you for feedback! You can change this behavior by putting following lines into Plesk configuration file (panel.ini): [ext-wp-toolkit] allowInstallAddendioPlugin = false In future versions of WordPress Toolkit we plan to expose this option into user interface.

Looks like initial data on the source website stored in non-UTF8 in the source database. In other words, tables encoding is UTF8, but stored text has another encoding. In certain cases such data could be corrupted while importing database. Could you please take a look on the corrupted text in...

File "/opt/psa/var/modules/panel-migrator/sessions/site-migration-1/debug.log" is the right place. Could you please serach log entries with the following prefix: "Upload file via FTP: " Such entries should be below info message "Deploy web RPC agent to the source website".

Could you please check log of web RPC agent? It should be placed at the same directory on your source hosting where web RPC agent entry point placed. You can browse the document root on the source (it should be directory with long randomly generated name) or find the exact path in the debug.log.