Protect from purge, for example we need the download history for Expiry date and if it no longer exists users can't be notified
Protect from purge, for example we need the download history for Expiry date and if it no longer exists users can't be notified
<!-- github-comment-id:3051820113 -->
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.
Suggestion to make download history seperate. Once visit history is purged we loose who downloaded what image.
When you say "seperate", you mean "in another table than piwigo_history" or simply "protected against purge"?
Protect from purge, for example we need the download history for Expiry date and if it no longer exists users can't be notified
Create seperate action purge visits and purge downloads, have explicit actions