Currently the only way to request data from the APIs is to send the appropriate data via the "request" parameter. While this gives a lot of control it's also quite cumbersome to create a request. To make this simpler the requests should also support "direct parameters".
Examples
https://host.name/api/json/?m=categories&a=view&e=all&title=textView all categories that match the title "text".If the "m" parameter is set it should set up a Data object and setRequestValues, i....
The current MD5 file signatures allows end users to check whether the file is still in tact. However it doesn't garanty the file (and MD5) haven'/files/ field and API should support PGP signatures.
JAS already support RSS formats for parsing and rendering but it should also have an API. It will probably be limited to read-only and it will be somewhat different from the other APIs. The idea is to work with templates to have some flexibility in defining the message format. Additionally it should probably support default rendering for all modules. Modules
/api/rss/module name/ will generate an Atom 1.0 feed like so:
<title>Title field value</title>
<summary>Same a...
When switching projects via the APIs it does load the new project but overwrites the current session (clearing the login etc). Depending on the scenario this may be desired behavior however it seems more logical to take a similar approach as how the backend handles multi project sessions.
Moreover it seems debatable whether switching projects with the APIs is something that should be allowed on a project basis. If project A allows it but project B doesn't then there's no way to switc...
It should be possible to set JAS in maintenance mode. This should show an "under maintenance" page for all projects.
Since this the goal is to allow for upgrades of various systems (include JAS itself) it should limit dependencies as much as possible. I.e. the earlier page can be shown the better, keeping in mind that JAS itself should remain accessible.
It would make sense to have a this in a config option in the JAS project with a configurable text. Once enabled the text should...
JAS should support JSON parsing and rendering which in turn can be used for a full-fledged read/write API. The JavaScript HTTP class should be extended to support this as well.
Currently all protocols (socket, http, smtp, etc), formats (csv, xml, etc) and APIs (data, csv, xmli) all reside in the include folder. They should be moved to the relevant subfolders to keep the include folder somewhat clean.
The pager plugin is available through $this->pager, the API that it offers should be properly defined:
Frontend
function setTitle($title)
function jasScript($show)
function addJavaScript($file)
function removeJavaScript($file)
function addStyleSheet($file, $media=false)
function removeStyleSheet($file)
function metaKeywords($keywords, $append=false)
function metaDescription($text, $append=false)
function addRelationLinks($rel, $link)
function removeRelationLinks($rel, $link)...
Report issues
We're currently not allowing issue reporting directly via ITS. Please use the feedback form to submit your issues.