Search results

There is a case, known as an issue EXTWPTOOLK-1844, when WordPress instance exists (and recognized by WordPress Toolkit) but hidden in GUI. Could you please list all instance via CLI: plesk ext wp-toolkit --list Do you see your instance in this list?

Thank you for feedback! I confirm a bug PPPM-9388. WordPress Toolkit services, listed at the Accounts tab of the subscription - are services, which could be added to hosting plan or subscribtion. There are several services provided by WordPress Toolkit by default: - Install WordPress (will...

Could you please give us access to this test Plesk server for investigation? Basically, WordPress Toolkit uses wp-cli to link with WordPress sources and execute it. So, if the instance code is infected, the issue which you describe could be possible. Actually, you can detach the broken site from...

WordPress Toolkit unable to retrieve administorator password from existing instance, because only hash of this password stored in WordPress instance database. But WordPress Toolkit is able to set new administrator password. In this case toolkit will remember entered password and after that...

Database name here - is the name of the WordPress instance database, specified in wp-config.php. It can not be changed via WordPress Toolkit. But if you somehow change it manually, toolkit will know about it and display updated info.

Thank you. Could you please run scheduled task manually and look for errors in log? It could be done by the following command: /usr/local/psa/admin/bin/php -dauto_prepend_file=sdk.php '/usr/local/psa/admin/plib/modules/wp-toolkit/scripts/instances-auto-update.php' If no errors will be...

Thank you. Could you please also attach a screenshot with Update Settings for this WordPress instance?

Automatic updates of WordPress core, plugins and themes occured once a day by scheduled task. Could you please clarify, is your theme is marked as outdated at the card of WordPress instance at WordPress Toolkit?

Thank you for feedback! We confirmed a bug EXTWPTOOLK-1664. It will be fixed in the nearest update of WordPress Toolkit module at the begining of next week. I apologize for inconvinience.

Hello, Could youi please clarify your scenario? As I understand, you just setup a WordPress Essentials set and specify service plan settings to install WordPress with this set automatically on new subscriptions. Then you create a new subscription according this plan and found that WordPress was...

Sure, if you need to migrate just a few sites you can use Site Import (http://extore.pp.plesk.ru/packages/da879838-ad5e-46f3-8a2c-36d26adbd218-site-import) Plesk extension. It allows to import both sites and mailboxes content from any remote server into Plesk.

I am glad to inform your that the issue EXTADVISOR-429 fixed in Advisor 1.3.1 which published a few minutes ago: Advisor - Plesk Extensions.

Hello! Unfortunately, Plesk Migrator can migrate only from live servers (which operate properly), so at first you need to fix your source Plesk. I would like to suggest you create a support request for assistance.

Thank you for investigation! We will definitely check this case as soon as we can to confirm a bug.

Could please check real permissions on files and directories of your WordPress instance? Is there are anything differ than 644 for files and 755 for directories?

Thank you for feedback, we will check this case carefully.

Could you please check content of /var/log/plesk/panel.log file? Exception stacktrace should be placed here, this could help us to find the root cause.

The most easiest way to move your WordPress site from one domain to another withing the same Plesk server - using the cloning feature of WordPress Toolkit: WordPress Toolkit. For more generic case, if you need to move a common web-site from any server into Plesk, we have the site importing...

Hello, WordPress Toolkit include special patched version of WP-CLI. Also, versions of several critical packages are fixed to ensure stability of toolkit itself, because it operate with WordPress instances via WP-CLI. So patching of WP-CLI or installing of additional packages are depricated and...

Looks like an issue occurred while retrieving list of instance at backend side. Could you please check panel.log - is there any errors or long-running operations while list of instances is loading?