Generally show_from+show_total are used to split data over multiple pages. As such it's seems logical to support this natively. If show_page is set it should be used to calculate show_from (show_page * show_total) prior to getting the data (and thus overwriting the set show_from). When the data is gathered and show_count is set this value should be used to calculate show_pages ( ceil ( show_count / show_total)).
IP (range) lock downbrute force protection (X attempts from same IP per Y minutes)email confirmation (should contain only the logic, requires an email field in a project module)timezone / language settingsseparators (also CSV) settingsdate/time format settingsEach feature should be configurable (config module) and should have the option to be locked down for admins (non owner). This should also be extended to changing username and password.
It seems logical to add a user/settings action th...
Currently the page browser logic in the lister plugin only remembers the sorting and the filters in rewrite mode. It should use a more generic approach where it reads the relevant filters from the Data object and use that.
Additionally it's probably a good idea to split off the page browser logic in the lister plugin from the output function so other plugins can easily reuse this logic.
Convert by: JAS13OCT014
The file (and image) field should get an additional field for the MD5 hash. The /files/ would then need a "MD5" variable that would download a "text/plain" file with the hash as content. The filename can be generated based on the original filename and a .md5 suffix (filename.ext.md5).
Note that it's probably wise to add a MD5 property to the file/image fields to allow it to be enabled/disabled.