XULadmin User Manual
From Cyclone3 Wiki
Contents |
User Interface
Login Window
Main Window
Modules
Articles
Images
Polls
Video
Files and Directories
Discussion Forums
Content
E-commerce
Administration
Intranet
Exports
In general XULadmin employs the "What You See is What You Get" principle. This means you get exactly what you see in the listings or view pages. If paging is enabled, you only see the current page. If you hide columns in the listings they will not appear in the exports either.
This means you can export your changes without having to save them into the database.
Currently these export document formats are supported: OpenDocument Text and Spreadsheet, CSV, XHTML and XML. They are all implemented using XML Transformation so you are free to write your own XSL files.
Debugging XULadmin
There are 4 main ways how to debug XULadmin and they all contain info very helpful to the developers.
- XML exports (listings)
- To see the real data in listings, click the Export button and export the listing as XML. All columns, including the hidden ones, are exported.
- Firefox Error Console
- Select Tools -> Error Console from the Firefox file menu or press CTRL+SHIFT+J. An error console appears. XULadmin logs most of events to this console. If you suspect the ouput is insufficient, try increasing the log level.
- Close the running instance of Firefox. Open your Firefox profile directory and edit the file prefs.js. Edit the logLevel variable, increase the value to see some results. For now, using 1 is sufficient. This might change in the future and a highher number might be needed to see the output. This file is cached by Firefox so if you want to see the results, close Firefox while you are editing it.
- user_pref("extensions.cyclone3XULAdmin.preferences.logLevel", 0);
- SOAP Faults and Errors
- XULadmin uses the SOAP protocol to exchange data with the server. SOAP Errors are generated either by the server, telling you something valuable about the state of remote services (Access denied, Wrong username or password), or locally (Faults), which usually points to a network error or a protocol problem. (Unable to connect) SOAP Errors come with a hash so that it is possible to identify the operation in the server's logs.
- alert messages
- All internal Javascript code is trapped within try-catch statements. If something really serious happens an alert message pops out. This usually shouldn't happen so please notify the developers in this case.
