Instead of trying to delete all selected photos "at once" on the form submission, Piwigo should delete photos by "blocks" of 100 photos (for example). It would make deletion of 5672 photos much more user friendly: less chance to fail, show a progression instead of a very long page to display.
Instead of trying to delete all selected photos "at once" on the form submission, Piwigo should delete photos by "blocks" of 100 photos (for example). It would make deletion of 5672 photos much more user friendly: less chance to fail, show a progression instead of a very long page to display.
<!-- github-sync-id:197623649 -->
It works fine on my dev environment. Tomorrow I will test on a Piwigo with tens of thousands of photos and try to delete several thousands photos.
It works fine on my dev environment. Tomorrow I will test on a Piwigo with tens of thousands of photos and try to delete several thousands photos.
<!-- github-comment-id:269246246 -->
@plegall looks fine except for the return from Web service (IMHO) because
success is useless (otherwise pwg error)
Just the details array should be fine (or the number of photos deleted as I
cannot see what else you could ever return)
@plegall looks fine except for the return from Web service (IMHO) because
success is useless (otherwise pwg error)
Just the details array should be fine (or the number of photos deleted as I
cannot see what else you could ever return)
On Dec 26, 2016 23:32, "Pierrick Le Gall" <notifications@github.com> wrote:
> @modus75 <https://github.com/modus75> can you review before I merge on
> master?
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <https://github.com/Piwigo/Piwigo/issues/593#issuecomment-269246111>, or mute
> the thread
> <https://github.com/notifications/unsubscribe-auth/AJRc9v4gjz9Sbl_ubC3qtS3iVckwjWFUks5rMEB1gaJpZM4LV7ra>
> .
>
<!-- github-comment-id:269246448 -->
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.
Instead of trying to delete all selected photos "at once" on the form submission, Piwigo should delete photos by "blocks" of 100 photos (for example). It would make deletion of 5672 photos much more user friendly: less chance to fail, show a progression instead of a very long page to display.
@modus75 can you review before I merge on master?
It works fine on my dev environment. Tomorrow I will test on a Piwigo with tens of thousands of photos and try to delete several thousands photos.
@plegall looks fine except for the return from Web service (IMHO) because
success is useless (otherwise pwg error)
Just the details array should be fine (or the number of photos deleted as I
cannot see what else you could ever return)
On Dec 26, 2016 23:32, "Pierrick Le Gall" notifications@github.com wrote: