• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved Problem cloning migrated wordpress instance

pge

New Pleskian
Hey Forum,
i am trying to create a clone of a site which was migrated from another plesk server using the migration wizard.
This wordpress site has been successfully cloned many times on the old host.

Now after the transfer i tried to create a clone and get:

Argument 1 passed to PleskExt\WpToolkit\Service\Scheduler\SchedulerTask::setDescription() must be of the type string, null given, called in /opt/psa/admin/plib/modules/wp-toolkit/library/Servers/DomainInstanceScheduler/PleskDomainInstanceScheduler.php on line 211

How do i solve this?
 
As I can see, this error could occur during cloning of cron task associated with a cloned website. Did you disable native wp-cron for them, right?

We need to check, but I can suggest that during migration the description of scheduled task was not migrated on the target, so during cloning toolkit failed to duplicate this task.

If my suggestion is correct, could you please open the cron task settings and set a description (any text on your choice)? And after that try to clone website once again.
 
Could you please clarify, is this cron job was related to your website? I am going to submit a bug so any details would be very appreciated. :)
 
I confirm an issue EXTWPTOOLK-5033. It will be fixed in the next update of WordPress Toolkit extension. Thank you for the feedback!
 
  • Like
Reactions: pge
Back
Top