Details
-
Type:
Bug
-
Status: Done/Fixed
-
Priority:
Minor
-
Resolution: Cannot Reproduce
-
Affects Version/s: 4.7.1
-
Fix Version/s: None
-
Component/s: WordPress Integration
-
Labels:None
-
Documentation Required?:User and Admin Doc
-
Funding Source:Needs Funding
Description
Hi,
it seems that installing CivicCRM as a wordpress plugin, under a specific condition causes an installation that is unusable. The resulting outcome is similar to the issue reported on ticket CRM-17894.
I did several tests on several machines with lastest releases of wordpress and CivicCRM, using Apache/2.4.7 and PHP 5.5.21 on Ubuntu 14.04 LTS and CentOS 6.7 and each test got me the same result.
The condition I'm speaking is where you install wordpress.
If you install it in the document root as a main domain (eg. "/home/account/wwww"), the CivicCRM plugin install is sccessful.
If you install wordpress in a subdomain, (eg. "/home/account/wwww/subdom" and the document root is correcty the same)" the CivicCRM tries to load javascript and css files prefixing also the subdirectory before of "/wp-content" path, thus failing to load the scripts and rendering the administration panel unusable.
Seems to be an error in the class that computes the "civic.root" parameter and seems related to the level of subdirectory nesting.
See you
