@leftquark said (on June 25):
We have this scheduled with the engineering team once a few folks recharge their batteries and are back from a vacation. I'll be sure to let you know when work begins and when the issue is closed.
By now the batteries should be recharged... Any chance of this being addressed in the coming weeks? I'd love to update some photos.
@leftquark said:
We have this scheduled with the engineering team once a few folks recharge their batteries and are back from a vacation. I'll be sure to let you know when work begins and when the issue is closed.
Aaron, you made this post on June 24, four and a half months ago. Now we've got a new Lightroom version and Jeffrey @Jeffrey Friedl has updated his plugin, but without the help of SmugMug although he repeatedly asked for assistance. Just like before, every file that gets re-published ends up with a file name of "unknown.jpg". In addition, the captions don't seem to be updating - I had a bunch of photos where I just updated the captions and now the photos all have the name "unknown" and the caption has not been updated.
This bug has been around since June 2018. I am way past the end of my patience.
The Engineering team and I have been discussing the bug impacting JFriedl's plugin and we're eager to get it worked on but continue to have some high priority projects that have fallen in front of it. It's at the top of our list once those projects are completed. As much as it's frustrating that a specific API bug is impacting this, we're trying to tackle the underlying root of the problem, which is the API itself, so that developers like Jeff will have a better experience developing for SmugMug in the near future. We expect that work to wrap up towards the end of January and hope to then fix the bug that's impacting the Jeff's plugin.
Also, fixing a bug and helping Jeff are two separate tasks. We're happy to work with Jeff to help him with anything he needs (and in fact have been responding to any of his messages). I don't want y'all to think that we're not here to help him - we have folks dedicated to help anyone who wants to use the SmugMug api.
thanks @leftquark, for finally getting back into communication about this issue. i really hope you can live up to your promise that things will be addressed in early 2020. from what i learned from Jeff Friedl here in the forum i doubt that your team responded to any off his messages - he was kind of lost in the middle of the process of working around the bug. i am happy to hear you will work with any developer having questions.
this is what @Jeffrey Friedl writes in the version history for his smugmug-plugin:
There's a bug on their side that causes republished photos to lose their title, which is a big deal for some users (especially professional photographers using SmugMug to present to clents), so I've been trying to work with SmugMug on a solution or at least a workaround, but getting a response from SmugMug is like pulling teeth. It's now been more than half a year of repeated messages via various methods, but no response. I guess I and Lightroom are small potatos for them, so they just don't care? I don't know. They were great to work with for a decade, until a year ago.
when you are serious about your statement in november:
I don't want y'all to think that we're not here to help him
this is what @Jeffrey Friedl writes in the version history for his smugmug-plugin:
There's a bug on their side that causes republished photos to lose their title, which is a big deal for some users (especially professional photographers using SmugMug to present to clents), so I've been trying to work with SmugMug on a solution or at least a workaround, but getting a response from SmugMug is like pulling teeth. It's now been more than half a year of repeated messages via various methods, but no response. I guess I and Lightroom are small potatos for them, so they just don't care? I don't know. They were great to work with for a decade, until a year ago.
when you are serious about your statement in november:
I don't want y'all to think that we're not here to help him
we would be VERY happy to see things improve!
thanks, etienne
Every since Jeff first posted that his emails had gotten lost in our API developer inbox, we’ve been responding to all of his messages. We haven’t been able to prioritize the bug fix and obviously that’s frustrating him (and you). He’s free to his opinions and write as he sees fit, which I’m sure will continue to be negative until we fix the bug. The one thing I can assure you is that we’re not ignoring him.
We hope to wrap up the underlying API items at the end of January and then will allocate some time to fix the bug.
1) The high priority work that the API team has been working on is taking loner than we anticipated, so we might not be able to tackle this bug until February. It still remains a high priority once the other work is complete.
2) The team member who was managing the API email list passed away suddenly last month and we're working on getting a new person up-to-speed on responding to API emails. Responses might be a bit slower than we'd like as we train a new person (in reality, train a few people so we have backup folks available).
hi @leftquark: thanks for the update- communication is everything ;-). still looking forward to seeing the bug solved so that we can proceed with using the lightroom to smugmug-plugin by @Jeffrey Friedl. my condolences on the passing of your colleague.
Hi Aaron @leftquark - I appreciate the difficulties that you have been having and extend my condolences on the loss of a colleague but would welcome a resolution to this matter in the very near future. We are approaching the two year mark.
It's still on our minds -- the big behind-the-scenes work the team has been doing is starting to wrap up and we're hoping we can get eyes on this one soon. I've asked the API folks for an update.
hey @leftquark this sounds promising to me ... even if it is around some time i am still very interested in a solution to this bug. i believe it, when i see it ,-)
I hate to keep pushing this back, but the team has another couple weeks of wrapping up the big project. They're hoping they can get to this in a month. It's still queued up to be next though!
@leftquark For me it's not longer relevant. I got extremely tired of waiting for answers, added a step to my workflow to change all of the captions to influde location information ( a clunky workaround) and have now taken over two days re-uploading every single gallery multiple times so that all of the files are synced and no longer show "unknown" as file name. Since I have so many pictures posted in fora, deleting all the photos and uploading anew was not really an option. (I'm sure I've already got a lot of broken links in DGRIN but the process of checking this is extremely tedious.) Then of course the result of switching to the SmugMug plugin and reverse-syncing is that my (existing) publish galleries are no longer in Lightroom smart collections but "dumb" collection so now every time I change a parameter that would normally automatically add or subtract a photo from a collection I'll have to remember to do this by hand. If there is any way to make these collections smart again and not lose to links to existing posted photos, I'd love to know.
So Aaron, you won. I am not at all happy about it, but it is so.
Comments
Thank you Aaron.
By now the batteries should be recharged...
Any chance of this being addressed in the coming weeks? I'd love to update some photos.
@leftquark
Bumpity bump bump.... any news?
Aaron, you made this post on June 24, four and a half months ago. Now we've got a new Lightroom version and Jeffrey @Jeffrey Friedl has updated his plugin, but without the help of SmugMug although he repeatedly asked for assistance. Just like before, every file that gets re-published ends up with a file name of "unknown.jpg". In addition, the captions don't seem to be updating - I had a bunch of photos where I just updated the captions and now the photos all have the name "unknown" and the caption has not been updated.
This bug has been around since June 2018. I am way past the end of my patience.
i just want to add my frustration about this not being addressed by the smugmug-team. please, get this issue solved - it is REALLY annoying.
The Engineering team and I have been discussing the bug impacting JFriedl's plugin and we're eager to get it worked on but continue to have some high priority projects that have fallen in front of it. It's at the top of our list once those projects are completed. As much as it's frustrating that a specific API bug is impacting this, we're trying to tackle the underlying root of the problem, which is the API itself, so that developers like Jeff will have a better experience developing for SmugMug in the near future. We expect that work to wrap up towards the end of January and hope to then fix the bug that's impacting the Jeff's plugin.
Also, fixing a bug and helping Jeff are two separate tasks. We're happy to work with Jeff to help him with anything he needs (and in fact have been responding to any of his messages). I don't want y'all to think that we're not here to help him - we have folks dedicated to help anyone who wants to use the SmugMug api.
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
Aaron, thank you for finally responding. I am glad to see that there is some progress being made.
thanks @leftquark, for finally getting back into communication about this issue. i really hope you can live up to your promise that things will be addressed in early 2020. from what i learned from Jeff Friedl here in the forum i doubt that your team responded to any off his messages - he was kind of lost in the middle of the process of working around the bug. i am happy to hear you will work with any developer having questions.
hi @leftquark, any news about this one?
this is what @Jeffrey Friedl writes in the version history for his smugmug-plugin:
when you are serious about your statement in november:
please get in touch with @Jeffrey Friedl to solve the issue. get his contact details here: http://regex.info/blog/jfriedl-links/about#contact
we would be VERY happy to see things improve!
thanks, etienne
Every since Jeff first posted that his emails had gotten lost in our API developer inbox, we’ve been responding to all of his messages. We haven’t been able to prioritize the bug fix and obviously that’s frustrating him (and you). He’s free to his opinions and write as he sees fit, which I’m sure will continue to be negative until we fix the bug. The one thing I can assure you is that we’re not ignoring him.
We hope to wrap up the underlying API items at the end of January and then will allocate some time to fix the bug.
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
Just wanted to give 2 quick updates:
1) The high priority work that the API team has been working on is taking loner than we anticipated, so we might not be able to tackle this bug until February. It still remains a high priority once the other work is complete.
2) The team member who was managing the API email list passed away suddenly last month and we're working on getting a new person up-to-speed on responding to API emails. Responses might be a bit slower than we'd like as we train a new person (in reality, train a few people so we have backup folks available).
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
hi @leftquark: thanks for the update- communication is everything ;-). still looking forward to seeing the bug solved so that we can proceed with using the lightroom to smugmug-plugin by @Jeffrey Friedl. my condolences on the passing of your colleague.
Hi Aaron @leftquark - I appreciate the difficulties that you have been having and extend my condolences on the loss of a colleague but would welcome a resolution to this matter in the very near future. We are approaching the two year mark.
@leftquark Is this now buried forever? Could you please give a status report?
It's still on our minds -- the big behind-the-scenes work the team has been doing is starting to wrap up and we're hoping we can get eyes on this one soon. I've asked the API folks for an update.
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
hey @leftquark this sounds promising to me ... even if it is around some time i am still very interested in a solution to this bug. i believe it, when i see it ,-)
I hate to keep pushing this back, but the team has another couple weeks of wrapping up the big project. They're hoping they can get to this in a month. It's still queued up to be next though!
Former SmugMug Product Team
aaron AT aaronmphotography DOT com
Website: http://www.aaronmphotography.com
My SmugMug CSS Customizations website: http://www.aaronmphotography.com/Customizations
@leftquark For me it's not longer relevant. I got extremely tired of waiting for answers, added a step to my workflow to change all of the captions to influde location information ( a clunky workaround) and have now taken over two days re-uploading every single gallery multiple times so that all of the files are synced and no longer show "unknown" as file name. Since I have so many pictures posted in fora, deleting all the photos and uploading anew was not really an option. (I'm sure I've already got a lot of broken links in DGRIN but the process of checking this is extremely tedious.) Then of course the result of switching to the SmugMug plugin and reverse-syncing is that my (existing) publish galleries are no longer in Lightroom smart collections but "dumb" collection so now every time I change a parameter that would normally automatically add or subtract a photo from a collection I'll have to remember to do this by hand. If there is any way to make these collections smart again and not lose to links to existing posted photos, I'd love to know.
So Aaron, you won. I am not at all happy about it, but it is so.