To avoid that the historical table does not inflate of too without knowing what is this functionality, for rendering comprehensible well with the webmasters that it is a greedy option, best would be to decontaminate the history and it will be with the webmaster to activate it.
By activating it, an informed message consequences
**Reported by Gotcha on 27 Mar 2010 13:47**
To avoid that the historical table does not inflate of too without knowing what is this functionality, for rendering comprehensible well with the webmasters that it is a greedy option, best would be to decontaminate the history and it will be with the webmaster to activate it.
By activating it, an informed message consequences
**Additional information:** http://fr.piwigo.org/forum/viewtopic.php?pid=138009#p138009
[Piwigo Bugtracker #1540](http://piwigo.org/bugs/view.php?id=1540)
<!-- github-sync-id:97226033 -->
I no longer think it's a good idea. Keeping the installation script as simple as possible is more important. But the issue is still the same: the history table might become huge. This is why I want to implement #370
I no longer think it's a good idea. Keeping the installation script as simple as possible is more important. But the issue is still the same: the history table might become huge. This is why I want to implement #370
<!-- github-comment-id:233961849 -->
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.
Reported by Gotcha on 27 Mar 2010 13:47
To avoid that the historical table does not inflate of too without knowing what is this functionality, for rendering comprehensible well with the webmasters that it is a greedy option, best would be to decontaminate the history and it will be with the webmaster to activate it.
By activating it, an informed message consequences
Additional information: http://fr.piwigo.org/forum/viewtopic.php?pid=138009#p138009
Piwigo Bugtracker #1540
I no longer think it's a good idea. Keeping the installation script as simple as possible is more important. But the issue is still the same: the history table might become huge. This is why I want to implement #370