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

Wordpress on 1&1 - is it this hard?

Ed_itor

New Pleskian
I'm a new 1&1 dedicated server customer running Plesk10.
I want to put some WordPress sites up.
I tried installing WordPress from the Plesk control panel but it doesn't find it out of the box.
I discovered that it installed WordPress BELOW the HTTPDOCS directory.
1&1 gives you access only to that HTTPDOCS directory.
I ended up having to do the following to get it to work with the control panel tools provided.
* Create a customer/subscriber (set parameters)
* Go to subscriber control panel
* Go to websites and domains
* Create a database
* Add a database user

* FTP to the subscriber directory
* Delete EVERYTHING from httpdocs
* Add a Wordpress directory (just the top level)
* In Websites and Domains (Advanced operations) choose website scripting
* Change search path to "httpdocs/wordpress" (directory must be empty and \wordpress must be present to do this)
* Go back to FTP and now DELETE the single top level Wordpress directory
* Go back to the customer control panel and install Wordpress
* During install delete "Wordpress" from the path "httpdocs/wordpress" so that it installs at the root of httpdocs

Should it be this hard?

Ed
 
Why you can't install WordPress in Plesk?
Did you try it?
 

Attachments

  • screen 2012-02-17 в 10.09.23.PNG
    screen 2012-02-17 в 10.09.23.PNG
    89.3 KB · Views: 8
I don't have that problem - WordPress installs into either root or a subdirectory (/wordpress by default) without a hitch. It's a true one-click-installer.

Make sure you have the correct webspace selected at the top.
 
Back
Top