I am using CiviCRM on Wordpress on Ubuntu where the Wordpress comes from a deb package, not from the original source. The only real difference that I know of is that Debian/Ubuntu split the Wordpress code into /usr/share/wordpress for the static PHP files, and /var/lib/wordpress for the content files and uploads.

Anyway, probably because of some weird interaction between the Ubuntu package and CiviCRM, I end up with a whole bunch of resources trying to load from a path that starts with https://mydomain.com/var/lib/wordpress and which creates a 404 error in the webserver log when it tries to access /var/lib/wordpress/var/lib/wordpress on my disk. What has obviously happened is that part of the filesystem path has accidentally been embedded into the URL for the resource.

Problem is, I'm not sure where that setting comes from or how to change it. Can anyone verify this, or is it really just me? Should I report this as a bug against the Ubuntu package maybe? Among the resources that have the wrong path are:

/uploads/civicrm/persist/contribute/files/delete-this-WjYpCHVDVl /uploads/civicrm/persist/contribute/index.php /plugins/civicrm/civicrm/js/wysiwyg/crm.ckeditor.js

  • Are you able to add your last comment and as Answer and then accept it so this can be closed off?
    – petednz - fuzion
    Commented Nov 16, 2018 at 19:27

2 Answers 2


I don't feel that this is a good solution to the problem, but as requested, I'm reposting this as an answer. I "solved" this error by creating a symlink using:

$ mkdir -p /var/lib/wordpress/var/lib

$ ln -s /var/lib/wordpress /var/lib/wordpress/var/lib/wordpress


This is a shortcoming in CiviCRM, unfortunately. The problem is that CiviCRM tries to guess where WordPress and its resources are via directory traversal. This works (by and large) for "standard" WordPress installs but not for those where wp-content has been moved or where the CiviCRM plugin directory has been symlinked.

Until this is remedied, your best bet is not to use the deb package and install WordPress manually in the DirectoryRoot location instead.

  • OK, thanks. The workaround that I have used for now is just to symlink /var/lib/wordpress/var/lib/wordpress to /var/lib/wordpress, and I should be able to do the same thing a bit more elegantly with some nginx configuration, once I figure it out. Commented Sep 18, 2018 at 17:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.