adam/Piwigo
1
0 Fork 0
mirror of https://github.com/Piwigo/Piwigo.git synced 2026-10-30 21:52:00 +01:00
Code Issues 657 Packages Projects Releases Wiki Activity

Unable to batch upload #1825

New Issue
Closed
opened 2026-10-05 00:57:57 +02:00 by adam · 5 comments
adam commented 2026-10-05 00:57:57 +02:00
Owner
Copy link
Copy source

Unable to batch upload files to piwigo hosted site via Remote-Sync. Errors given on all files are

15:34:23.044 [Thread-4] INFO o.p.r.api.sync.SyncDirectoryWalker - Uploading Dunkers_0053.jpeg in album with ID null
15:34:23.044 [Thread-4] ERROR o.p.r.api.sync.ConnectedWalker - Cannot upload an image without an album. Please move the image in a subfolder.

Additionally unable to upload via FTP as the documentation is out of date (Photos>Add>FTP+Sync does not exist anymore)

Version: 14.1.0

Unable to batch upload files to piwigo hosted site via Remote-Sync. Errors given on all files are 15:34:23.044 [Thread-4] INFO o.p.r.api.sync.SyncDirectoryWalker - Uploading Dunkers_0053.jpeg in album with ID null 15:34:23.044 [Thread-4] ERROR o.p.r.api.sync.ConnectedWalker - Cannot upload an image without an album. Please move the image in a subfolder. Additionally unable to upload via FTP as the documentation is out of date (Photos>Add>FTP+Sync does not exist anymore) Version: 14.1.0 <!-- github-sync-id:2106387015 -->
adam closed this issue 2026-10-05 00:57:57 +02:00
adam commented 2026-10-05 00:57:58 +02:00
Author
Owner
Copy link
Copy source

relate to https://github.com/Piwigo/Piwigo-Java/issues/25 and more precisely:

Unable to parse response [...] : Element 'save_visits' does not have a match [...]

relate to https://github.com/Piwigo/Piwigo-Java/issues/25 and more precisely: > Unable to parse response [...] : Element 'save_visits' does not have a match [...] <!-- github-comment-id:1918793143 -->
adam commented 2026-10-05 00:57:59 +02:00
Author
Owner
Copy link
Copy source

For the record, it's related to #1920 : we have added a new output parameter to API method pwg.session.getStatus and the Java code of PiwigoRemoteSync doesn't like, at all, when something new appears in the response. Not very flexible in my opinion...

For the record, it's related to #1920 : we have added a new output parameter to API method `pwg.session.getStatus` and the Java code of PiwigoRemoteSync doesn't like, at all, when something new appears in the response. Not very flexible in my opinion... <!-- github-comment-id:1918811886 -->
adam commented 2026-10-05 00:58:00 +02:00
Author
Owner
Copy link
Copy source

@macstrat because you're a Piwigo.com client, specific information: this bug fix has been backported on your Piwigo. No need to wait for the 14.3.0

@macstrat because you're a Piwigo.com client, specific information: this bug fix has been backported on your Piwigo. No need to wait for the 14.3.0 <!-- github-comment-id:1918813965 -->
adam commented 2026-10-05 00:58:00 +02:00
Author
Owner
Copy link
Copy source

For the record, it's related to #1920 : we have added a new output parameter to API method pwg.session.getStatus and the Java code of PiwigoRemoteSync doesn't like, at all, when something new appears in the response. Not very flexible in my opinion...

Thank you for the quick fix. I would agree its not very flexable at all. The code is no longer maintained. Has Piwigo thought about forking the git and creating their own uploader?

> For the record, it's related to #1920 : we have added a new output parameter to API method `pwg.session.getStatus` and the Java code of PiwigoRemoteSync doesn't like, at all, when something new appears in the response. Not very flexible in my opinion... Thank you for the quick fix. I would agree its not very flexable at all. The code is no longer maintained. Has Piwigo thought about forking the git and creating their own uploader? <!-- github-comment-id:1919139600 -->
adam commented 2026-10-05 00:58:01 +02:00
Author
Owner
Copy link
Copy source

Has Piwigo thought about forking the git and creating their own uploader?

It's not the problem. Piwigo Remote Sync is already our code. I mean we can maintain it. We just don't have much people willing to work on it. But we will if we have to.

> Has Piwigo thought about forking the git and creating their own uploader? It's not the problem. Piwigo Remote Sync is already our code. I mean we can maintain it. We just don't have much people willing to work on it. But we will if we have to. <!-- github-comment-id:1919170241 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/Piwigo#1825