SUMMARY During a session of uploading hundreds of photos and videos, I encountered two specific files for which upload to SmugMug fails. The two files upload fine using SmugMug's web UI, but fail from digiKam export. Other photos in the same folder taken by the same camera upload fine. Perhaps there is something about these files or their metadata which is causing a problem with the SmugMug API or how the API is used, but there is insufficient detail in the console logging to identify a problem. STEPS TO REPRODUCE 1. Select one of these files. 2. Click Export -> Export to SmugMug... 3. Select Album for upload destination. 4. Click "Start Upload" OBSERVED RESULT Error dialog appears. Dialog title: Uploading Failed -- digiKam Dialog contents: Failed to upload photo to SmugMug. Connection closed Do you want to continue? Yes No Logging in console after clicking "Start Upload": unknown: slotStartTransfer invoked unknown: d->currentAlbumID -1 Digikam::DBInfoIface::itemInfo: Database Info populated for QUrl("file://[path...]/[filename].jpg") unknown: url to upload "https://upload.smugmug.com/" unknown: slotStartTransfer done unknown: error code : QNetworkReply::RemoteHostClosedError error text "Connection closed" EXPECTED RESULT Photo uploads successfully. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.24.7-0ubuntu0.1 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.7 (built against 5.15.7) ADDITIONAL INFORMATION
Without the corresponding file that failing we won't be able to reproduce it. Unfortunately SmugMug also charges money for access and our developer account will be disabled after 30 days. So if anyone is paying for SmugMug and wants to fix it, feel free to... Maik
*** This bug has been marked as a duplicate of bug 434556 ***
Hi Maik I don't think this is a duplicate of bug 434556, because that bug is about some random intermittent failure where all uploads stop working though they work at a different time. This bug is a reliable failure for a specific file, while all other files continue working. Is there a way to get digiKam to log more detail that what I've already included here (which was using 'export QT_LOGGING_RULES="digikam*=true"')?