The reason WP2Cloud loads wp-load.php is to handle /wp-content/plugins/wp2cloud-wordpress-to-cloud/wp2cloud.php?weblob_id=42/pic.jpg URLs. wp2cloud.php is called directly in that case and needs to load wp-load.php to bootstrap WordPress and get all context including ABSPATH.
So unfortunately, it’s a chicken-and-egg problem, and WP2Cloud needs to know how to include wp-load.php before it can use ABSPATH.
So do you have a proposed solution when the wp-content directory is not in the the wordpress directory? Is hardcoding the only option?
Well, WP2Cloud has to know how to load wp-load.php before it can load wp-load.php, so the path has to be configured somewhere. What we can do is to provide a way configure the path without modifying the plugin code. If you send an email to support (at) oblaksoft (dot) com, we’ll send you an experimental version, so you could see if this works for you.
I sent you an email. Although I load my dependencies through Composer and wpackgist. If there’s a way to specify a dev branch on the SVN, or provide a Composer compatible wordpress plugin installer, it would be great.
The new plugin version 1.3.11 (just released) supports optional wp2cloud-config.php that can be added to the plugin directory to configure ABSPATH.
The wp2cloud-config.php should contain code like this:
<?php define('ABSPATH', '/your/custom/abspath');
This way the ABSPATH can be customized without changing the plugin’s code.
