Since Piwigo 12, a third-party app must call pwg.images.uploadCompleted to empty the lounge. If it calls it at the end of a series of uploads, calling pwg.categories.getList before the end of the series does not return already uploaded images.
With an app appending each image in its album as soon as it is uploaded (in cache), this leads to the situation where already uploaded images are removed from the album view when the user tries to refresh the album content or kills/restarts the app. And if the app uploads images in the background and the user launches the app before the upload series is completed, none of the uploaded images are visible.
It is possible to edit the properties of an image with pwg.images.setInfo before emptying the lounge. Similarly, the method pwg.categories.getList should return all images even if the lounge has not been emptied yet.
Since Piwigo 12, a third-party app must call `pwg.images.uploadCompleted` to empty the lounge. If it calls it at the end of a series of uploads, calling `pwg.categories.getList` before the end of the series does not return already uploaded images.
With an app appending each image in its album as soon as it is uploaded (in cache), this leads to the situation where already uploaded images are removed from the album view when the user tries to refresh the album content or kills/restarts the app. And if the app uploads images in the background and the user launches the app before the upload series is completed, none of the uploaded images are visible.
It is possible to edit the properties of an image with `pwg.images.setInfo` before emptying the lounge. Similarly, the method `pwg.categories.getList` should return all images even if the lounge has not been emptied yet.
<!-- github-sync-id:1053017332 -->
I like the idea to queue uploaded images in a lounge, but this lounge should not be a room waiting for an external trigger.
Images should be processed in a background or parallel thread to keep the server reactive. The server knows when images are uploaded and should trigger the process himself.
I like the idea to queue uploaded images in a lounge, but this lounge should not be a room waiting for an external trigger.
Images should be processed in a background or parallel thread to keep the server reactive. The server knows when images are uploaded and should trigger the process himself.
<!-- github-comment-id:968564891 -->
Similarly, the method pwg.images.uploadAsync does not return the category in which the image is supposed to be uploaded. The category field is empty, certainly because the image is not inside the album until the pwg.images.uploadCompleted method is called.
Similarly, the method `pwg.images.uploadAsync` does not return the category in which the image is supposed to be uploaded. The category field is empty, certainly because the image is not inside the album until the `pwg.images.uploadCompleted` method is called.
<!-- github-comment-id:1004228832 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Since Piwigo 12, a third-party app must call
pwg.images.uploadCompletedto empty the lounge. If it calls it at the end of a series of uploads, callingpwg.categories.getListbefore the end of the series does not return already uploaded images.With an app appending each image in its album as soon as it is uploaded (in cache), this leads to the situation where already uploaded images are removed from the album view when the user tries to refresh the album content or kills/restarts the app. And if the app uploads images in the background and the user launches the app before the upload series is completed, none of the uploaded images are visible.
It is possible to edit the properties of an image with
pwg.images.setInfobefore emptying the lounge. Similarly, the methodpwg.categories.getListshould return all images even if the lounge has not been emptied yet.I like the idea to queue uploaded images in a lounge, but this lounge should not be a room waiting for an external trigger.
Images should be processed in a background or parallel thread to keep the server reactive. The server knows when images are uploaded and should trigger the process himself.
Similarly, the method
pwg.images.uploadAsyncdoes not return the category in which the image is supposed to be uploaded. The category field is empty, certainly because the image is not inside the album until thepwg.images.uploadCompletedmethod is called.Inefficient but working solution: empty the lounge after each single upload.