Every time I update Salesforce via drush it moves the old module directory to a backup area and deploys a fresh new version. The side effect of this is that the PHP Toolkit 'soapclient' library goes missing.
A number of others modules are now favouring installing 3rd party libraries under /sites/all/libraries/ to keep it out of the module directory all together.
Whats the chances of moving to this style of file organisation?
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | salesforce-libraries.patch | 1.01 KB | aaronbauman |
Comments
Comment #1
13rac1 commented+1
Implement Libraries API.
Added tag "Libraries": http://drupal.org/project/issues/search?issue_tags=Libraries
Comment #2
kmonty+1
Comment #3
aaronbaumanThe WSDL should probably be moved out of the distributed code too.
I think this should be as simple as
Does that look right?
Swapping in a conditionally defined constant will eliminate the need for a hard dependency on Libraries API
Comment #4
aaronbaumanComment #5
EvanDonovan commentedIsn't the WSDL already supposed to be outside of the website's DocumentRoot, though? (i.e., not in sites/all/libraries)
Comment #6
EvanDonovan commentedI think this is "needs work", since the WSDL is already outside the DocumentRoot, but Libraries API would be good for the soapclient.
Comment #7
aaronbaumanThis is in latest 2.x-dev
Evan, you're right - only the soap client location needed to change.
Also updated README instructions
Comment #8
EvanDonovan commentedJust tested this. Great!