Facebook
Twitter-
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.
Old website is gone after installing WordPress on Plesk
- Thread starter evelynv
- Start date
Oh, I think I might have overwritten the old one. I can still see the old files inside /httpdocs. Can I retrieve it?
Also, I was setting up a coming soon page using Elementor free but it does not appear as designed. I actually have a lot of issues with Plesk being a first-time user and I can't seem to resolve them following available online resources.
The files that have been overwritten cannot be restored unless you restore them from a backup.
The issues you are describing seem to be related to missing best practice procedures. For example: Before you start something new, clean up the old stuff (e.g. remove the previous content). Before you apply a change to an existing configuration or website, have a backup. Etc.
The issues you are describing seem to be related to missing best practice procedures. For example: Before you start something new, clean up the old stuff (e.g. remove the previous content). Before you apply a change to an existing configuration or website, have a backup. Etc.
Similar threads
