Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.
How should system upgrades be handled?
Currently only the initial installation is foreseen, however upgrades should be easy to install as well. This could be handled in a similar fashion as plugins, i.e. download the latest version and upgrade JAS using the backend.
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 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)).
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...
DT timezone & date support support
Add change default timezone(timezone=false (=default in config)) and date(format, tme=false (= current time)) to DT.
Data add touch item action
A simple action which updates the "updated" time stamp and nothing else. Handy when needing to trigger recache of lister plugin sections when multiple modules are involved.
$d=Data::cache("module", "touch", "item");
$d->setValue("nr", $id);
$d->submit();
Only "forceUpdate" and ID fields will be checked and subitted, all other fields may not be checked to avoid potential errors. Storage object "edit" function should be used which should just update the relevant forceUpdate fields...
Determine what to do with sync
The sync support is rather buggy. It should probably disabled as part of the 1.0 release and reworked as part of JAS 1.1.
Rewrite template pageBrowser
Current page browser is far to restrictive and doesn't support advanced template features.
Also consider remarks in: PLGN14AUG003
Workflow dynamic conditions
Workflow should have support dynamic conditions. That is, determineState should check with the reference module if the state may be changed. This can be done using the "disable" parameter by which the disabled options are provided to determineState, validateState and getOptions.
Additionally the workflow transitions module itself can do so user validations (root only, has to be in group, etc) before it allows for a certain state change.
