- Online setup tool for register settings
- Arduino baud rate 8 times too high?
- How do I connect an accelerometer (GY-521) to a SparkFun Thing Dev (ESP8266)?
- What technology is best to simulate a static 2d/3d lattice structure?
- Designing stripboards (prototype boards)
- In an articulated hub rotor craft, what could cause the blade to flap negatively?
- What does it mean to fly a procedure turn?
- Why is a plane escorted while in technical difficulties?
- Fan dipole radiation pattern
- Streamlining Aquarium for Frequent Travel
- How much purring is too much purring?
- Headphones stopped working, need better alternative
- Is there a flight simulator or 3d chart showing the gravity well of the Earth and Moon?
- Is it possible to navigate space travel with no computer?
- UV coordinates are locked from -10 to 10?
- How to make blue hot metal
- Dope Sheet copy/paste buffer keyframes problem
- How to make a realistic snow material in Cycles?
- Bezier curve between faces of different meshes
- Rendering with background, but saving with alpha?
Stock CiviCRM on Ubuntu package of Wordpress leads to /var/lib/wordpress/var/lib/wordpress/ paths
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 resou
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.2018-10-17 12:53:12