Search results

Hello, You can create new domain in Plesk and then import site into it: Website Migration. If your site based on WordPress, Joomla!, Drupal, PrestaShop or Magento, it will be adjusted to new environment automatically.

Thank you for feedback, this issue now fixed. I apologize for inconvenience.

Hello! Could you please try site import feature: Website Migration. Looks like it is all that you need. You will need to create subdomain manually in the target webspace and then import content from the source using site importing.

Could you please clarify, does it block migration? Or migration of affected subscription completed with this error/warning message? Could you please add a block of info.log for details?

All files normally should be owned by system user of subscription, is it right?

Looks like an issue with permissions on uploads directory inside of wp-content. Could you please check it? Such issues could occurs, for example, if PHP works as mod_php on the source server before migration.

So, after migration you see an empty list of WordPress instances in WordPress toolkit, right?

Do you migrate whole subscription, or just sigle site using site importing feature?

Hello! Could you please clarify, how do you perform a migration?

Could you please clarify, which Plesk interface do you use: service provider view or power user view? Is there an anility to go to the list of WordPress instanses? By the link from right menu, for example?

Hello! Looks like data on your source Plesk server is in inconsistent state: one of domains assigned to hosting plan, which belongs to another vendor. There are several ways to fix it, I whould like to suggest you the most universal way - to create hosting plan named 'Mini' on the target Plesk...

I got it, looks like your WordPress instance initially installed via Applications catalog. That's right? Such applications associated with their databases and controlled by Plesk. WordPress Toolkit has ability to take over WordPress instances, installed by a such way, but unable to detach it...

Hello! In this case you can just detach extra instance, not remove it. You need to go to the overview screen of WordPress instance, do you see there Detach button?

So, database of your WordPress located on local MySQL server (database server, where Plesk database located), with default port, that's right? Probably, WordPress Toolkit unable to parse wp.config.php and extract database user name or database password incorrectly... could you please send me...

Looks like WordPress Toolkit unable to dump database of your source WordPress instance using access credentials, retrieved from the wp-config.php of this instance. The initial issue EXTWPTOOLK-636 fixed in WordPress 2.2.0 (WordPress Toolkit - Plesk Extensions): [-] If cloning of a WordPress...

It looks strange... anyway, you can download latest version of WordPress Toolkit here WordPress Toolkit - Plesk Extensions and upgrade it manually.

This numbers means hours when task is running: 04:00. 08:00, 12:00, 16:00, 20:00, 24:00. On Unix this schedule could be specified in short form, but we use common format for Unix and Windows scheduler implementation.

Hello, That's about tasks, related to WordPress Toolkit module: 1. /opt/psa/admin/plib/modules/wp-toolkit/scripts/maintenance.php - runs every 4 hours, validate cache of the list of avaialable WordPress versions and languages, refresh cache if it expired. 2...

Hello, Similar issue could occur when WordPress options "siteurl" and "home" for some reason was incorrectly replaced in the database of the clone. Could you please check it directlry in database (see attached screenshot) or via WordPress administrator dashboard? Both options should have the...

Hello, We confirm an issue EXTWPTOOLK-697, we will fix in future releases of WordPress Toolkit. I apologize for inconvenience.