Quote:
Originally Posted by GakcaT
1) Unfortunately, there is old offline version of documentation in ISPmanager. Now you can see revised version of documentation at http://www.ispsystem.com/en/software...documentation/. But at the present time there isn't any information about ISPmanager API on this website.
Information about menu levels is located in /usr/local/ispmgr/etc/ispmgr.xml file.
What are your working hours? We have a difference in time zones, I'll try answer on your questions ASAP. |
Thank you. We're usually available from 8am-2am EST.
We've made some progress on this topic and have created our test scenario of adding an item; however, the docs are very lacking in the toolbar button to column data area. We've managed to get the column data via a CGI to present the XML data properly, but we cannot seem to figure out how to interact with the toolbar buttons.
Essentially, we have 3 buttons (start/stop/restart) and the column data present a single line of information. We cannot figure out how to have the buttons interact with that data. When the page loads, all buttons are disabled, and when we click on the single item in the column data, the buttons activate, but if we click on any of the buttons, nothing happens. What is actually going on behind the scenes when a button is created, i.e., what kind of POST/GET request is made and with what specific data?
Ideally, we'd like for the system to recognize that the item is 'running' (we have a status in one of our columns) and then only activate the stop/restart buttons if it is running. If the status is reporting 'stopped', then only the start/restart buttons activate. But of course, before we can even pursue that possibility, we just need the buttons to actually work.
Quote:
Originally Posted by GakcaT
2) Do you mean "Nodes are placed on new lines and their values are placed on the same lines"? We store all nodes on new lines. Also we handle these *.xml files (look for changes, mistakes and etc.). This is not a problem.
|
The grammar, terminology, etc. are not suitable for our service and customers (your russian-to-english translations are not quite accurate and our customers are used to different terminology), so we need to be able to update those .xml files accordingly. We don't mind doing so, as long as we can track any changes in your versions of it between upgrades/releases; however, you do not have each element on a single line, so tracking becomes very difficult. For example, you might currently have something like the following:
---
...
</message><messages name="messagesname1">
<msg name="msgname1">String for name1</msg>
<msg name="msgname2">String for name2</msg>
<msg name="msgname3">String for name3</msg><msg name="msgname4">String for name4</msg><msg name="msgname5">String for name5</msg>
</message><messages name="messagesname2">
...
---
As you can see above, you have the closing tag for the previous messages element on the same line as the next messages element opening tag, as well as having *3* msg elements on one line. This poses us a problem as in some cases you have more than 100 elements on a single line in the xml files and if just one of them changes between your releases, the diff reports that the line with 100 elements has changed, but we then need to manually review that single line to figure out what actually changed, which is very time-consuming. What we need is for your xml files to cleanly have a single element on each line, such as:
---
...
</messages>
<messages name="messagesname1">
<msg name="msgname1">String for name1</msg>
<msg name="msgname2">String for name2</msg>
<msg name="msgname3">String for name3</msg>
<msg name="msgname4">String for name4</msg>
<msg name="msgname5">String for name5</msg>
</messages>
<messages name="messagesname2">
...
---
Thank you for your attention to this matter.