wordpress default install dir public_html
Hi,
Recently (cpanel version 11.36.1) the option to have wordpress installed in the root dir (public_html) of an account is no longer possible.
You can now only install it into a subdir.
I understand it was removed because one could overwrite an existing site, if there were any, in the public_html.
Maybe this happened to a lot of people and that is why this option was removed. But, one would still have the possibility to restore a backup, if one would have overwritten their own website.
We have lots of wordpress sites and it would be great if this was possible again. To specify the root dir with the first installation of wordpress. In stead of installing it into a subdir and then moving the files into the root.
Paul
I like this idea 
cPanel, WebHost Manager and WHM are registered trademarks of cPanel, L.L.C. for providing its computer software that facilitates the management and configuration of Internet web servers.
The WordPress cPAddon has been updated to 3.5.2. This should also restore the document root installation functionality.
The WordPress cPAddon has been updated to 3.5.2. This should also restore the document root installation functionality.
Someone decided to force Site Software -> WordPress installer to only allow installation in a subdirectory.
This is so 1990's thinking. I have to imagine this is a hold over from years past when WordPress was a lesser known CMS.
Now that the majority of new websites being created today "are
WordPress" please remove this subdirectory requirement as soon as
possible.
Not a single commercial installer forces this requirement (hint?).
The option to install within public_html needs to be allowed.
I'm having to manually "fix" this rather serious annoyance for clients
more often than I would prefer too, and truthfully, this is more of a
support ticket filler than a necessary feature IMHO.
WordPress subdirectory installation requirement is only a good "feature"
if my primary goal is to annoy clients (which it is not).
Thanks,
Jim
Someone decided to force Site Software -> WordPress installer to only allow installation in a subdirectory.
This is so 1990's thinking. I have to imagine this is a hold over from years past when WordPress was a lesser known CMS.
Now that the majority of new websites being created today "are
WordPress" please remove this subdirectory requirement as soon as
possible.
Not a single commercial installer forces this requirement (hint?).
The option to install within public_html needs to be allowed.
I'm having to manually "fix" this rather serious annoyance for clients
more often than I would prefer too, and truthfully, this is more of a
support ticket filler than a necessary feature IMHO.
WordPress subdirectory installation requirement is only a good "feature"
if my primary goal is to annoy clients (which it is not).
Thanks,
Jim
This is a joke! This used to work and now it doesnt and I am very angry because as far as I am concerned cPanel is very expensive and whoever made this dumb decision needs to be counselled! Wrong wrong wrong! I am taken this cause to Social Media to get this changed as it is a joke!
This is a joke! This used to work and now it doesnt and I am very angry because as far as I am concerned cPanel is very expensive and whoever made this dumb decision needs to be counselled! Wrong wrong wrong! I am taken this cause to Social Media to get this changed as it is a joke!
I absolutely agree that this "feature" needs to be removed.
Fyi regarding cPanel's reason for this "feature" as documented on How to use Wordpress with cPanel
Warning: If you use cPAddon to install WordPress, you must specify a subdirectory on the Install screen. If you wish to install WordPress into your document root, install WordPress manually without the assistance of cPAddon. A WordPress installation in the document root may cause conflicts with any other non-WordPress content in that account due to how the .htaccess file behaves. Also, WordPress installed in the document root prevents multiple installations of WordPress in an account because of these .htaccess conflicts.
I manage a cPanel instance for a University and having to manually install WordPress for all the clients who can't use the cli is a nightmare. We have never experienced any of the issues mentioned and even if we did, I would much rather manage the occasional htaccess issue than having to manually install multiple WordPress instances.
I absolutely agree that this "feature" needs to be removed.
Fyi regarding cPanel's reason for this "feature" as documented on How to use Wordpress with cPanel
Warning: If you use cPAddon to install WordPress, you must specify a subdirectory on the Install screen. If you wish to install WordPress into your document root, install WordPress manually without the assistance of cPAddon. A WordPress installation in the document root may cause conflicts with any other non-WordPress content in that account due to how the .htaccess file behaves. Also, WordPress installed in the document root prevents multiple installations of WordPress in an account because of these .htaccess conflicts.
I manage a cPanel instance for a University and having to manually install WordPress for all the clients who can't use the cli is a nightmare. We have never experienced any of the issues mentioned and even if we did, I would much rather manage the occasional htaccess issue than having to manually install multiple WordPress instances.
Nearly every one of my clients wants to use Wordpress AS THEIR WEBSITE, not just a subdirectory of their site. Why would you prevent it from being installed in the root of the site? If you're really worried about it breaking other things, just put up a warning saying "This may break the rest of your site, do you want to continue?" Since almost everyone will not even have a "rest of your site", they will continue and use Wordpress the way it was intended.
Nearly every one of my clients wants to use Wordpress AS THEIR WEBSITE, not just a subdirectory of their site. Why would you prevent it from being installed in the root of the site? If you're really worried about it breaking other things, just put up a warning saying "This may break the rest of your site, do you want to continue?" Since almost everyone will not even have a "rest of your site", they will continue and use Wordpress the way it was intended.
What's the word cPanel.
Seriously, hopefully no one there is taking this as a joke.
This is business ending stuff here.
Yes, I can go pay for Fantastico or go with Simplescripts to get around this "restriction."
All you cpanel folks are doing is forcing my clients away to other hosts whose control panels have no restrictions like this "out of the box."
What's the word cPanel.
Seriously, hopefully no one there is taking this as a joke.
This is business ending stuff here.
Yes, I can go pay for Fantastico or go with Simplescripts to get around this "restriction."
All you cpanel folks are doing is forcing my clients away to other hosts whose control panels have no restrictions like this "out of the box."
Something is happening...
The status of the feature request: you were watching has changed to In Progress.
Something is happening...
The status of the feature request: you were watching has changed to In Progress.
When we issue the update for Wordpress 3.5.2 you will again be able to install directly to a site's document root.
When we issue the update for Wordpress 3.5.2 you will again be able to install directly to a site's document root.
The WordPress cPAddon has been updated to 3.5.2. This should also restore the document root installation functionality.
The WordPress cPAddon has been updated to 3.5.2. This should also restore the document root installation functionality.
super!!
thank you very much!
highly appreciated..!
super!!
thank you very much!
highly appreciated..!
Hi,
Thank you for sharing this information.
Keep it up!
Please check out my website <a href="http://filesee.net/" target="_blank">buy premium WordPress theme </a>
with kind regards,
memoona
Hi,
Thank you for sharing this information.
Keep it up!
Please check out my website <a href="http://filesee.net/" target="_blank">buy premium WordPress theme </a>
with kind regards,
memoona
Replies have been locked on this page!