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

Resolved Pwd Protected Dir Pop-Up from Copy Files (Wptoolkit)

Aethem

New Pleskian
Server operating system version
Debian 12
Plesk version and microupdate number
18.0.54
Hello Supporter,

I‘m new to plesk and have some issues by using the copy files function via the wptoolkit.

Situation:

I have two wordpress domains

domain.com (no pwd dir)
staging.domain.com (password protected directory „/„)

After I copied the wordpress from staging.domain.com to domain.com.

I received the staging.domain.com pop-up if I open domain.com.

It‘s possible to click abort and continue on th website.com

Is wptoolkit\copyfiles creating a htaccess in the background and it‘s copied as well?

Many thanks for your reply
 
After you copied the files, did you update the database that Wordpress uses, and did you also update the "home" and "siteurl" URLs in the options table of that database to reflect your new URL of the new website?
 
Hello Peter,

no i didn't.

Now it's solved. Thank you so much.

I just watched on the webspace size of both domains.

Do you know, why the source "subdomain" is quite less then the top-level domain?

staging.domain.com
Subdomain-Website 9.3 MB
domain.com
Webseite 757.3 MB
 
The issue regarding a wrong disk space usage segment display is related to the way this is calculated. As far as I remember the reason why this was never fixed so far is that an exact calculation would use too much cpu resources during nightly maintenance.

As a workaround you can run any "du" command on the Linux shell to determine the real disk space usage of the subdomain's directory, like du -csh ./<subdomain directory>.
 
Back
Top