any plans to update smugpy for the v2.0 SmugMug API?

[gingerlime]

Hi @chrishoffman. Thanks again for smugpy. I'm using it for smugline - a command line tool for SmugMug and it's really useful.

I know that SmugMug released their v2.0 API a while ago, and am wondering if you have any plans to update smugpy to support the latest version of their API?

Cheers
Yoav

[chrishoffman]

The 2.0 API is still in beta but I will take a look

[gingerlime]

Thanks @chrishoffman. I imagine you also received a note from SmugMug about the beta launch around December last year? I was expecting things to move forward since then, but in a way it's good to know that it's not moving too fast.

In any case, I asked you just in case you already made some progress, or to find out if you have any plans in this direction.

[chuckhays]

I'm planning on working on 2.0 support for this library, happy to coordinate @chrishoffman if you are interested.

[gingerlime]

Got this email just now:

Dear SmugMug API Developer,

We want to update you on a couple of important changes that will be happening at SmugMug and what they will mean for you and your apps, plug-ins, and other SmugMug integrations.

As you may have heard, we are retiring our Old SmugMug platform on October 15. Almost all of our customers are already using New SmugMug and many of your apps already support them. If you find any problems in how your code interacts with New SmugMug, you should look at changing your app to use API v2, which was built specifically to support the New SmugMug platform. If you have any issues and/or want help getting started on the new API, please feel free to reach out to us.

Also, starting on October 15, all HTTP requests to SmugMug, including all versions of the SmugMug API, must be secured with SSL/TLS. In other words, you must make all requests with https URLs. If your application is not already using https URLs, you need to update it by October 15 in order to maintain SmugMug compatibility. We made these changes to foster the most secure environment for our customers and partners.

We will redirect insecure requests to secure URLs; however, if you are using OAuth, this may not help your application, because if your application follows redirects without recalculating the OAuth signature, the signature will be invalid when you make the secure request.

If you have any questions, please feel free to contact [email protected] as always. Thanks for your support in making our shared customers' experiences as great and secure as possible.

Sincerely,

The SmugMug API Team

If I'm reading this correctly(?), even though the v2 API is still marked as Beta, they're retiring the old API (does it include v1.3?).

[chrishoffman]

I got the same e-mail. It doesn't look like they are retiring the old APIs but forcing connections over HTTPS. This will probably not require any changes to the library, although I will look, since it already support https. I created a new ticket to track this issue #14

[tedder]

FWIW, I've been starting an API class called "mug", so if smugpy isn't going to v2 I can clean it up and share as a starting point.

[gingerlime]

Thanks for clarifying @chrishoffman. It does sound rather vague, particularly for an email targeted at developers, I have to say. Not very clear to me what's the old platform and what's the new one and how it all fits with their API versioning etc.

[chrishoffman]

I think they are just talking about their website designer platform which was opt-in for a very long time. They added features like unlimited nesting, among other things, that did not translate well to their old API (well their current API).

[adhawkins]

Has anyone made any progress on python support for the v2 API? I'm about to start on an application myself, and don't want to reinvent the wheel if at all possible.

Thanks

Andy

[adhawkins]

I've made a start on a v2 API here:

https://github.com/adhawkins/smugmugv2py

Interested in any comments or suggestions, it's still in the early stages at the moment, with little documentation.

I have written a sync program using it though, source is here:

https://github.com/adhawkins/pysmugmugsync

Would appreciate any comments or suggestions in those repos.

Andy

[gingerlime]

@chrishoffman @adhawkins What's the status of this? Any chance getting v2 API changes merged into smugpy?

[adhawkins]

Hi,

My API is usable, at the GitHub link above. No plans to merge really.

Andy

[gingerlime]

@adhawkins Any particular reason to create a separate project for accessing the SmugMug API ? Rather than contribute to this one? (Having two libraries, for v1.3 and one for v2.0 could create fragmentation and confusion)... Or did I misunderstand your intentions?

[adhawkins]

Mainly because there was no progress on this issue for a long period before I started work on mine. There seems to have been little activity on this project as a whole for a number of years now...

Andy

[gingerlime]

That's a valid comment I suppose. @chrishoffman is this project dead?

[e40]

@gingerlime Re: is this project dead? I guess it is now. I'm looking at the project by @adhawkins but I don't see any documentation and I'm not a Python programmer, so I don't know if it's a possible replacement for me.

[adhawkins]

Your comment is valid @e40. I keep meaning to packaging up my library such that it's more useful to others.

That said, I do have a working sync client that is using my library. It's here if you're interested.