One nice feature would be to have statistics page that allows you to dynamically generate any type of statistics on the various modules.
Some examples:
Total rows per module (already in database section)
Adds/Updates per day
Top used categories
It should be flexible to allow any type of statistics to be pulled using the aggregation fields. It's probably handy to be able to store presets so they can be easily rerun later (prolly wise to store them in the "JAS" project so the...
The JAS backend should support recursive delete options.
Note that this probably also requires recurseCategories / recurseContent to be submitted in the CMS. This is probably best done by setting use=form.
The localfile (and probably localfiles and localdirectory) field don't take into account a module can be initialized from different path. Subsequently the using the module from a different path causes it to fail on "Invalid local file directory"/files/index.php since that is called from different path.
It seems logical to always consider the lock down path to the relative folder of the root and thus _path["root"] should be added in front of the file path. Note however that this can't be do...
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...
It seems the URLs are created and/or rendered incorrectly. This issue tends to occur when multiple environments use the same database where the hostnames differ. Or rather when in one environment the default project is JAS and in the other it isn't.
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