Answers.Body: <p>I'm sorry to say that you'll have to revert back to the default 'wp-content' folder name in order to use CiviCRM. I can find at least 5 places in CiviCRM core where this is hard-coded.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-28T13:39:16.467Z
Answers.Text: I agree with Christian.   I have been looking at this again recently as this is a blocker to many things.   Christian, thoughts on trying to work together to remove these hard coded references? The problem I see is when CiviCRM runs a process that does not bootstrap wp.   This had been the issue with the PayPal IPN, I am certain a few others are still out there.
Answers.UserDisplayName: Kevin Cristiano
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-28T18:49:18.893Z
Answers.Text: Whilst the `wpLoadPhp` setting is a good start (and was sufficient to get Paypal IPN working) Civi-for-WP needs to be more sensitive to its context. There are a stack of other possible constants that WordPress uses to define its environment - as Corey's question demonstrates. And that's without raising the issue of Multisite. Kevin, I'd happily work on this with you during Edale, even if you're only present remotely ;-)
Answers.UserDisplayName: Christian Wach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-30T21:19:56.520Z
Answers.Text: Thank you for the reply. I have WP installed in a subdirectory with the content directory in the doc root. My solution has been to create a sym link named `wp-content` inside the WP subdirectory that points to my content directory. This is working for me (so far) without issue.
Answers.UserDisplayName: Corey
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-09-07T08:42:05.383Z
Answers.Text: That's a neat workaround, thanks for sharing.
Answers.UserDisplayName: Christian Wach
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-08-28T13:14:19.153Z
Answers.LastActivityDate: 2015-08-28T13:14:19.153Z
Answers.UserDisplayName: Christian Wach
Body: <p>I have installed CiviCRM successfully for WordPress. However, the Civi dashboard shows many 404 errors. My install directory is <code>content/plugins/civicrm</code> and the dashboard is searching for <code>wp-content/plugins/civicrm</code>. I am not able to find a setting that tells Civi where to look for the content directory. Is this something that I can modify?</p>
  
Tags: <wordpress><settings>
Title: WordPress Content Directory Setting
ThreadText: # WordPress Content Directory Setting
  
  (Asked by: username_0 on 2015-08-25)
  
  I have installed CiviCRM successfully for WordPress. However, the Civi dashboard shows many 404 errors. My install directory is `content/plugins/civicrm` and the dashboard is searching for `wp-content/plugins/civicrm`. I am not able to find a setting that tells Civi where to look for the content directory. Is this something that I can modify?
  
  **Tags:** wordpress, settings
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2015-08-28. Score: 3
  
  I'm sorry to say that you'll have to revert back to the default 'wp-content' folder name in order to use CiviCRM. I can find at least 5 places in CiviCRM core where this is hard-coded.
  
  > **Comments:**
  > **username_2**: I agree with Christian.   I have been looking at this again recently as this is a blocker to many things.   Christian, thoughts on trying to work together to remove these hard coded references? The problem I see is when CiviCRM runs a process that does not bootstrap wp.   This had been the issue with the PayPal IPN, I am certain a few others are still out there.  
  > **username_1**: Whilst the `wpLoadPhp` setting is a good start (and was sufficient to get Paypal IPN working) Civi-for-WP needs to be more sensitive to its context. There are a stack of other possible constants that WordPress uses to define its environment - as username_0's question demonstrates. And that's without raising the issue of Multisite. Kevin, I'd happily work on this with you during Edale, even if you're only present remotely ;-)  
  > **username_0**: Thank you for the reply. I have WP installed in a subdirectory with the content directory in the doc root. My solution has been to create a sym link named `wp-content` inside the WP subdirectory that points to my content directory. This is working for me (so far) without issue.  
  > **username_1**: That's a neat workaround, thanks for sharing.  
  
  ---
  
  