Installing WordPress in a sub-domain when it is also installed in the root

[gkgcpanel]

The described symptoms appear to be for a different issue. Please submit a support request so the precise symptoms and specific circumstances may be thoroughly investigated. If needed, the link in my forums signature may be used to initiate a ticket submission; when available, please PM me referencing your post and the new ticket ID number so I may follow-up internally.

No, the problem here was something different, I deleted the account and re-created it and now installing WordPress on Addon Domains work fine (in the WordPress directory). Not in the root of the Addon domain.

I received the same error as stated above:

"There is already public_html install of this addon."


This issue has caused us a customer. The customer insisted that this is a bug (which he is right) and wanted a refund of his hosting fees.

This needs to be corrected.

Running the latest stable version:

11.24.5-STABLE_38506

with WordPress 2.8.6

Thanks,
Peter

[OcalaDesigns]

I'm having this same problem on my CentOS VPS server, hosted through DotBlock.com. I can install a single copy of WordPress into the root of a site or in a sub-domain, once there is an install, I can't install another copy into a subdomain. After using CPanel Addons to install WordPress, I get the error "There is already public_html install of this addon.". Is there a setting in WHM that would correct this and allow multiple installs? I'm installing WordPress 3.1.2, which shouldn't matter.

I even tried creating a new hosting account in WHM, installed WordPress into a subdomain first, then tried to install it again into the root domain public_html folder and I get the same error. I do have a cPanel::Blogs::WordPress.0.yaml file in the folder /home/myfolder/.cpaddons, but I don't know what it's for ... Obviously something to do with the cpanel addons ....

[Ballarino]

Same problem I'm having.. Trying to use the WP addon script to install directly into the "addon" domain and get error "There is already public_html install of this addon" which shouldn't matter since the NEW addon domain is pointed to a new subfolder in public_html and in www. - does anyone have a fix for this?

BTW, cpanel folks, I'm trialing your software and if I can't find a fix for this, I'm going elsewhere... thank you.

[cPanelMichael]

Hello

The behavior you are reporting is by design. Multiple docroot installations would result in various configuration conflicts. You are only permitted to have one docroot install per account, however you can have an additional installation in a subdirectory. Here are the steps you can take to configure this:

1) Install WordPress to a subdirectory of an existing domain name.

2) Create a subdomain (or Addon domain) that uses that subdirectory as it's DocumentRoot.

There has been discussion of revamping the cPAddon system to allow for multiple docroot installs, however there are currently no plans to do so in the immediate future.

Thank you.

[ruzbehraja]

Same problem I'm having.. Trying to use the WP addon script to install directly into the "addon" domain and get error "There is already public_html install of this addon" which shouldn't matter since the NEW addon domain is pointed to a new subfolder in public_html and in www. - does anyone have a fix for this?

BTW, cpanel folks, I'm trialing your software and if I can't find a fix for this, I'm going elsewhere... thank you.

Rename the folder which contains the addon domain (you can remove the ".")

Eg: rename the folder from "domain.com" to "domain" or "domaincom"