Bug 323118

Summary:	SmugMug API access fails after SmugMug relaunch [patch]
Product:	[Applications] digikam	Reporter:	Gary Edberg <ginslo>
Component:	Plugin-WebService-SmugMug	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	caulier.gilles, doug, rharrison, tim
Priority:	NOR
Version:	3.5.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:	http://commits.kde.org/kipi-plugins/091d605f4a6b4524a6985db2301c314a90e3604c	Version Fixed In:	4.0.0
Sentry Crash Report:
Attachments:	Patch to smug kipi-plugin that fixes this bug. Updated patch, which addresses Christoph's comments.

Description Gary Edberg 2013-08-02 19:33:14 UTC

Smugmug just released a major makeover of their website this past Tuesday (7/30/2013). Since migrating my existing account to the new version I am no longer able to export photos from Digikam using export tool.

This is the error displayed:
SmugMug Call Failed: invalid method

This issue is also affecting any application using Kipi plugins and in fact fails in any API access including F-Spot (Gnome) as well so it's not Digikam/Kipi specific and likely a Smugmug issue. 

This is an irritating inconvenience, but not a complete show-stopper because Digikam does allow drag and drop directly from the DigiKam UI to the SmugMug bulk upload UI.

Reproducible: Always

Steps to Reproduce:
1. Select photos to upload
2. Click Export -> SmugMug
3. Enter Credentials
Actual Results:  
Popup alert with this message:

SmugMug Call Failed: invalid method

Expected Results:  
Listing of available folders, ability to create new folders and ability to complete file transfer

Comment 1 Russell Harrison 2013-08-12 23:02:11 UTC

I'm also seeing the same issue on Fedora 18.

$ rpm -qa | grep kipi
kipi-plugins-3.3.0-1.fc18.x86_64
kipi-plugins-doc-3.3.0-1.fc18.noarch
kipi-plugins-libs-3.3.0-1.fc18.x86_64
libkipi-4.10.5-1.fc18.x86_64

I'll see if I can get any information from SmugMug support.

Comment 2 Gary Edberg 2013-08-13 01:48:33 UTC

Thanks Russell. The response I got from SmugMug was that they were overwhelmed with support issues during the launch aftermath. Perhaps things have settled down a little by now.

Also, fyi, I've got essentially the same packages other than mine being fc19

$ rpm -qa | grep kipi
kipi-plugins-doc-3.3.0-1.fc19.noarch
libkipi-4.10.5-1.fc19.x86_64
kipi-plugins-3.3.0-1.fc19.x86_64
kipi-plugins-libs-3.3.0-1.fc19.x86_64

Comment 3 Tim Newsome 2013-09-28 21:32:15 UTC

Created attachment 82531 [details]
Patch to smug kipi-plugin that fixes this bug.

This version works for me, using kphotoalbum 4.4 and KDE Development Platform 4.10.5.

Comment 4 Christoph Feck 2013-10-05 21:40:05 UTC

Thanks Tim for the patch. Please explain why you added "<<<" to the window titles. Also, please remove the spaces around the brackets in the added qSort call.

Comment 5 Tim Newsome 2013-10-06 01:28:27 UTC

The <<< was for my debugging (so I could confirm that my plugin was actually being run). I've removed it.
I also fixed the qSort( ) formatting like you asked. I'll update the attached patch.

Thanks for reviewing!

Tim

Comment 6 Tim Newsome 2013-10-06 01:29:45 UTC

Created attachment 82683 [details]
Updated patch, which addresses Christoph's comments.

Comment 7 caulier.gilles 2013-10-29 17:48:17 UTC

Git commit 091d605f4a6b4524a6985db2301c314a90e3604c by Gilles Caulier.
Committed on 29/10/2013 at 17:45.
Pushed by cgilles into branch 'master'.

Apply patch #82683 from Tim Newsome about to make smug export work with smugmug's new interface.

Changed most http_post() calls to get() calls. Apparently POST doesn't
work with the new interface albums.
Upgraded the interface we use from 1.2.0 to 1.2.2, since that's the
latest version in the 1.2 train.
Sort the list of albums that we receive from smugmug before presenting
it to the user.
FIXES-IN: 4.0.0

M  +5    -0    smug/smugitem.h
M  +14   -20   smug/smugtalker.cpp

http://commits.kde.org/kipi-plugins/091d605f4a6b4524a6985db2301c314a90e3604c

Comment 8 doug 2015-01-25 07:05:17 UTC

*** Bug 343263 has been marked as a duplicate of this bug. ***