The "sync metadata" action generates several AJAX requests to pwg.images.syncMetadata. Unfortunately, they are sent in parallel, all at once. That is a nonsense to me. Piwigo frontend shoud send them one by one. With the use of queuedManager just like it's done with pwg.images.delete.
The "sync metadata" action generates several AJAX requests to `pwg.images.syncMetadata`. Unfortunately, they are sent in parallel, all at once. That is a nonsense to me. Piwigo frontend shoud send them one by one. With the use of `queuedManager` just like it's done with `pwg.images.delete`.
<!-- github-sync-id:2366703463 -->
adam
changed title from [batch manager, sync metadata] use AJAX requests in sequence instead of parallel to [batch manager, sync metadata] use AJAX requests in sequence instead of parallel 2026-10-27 11:30:10 +01:00
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.
The "sync metadata" action generates several AJAX requests to
pwg.images.syncMetadata. Unfortunately, they are sent in parallel, all at once. That is a nonsense to me. Piwigo frontend shoud send them one by one. With the use ofqueuedManagerjust like it's done withpwg.images.delete.[batch manager, sync metadata] use AJAX requests in sequence instead of parallelto [batch manager, sync metadata] use AJAX requests in sequence instead of parallel