Jump to:
| Project: | Image Publishing |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Issue Summary
The 0.2.0 version of kipi-plugins galleryexport is only checking/passing a GALLERYSID cookie, and so drops the Drupal session, causing access denied errors on upload.
While it is possible to get this to work by hacking bootstrap.inc from session_name('SESS' . md5($session_name)); to session_name('GALLERYSID'); (possibly this could be done in hook_init) I don't believe this is the correct fix, because I don't think the session name is part of the G2 API spec and it could be quite disruptive.
Hence I have opened an issue upstream at http://bugs.kde.org/show_bug.cgi?id=195136 and creating this one for tracking.
In the meantime I would suggest that we add a note to the image_pub project page that digiKam compatibility is currently broken and reference this link.
Comments
#1
#2
Hello Owen,
thanks for your very helpful report and the work you've done on debugging this. I've mentioned the problem on the project page as you suggested, and put a link in to this issue. Hope this is OK!
However, I'm wondering if there might be something relatively non-hacky we could do with image_pub that would fix the problem. The g2remote protocol contains an "authToken" field, which image_pub doesn't yet implement. This has been touched on in a previous issue, but was never implemented: #205535: Gallery Remote: Module incompatible with latest GR protocol
It might be worth investigating if digiKam is sending authToken fields in its dealings with image_pub. If you find that it is, please let me know.
#3
From my reading of the kipi-plugins galleryexport source, I don't believe it handles authToken, but I could be wrong there. From my chat on IRC I think they would like to do a rewrite at some point, which might make sense.
#4
confirming the issue & subscribing