Bugfix update to v1.1.1 - All known bugs fixed!

onethumb · November 17, 2006

The API blog has all the details.

Discuss what works & doesn't work here, please.

Don

wellman · November 17, 2006

Great work! Now get some well-deserved rest. :cavig

javier.rinaldi · November 17, 2006

awesome, how about the smugmug.logout returning "invalid API key" bug?

devbobo · November 17, 2006

javier.rinaldi wrote:

awesome, how about the smugmug.logout returning "invalid API key" bug?

hey Javier,

yeah unfortnately, it's still returning that, but it's no longer returning an empty sessionID on a subsequent login.

javier.rinaldi · November 17, 2006

devbobo wrote:

hey Javier,

yeah unfortnately, it's still returning that, but it's no longer returning an empty sessionID on a subsequent login.

no prob, i'll keep using the call to logout.mg, thanks for the hard work

Stardog · November 17, 2006

Umm, Has the serialized php been removed? I don't get any response from it at all.

devbobo · November 17, 2006

Stardog wrote:

Umm, Has the serialized php been removed? I don't get any response from it at all.

Stardog,

No it hasn't been removed, for some reason json and php are returning blank responses. I am chasing it up with Don.

Cheers,

David

groovybeat · November 17, 2006

Multi-PART POST API no longer working?
Hi,

I've been using the multi-part POST API:

http://upload.SmugMug.com/photos/xmladd.mg

But yesterday this stopped working (presumably when the update was done). I'm not receiving any error; just an empty response, and the uploaded photo does not get posted to my album.

Has something changed with this API? Are there headers or post arguments that used to be optional but are now required? I'm sending AlbumID, ByteCount, and have tried both ResposeType optoins.

I am NOT sending MD5Sum, nor Caption at this time. Perhaps one of these is now required?

I'd prefer to use this Mutli-PART POST API since the mobile client I'm working with doesn't do PUT and I'd rather not base64 encode either. I'd also prefer to stay away from adding custom headers (i.e. doing a RAW POST) if possible.

Thanks for your help,
Groovybeat

devbobo · November 17, 2006

Hey groovybeat,

Not sure why this stopped working

But can i suggest that u use a different upload method.

Please try the RAW HTTP POST method, on this page

It should be a very straight forward change.

Let me know how u get on.

Cheers,

David

onethumb · November 18, 2006

Stardog wrote:

Umm, Has the serialized php been removed? I don't get any response from it at all.

Technically, v1.1.1 never had serlialized PHP (or JSON).

The next version, due out early next week, will have very robust support for both. I'm just waiting for devbobo to confirm it works well.

Don

onethumb · November 18, 2006

groovybeat wrote:

Hi,

I've been using the multi-part POST API:

http://upload.SmugMug.com/photos/xmladd.mg

But yesterday this stopped working (presumably when the update was done). I'm not receiving any error; just an empty response, and the uploaded photo does not get posted to my album.

Has something changed with this API? Are there headers or post arguments that used to be optional but are now required? I'm sending AlbumID, ByteCount, and have tried both ResposeType optoins.

I am NOT sending MD5Sum, nor Caption at this time. Perhaps one of these is now required?

I'd prefer to use this Mutli-PART POST API since the mobile client I'm working with doesn't do PUT and I'd rather not base64 encode either. I'd also prefer to stay away from adding custom headers (i.e. doing a RAW POST) if possible.

Thanks for your help,
Groovybeat

Sorry, we had a bug. It was fixed yesterday. Give it another shot!

Don

den123 · November 18, 2006

getStats?
Did anybody test for smugmug.images.getStat? I continue to receive

err code="4" msg="invalid user"<err code="4" msg="invalid user">

maybe I do something wrong

Everything (in my test) is working fine, except getStat:cry</err>

devbobo · November 18, 2006

onethumb wrote:

Technically, v1.1.1 never had serlialized PHP (or JSON).

The next version, due out early next week, will have very robust support for both. I'm just waiting for devbobo to confirm it works well.

Don

umm....didn't u get my email ?

Stardog · November 18, 2006

onethumb wrote:

Technically, v1.1.1 never had serlialized PHP (or JSON).

The next version, due out early next week, will have very robust support for both. I'm just waiting for devbobo to confirm it works well.

Don

Nice! I've fully converted the smugmug module for drupal that tazzytazzy wrote to use serialized PHP. It was working fine (except for the few bugs I posted) until the other day. If you need any help testing, just let me know.

I look forward to trying out the new version!

Brian

Bugfix update to v1.1.1 - All known bugs fixed!

Comments