ATTN: phpSmug Users - Update NOW!!

lildude

Hi all

Just a quick note to say if you are currently using phpSmug 2.0.2 or earlier, you will need to update to the latest version (2.1).

The primary reason for this is due to problems with uploads going to api.smugmug.com (like phpSmug used to do) SmugMug are forcing people to upload to upload.smugmug.com (I really can't remember why I didn't upload here in the first place).

phpSmug 2.1 now uploads to the correct location.

Cheers,
Colin

PS. If you are using phpSmug for a public application, drop me a line (either PM or via the contact form at phpsmug.com/about) and I'll add a link to your app site and a short description to the sidebar on phpsmug.com.

SamirD

Thank you for the update. So if we're not using anything intensive needing caching or uploading, would there be any need to update? My custom application is just pulling a list of albums every 4 hours.

lildude

SamirD wrote:

Thank you for the update. So if we're not using anything intensive needing caching or uploading, would there be any need to update? My custom application is just pulling a list of albums every 4 hours.

If you're using the default caching timeout of 3600 seconds (1 hour), then you're not likely to be hitting the caching issue as you'll only be querying your cache every 4 hours. This check will find it's stale and re-request the data from SmugMug.

The caching issue only comes to light it you regularly querying SmugMug within the cache interval.

What happens then is phpSmug initially checks the cache to find it's empty, pulls the data from SmugMug, caches it and then continues. Subsequent calls to the cache within the cache interval would check the cache, find it's valid, use the data but then re-cache the cached data. If changes were made to your galleries on SmugMug within this time, you could end up in a situation of never actually seeing them.

I've resolved this by moving the caching line a bit further up in the code so that it only caches data received from SmugMug rather than re-caching cached data.

SamirD

lildude wrote:

If you're using the default caching timeout of 3600 seconds (1 hour), then you're not likely to be hitting the caching issue as you'll only be querying your cache every 4 hours. This check will find it's stale and re-request the data from SmugMug.

The caching issue only comes to light it you regularly querying SmugMug within the cache interval.

What happens then is phpSmug initially checks the cache to find it's empty, pulls the data from SmugMug, caches it and then continues. Subsequent calls to the cache within the cache interval would check the cache, find it's valid, use the data but then re-cache the cached data. If changes were made to your galleries on SmugMug within this time, you could end up in a situation of never actually seeing them.

I've resolved this by moving the caching line a bit further up in the code so that it only caches data received from SmugMug rather than re-caching cached data.

Thank for Colin for the reply and explanation! I'm just going to stick with the 2.0.2 version for now.

BHsu

smugmug.com is down and phpSmug is crashing my application
hey all, i was wondering if you're aware of this situation, as i dont think the smugmug servers are down very often.

i have a page that uses phpsmug to display some album images.

right now, the servers are down for maintenance and it appears that the php code is crashing at the $f->login line because there is no server response. does anybody know if there is a workaround for this?

SamirD

BHsu wrote:

hey all, i was wondering if you're aware of this situation, as i dont think the smugmug servers are down very often.

i have a page that uses phpsmug to display some album images.

right now, the servers are down for maintenance and it appears that the php code is crashing at the $f->login line because there is no server response. does anybody know if there is a workaround for this?

There is a result which is returned when it is in read-only mode or has trouble connecting. You just have to code your php to check for that result before executing the core of your program.