• 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!
  • 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.

Forwarded to devs WP Cloning does not clone index.php on newly created targets when the skeleton of the target has an index.php

Bitpalast

Plesk addicted!
Plesk Guru
Username: Peter Debik

TITLE

WP Cloning does not clone index.php on newly created targets when the skeleton of the target has an index.php

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

CentOS 7.9, Obsidian 18.0.38 latest MU, but also on older versions

PROBLEM DESCRIPTION

We have a skeleton in /var/www/vhosts/.skel/0/httpdocs with an index.php file that displays a "Coming soon" page for newly created customers, subscriptions, domains. The index.php is owned by the subscription user and the group psacln.

When a customer has a Wordpress website in the same subscription and clones that Wordpress website with the "clone" button into a new subdomain or domain, all files are being cloned but index.php of the source. It seems that the cloning function does not clone index.php when an index.php in the target directory exists.

STEPS TO REPRODUCE

1) Place an index.php into /var/www/vhosts/.skel/0/httpdocs.
2) Create a WP website in any subscription.
3) Clone that WP website into a NEW domain or subdomain that did not previously exist.

ACTUAL RESULT

All content is cloned but the index.php file of the WP installation. Instead, the index.php file from the skeleton remains in the newly created domain/subdomain.

EXPECTED RESULT

All files are cloned.

ANY ADDITIONAL INFORMATION



YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you, Peter.
The issue was reproduced in the test environment. Bug confirmed: EXTWPTOOLK-8244
 
Back
Top