Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.
JAS backend filters
The JAS backend should have a filter section to more effectively drill down in the data. the filters should be automatically generated based on the module (similar to the CMS). Text fields should have a inline dropdown with available values (like the search box).
Additionally it should remember the last set filters if the user comes back to the page later. This will require a "Reset" button to set all values to their defaults.
Backend statistics page
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...
Add recursive category delete to backend
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.
Add round/floor/ceil field mutilation
Float and price fields should have round/floor/ceil field mutilations
Mutilate::round(number, precision=0, mode=false)
mode: normal, floor, ceil
if precision > 0 and mode = floor/ceil:
floor(number * pow(10, precision))/
pow(10, precision)
Data::addMutilationFormat_Template
Add implied ranking field to ITS
High priority and low impact can and should be quickly fixed whereas low priority and high impact will end up lower on the list. With this in mind a "ranking" can be determined using the priority and impact fields (similar to the risk score in the Procon plugin).
Priority scores:
High
Medium
Low
Impact score:
LowMedium
High
Ranking = Priority score + Impact score - 1
Examples:
1 = High priority + Low impact
2 =
High priority + Medium impact
2 = ...
Add show_page and show_pages support
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)).
localfile download issues
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...
User module features
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...
root_url doesn't seem to work properly in native projects
Templates using root_url in a native project (default project isn't JAS) seems to incorrectly create the URLs. Presumably this is due to the "/images/" functionality in the pager plugin.
