Facebook webservice: content access denied
caulier.gilles at gmail.com
Sun Jun 17 09:32:04 BST 2018
I started to run static analyzers over your branch.
cppcheck results are here :
Look especially the reports located in core/utilities/assistants/...
Take a care, sometimes cppcheck report false errors, sometimes, no
(:=)))... You can forget all others place where i already fixed all most
I run now clang tool, which come generally with better results.
2018-06-17 2:21 GMT+02:00 Thanh Trung Dinh <dinhthanhtrung1996 at gmail.com>:
> Gilles, Maik,
> I have to reopen this post again, since I got a problem here again with
> Facebook for a week and this may affect the 6.0.0 beta release. The problem
> is that now I cannot create albums on Facebook via digiKam a anymore.
> Back to 22 May, when Maik tested my code for the first time, an album name
> "Test2018" was created normally on test user "Dick Albfbdhiehefa
> After that I created some other to test and then deleted them. I was also
> able to upload photos to those albums, and to no album (indeed an album
> "digiKam photos" will be created automatically if no album is assigned to
> uploaded photos).
> But now, I cannot create albums anymore. Each time doing that, I got the
> error "/content access denied/" again. When inspecting json response from
> API call, the error message is "/(#200) Insufficient permission to create
> album/" However, thing is stranger when I can still upload photos to
> existant albums, and to no album as well. Tracking down commits from 22
> after the first 2 commits that I made many changes in fbtalker.cpp, other
> commits were mostly about polish or some minor modifications.
> In fact, because of that problem, I can't finish app review. Therefore,
> Facebook export tool will not be able to be used in public mode (for users
> not tester, admin, etc.).
> So, Gilles, Maik, could you please review my code for Facebook tool? It's
> still possible that I made mistakes in codes. Otherwise, do you have any
> ideas, suggestions about that problem?
> Many thanks.
> Sent from: http://digikam.1695700.n4.nabble.com/digikam-devel-
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Digikam-devel