Bug 347452 - Facebook export does not work any more -- authentication problem
Summary: Facebook export does not work any more -- authentication problem
Status: RESOLVED UNMAINTAINED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-WebService-Facebook (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-08 22:59 UTC by tps
Modified: 2023-05-10 06:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description tps 2015-05-08 22:59:34 UTC 
Trying to export to facebook leads to authentication errors. It does not matter how often you try to update the authentication URL. Login to facebook will fail.

Reproducible: Always

Steps to Reproduce:
1. Install digikam, kipi-plugins
2. try to export pictures to facebook


Actual Results:  
authentication fails

Expected Results:  
authentication OK, exporting pictures
Comment 1 Vangelis 2015-05-09 21:30:20 UTC 
Same issue here! It was working until recently.
Comment 2 magusofthedark 2015-05-12 05:34:26 UTC 
Happening to me too.

I'm on version 3.5.0 of digiKam in OpenSuse 13.1. Worked fine until very recently. I also have the separate bug where the url appears too briefly, but getting that url and pasting it in gives me this bug.
Comment 3 tps 2015-05-12 16:28:55 UTC 
Seems to be related to recent Facebook API changes. Maybe these reveal bugs never shown up before, because Facebook states no changes for programs using the API would be necessary.
Comment 4 magusofthedark 2015-05-13 03:02:00 UTC 
Is this a dupe of 347194?
Comment 5 tps 2015-05-16 10:58:55 UTC 
Same for digikam 4.10.0: Facebook-Aufruf fehlgeschlagen: User must specify a valid extended permission or data permission (100)
Comment 6 tps 2015-05-16 11:02:21 UTC 
#4: yes it is.
Comment 7 tps 2015-05-16 11:02:42 UTC 

*** This bug has been marked as a duplicate of bug 347194 ***
Comment 8 caulier.gilles 2023-05-10 05:44:38 UTC 
fixed with bug 347194
Comment 9 caulier.gilles 2023-05-10 05:46:49 UTC 

*** This bug has been marked as a duplicate of bug 347194 ***
Comment 10 caulier.gilles 2023-05-10 06:19:59 UTC 
fixed with 347194