Search results

Did you try to remove this plugin directly from WordPress administrator dashboard?

I am apologize for inconvenience, we are still working on update, and Site Import v1.4.3 which will fix the issue will be delivered as soon as we can. I believe it takes no more than few days.

This issue registered as PMT-4694. Fix will be delivered with Site Import v1.4.1 in the middle of January, 2020.

As I understand, for each removal operation you have checked (default state) option to remove database and database user, is it correct? And second: was there any errors occurs during removals?

Could you please clarify, did you share any single database with several WordPress installations? And another one: did you use group removal of WordPress installations, or did remove websites one-by-one?

Plesk Migrator don't have ability to migrate cPanel packages. Regarding migration from Plesk, hosting plans could be migrated, but only with associated subscription. However, there is no ability to synchronize once migrated hosting plan: means if plan with the same name already exists on target...

Plesk Migrator will migrate hosting plan only then you start migration at least one subscription associated with this plan, and, at the same time, if plan with the same name not exists on the target yet.

Database and database users prefixes policy could be managed at Tools & Settings / Database Hosting Preferences.

Did you try to run update manually, via Plesk Extension Catalog? Is this error persist?

Could you please clarify precisely how have you moved your website into DigitalOcean? Which tools do you use?

Hello, Probably, requirements for your sites is differ... Could you please try to upgrade this website manually, using WordPress administrative dashboard? If the same error occurs, it is an issue with website itself, but if it's not, we will try to go deeper.

Could you please clarify, is WordPress Toolkit display avialability of updates for your sites? Is updates avilalble only for themes or plugins, or for WordPress core too? Which versions you have already and which versions are available? This information will help us to suggest a solution more...

Thank you for feedback! We confirmed an issue EXTWPTOOLK-3040: updating WordPress from v5.2.1 generate the error message you mentioned. Actually, upgrade procedure succeed, but a warning message, generated on it, assumed by WordPress Toolkit as an error and thus displayed in a such unpleasant...

I appologize for inconvinience, Drupal updates is on the way and will be available at the beginning of next week.

Do you mean paid version of an Elementor Page Builder (Elementor ★ Page Builder for WordPress) plugin?

It could be an issue with direct links between pages. Could you please clarify, how exactly links did not work? It means 404 errors occurred, or links from the staging follow to the original site?

Hello, It looks like a reliability issue, we are working on fixing that. For now you can just run an upgrade once again: it should be successful at this time.

Thank you for feedback! I just created an issue EXTWPTOOLK-2163. I belive we can automate clean up of the WP-CLI cached data in future releases of WordPress Toolkit.

Chache files stored at /var/www/vhosts/*/.wp-cli/cache/* are artifacts of WP-CLI utility which used by WordPress Toolkit to interact with WordPress instances. You can find more details at Question - .wp-cli/cache files. Regarding an option cacheDataByVersion, it's legacy and useless for now...

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?