Bug 381354 - Dropbox export: API v1 deprecation
Summary: Dropbox export: API v1 deprecation
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-DropBox (show other bugs)
Version: 5.5.0
Platform: Other All
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-18 09:17 UTC by Leonard Lausen
Modified: 2019-01-08 11:29 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.8.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leonard Lausen 2017-06-18 09:17:33 UTC
Digikams export to Dropbox feature seems to rely on the Dropbox v1 API which is deprecated since June 2016 and will be shut down end of June 2017. When authorizing digikam to export to Dropbox, Dropbox will display a warning to the user that API v1 is soon to be shut down.

Doing only a quick search I have not found any issue covering this topic. So I would like to make you aware that either a transition to the v2 API or the removal of the Dropbox export feature will be necessary.

https://blogs.dropbox.com/developers/2016/06/api-v1-deprecated/
Comment 1 Iris Hammer 2017-06-26 08:14:21 UTC
I can confirm this. 
Connecting to dropbox shows that it stops at 28. June 2017.
Comment 2 Maik Qualmann 2018-01-07 08:35:13 UTC
Git commit acae55991a4f51e727c09609216cfff85697724a by Maik Qualmann.
Committed on 07/01/2018 at 08:33.
Pushed by mqualmann into branch 'master'.

dropbox tool ported to API V2 and OAuth2
FIXED-IN: 5.8.0

M  +2    -1    NEWS
M  +3    -9    dropbox/dbalbum.cpp
M  +115  -282  dropbox/dbtalker.cpp
M  +30   -41   dropbox/dbtalker.h
M  +1    -12   dropbox/dbwidget.cpp
M  +44   -88   dropbox/dbwindow.cpp
M  +2    -8    dropbox/dbwindow.h
M  +2    -2    dropbox/mpform.cpp
M  +3    -3    dropbox/plugin_dropbox.cpp

https://commits.kde.org/kipi-plugins/acae55991a4f51e727c09609216cfff85697724a
Comment 3 Maik Qualmann 2019-01-08 11:29:19 UTC
*** Bug 402993 has been marked as a duplicate of this bug. ***