Current Issues

phpSmug Bugs

IDStatusDescriptionReported
6Resolved
(2.2)
login_*() method calls are incorrectly handled when used instead of the phpSmug specific single unified login() method.Chris Abbey
3 Jan '10
5Resolved
(2.1)
Uploads have started to fail because phpSmug uploads to api.smugmug.com and not upload.smugmug.com.Brian Steele
23 Sep '09
4Resolved
(2.1)
Caching re-stores data to the cache it's just pulled it from thus resulting in an updated timestamp on the cache (entry or file) and could potentially lead to stale cache data. This affects both DB and FS caching.Aaron
28 Aug '09
3Resolved (2.0.2)clearCache() is over zealous and deletes all files in specified cache directory, not just it's own.

Notes:
Until this is resolved, ensure you use a dedicated directory for caching.
Me
20 Nov '08
2Partially Fixed (2.0.2)phpSmug is not PHP 5 E_STRICT compliant

Notes:
This status is only going to change when the 2 PEAR modules phpSmug rely on become E_STRICT compliant, or I can find a good alternative without re-writing the code myself.
Me
9 Nov '08
1Resolved (2.0.1)Error code not being passed to Exception() on line 350 of phpSmug.php (rev 2.0)MVA
7 Nov '08

SmugMug API Bugs

NOTE: 21 July 2010: I'm no longer tracking bugs in the API as it's much easier for the guys at SmugMug to develop a test suite around their code than it is for me. I will however continue to report issues to SmugMug if I discover any.



  

phpSmug Users

If you're using phpSmug and wish to let the world know, drop me a line and I'll add a link and short description here