phpSmug - PHP Wrapper for the SmugMug API

It's been a while since I last released an update to phpSmug, but rest assured I've not forgotten phpSmug and have actually been working on some of the behind-the-scenes stuff. Most of the work I've been doing has been on building a test suite for my own purposes so I can thoroughly test phpSmug with ease.

This is list of the changes you as a developer/user may notice (taken from the README.txt):

Time for a relatively major update that primarily fixes uploading and caching.

SmugMug have enforced the use of upload.smugmug.com for all uploads. All earlier releases of phpSmug uploaded to api.smugmug.com, and whilst this worked, apparently SmugMug were having problems with people using this endpoint for uploads, so they've now forced people to use the correct url :-) (Ticket #5).

Just a small minor update to phpSmug that resolves the over zealous clearCache() (Ticket #3) and some code tidying to get phpSmug a bit closer to being E_STRICT "compliant" (Ticket #2). Sadly we're still tied by PEAR for full compliance, bit for the moment all the code I have control over works with E_STRICT.

As usual, it's available for download from the download page.

I've just found another bug (#3 logged) in phpSmug that you should be aware of. The clearCache() function is over zealous when using the filesystem as the cache location. The function deletes ALL files in the specified directory, not just it's own.

This isn't a problem if you've specified a unique directory for caching, but if you're using a shared caching directory, like you may do if including phpSmug in an application, then all the cache files are removed.

I'm in the process of creating a project using my phpSmug class and I've discovered I'm not quite 100% PHP5 E_STRICT compliant in two locations in the way I instantiate new PEAR objects:

105         $this->req = new HTTP_Request();
[...]
472         $upload_req = new HTTP_Request();