OK, so I snuck beta7 up to Launchpad on the weekend. I couldn't get the XAMPP version to upload. It would go to about 85% then timeout
There's only one DB change so this one should be quite smooth.
There's a few additions. I haven't finished "other" items yet - but they should be safe enough to use. Just bear in mind that this will change, so don't rely on it too much. Just play with it
You can access the application via POST and GET now. username and password are the magic variables. Example GET request [code]http://localhost/index.php/report/8/8/username/YOURUSERNAME/password/YOURPASSWORD[/code] If you're nervous about putting your credentials in the URL, use HTTPS. I tested the POST items using WGET. Seemed to work fine for me.
RSS feeds are capable using the URL format above (use your username + password) and put /rss on the end of the URL. They will only work on Reports that have timestamps as a column. A button will appear on suitable reports next to the other "export" type buttons.
You can export to JSON the same as XML, HTML, CSV, etc, etc - just make /json the final item of the URL.
If you're an Admin in the application, you have a small button (near the Logout button) for Debug. It will turn on the CodeIgniter debug items. They will appear at the bottom of the page.
I've altered every model PHP file to make sure they're all consistent in terms of code format. Stuff like opening bracket position, etc, etc - boring stuff really but it makes the code consistent and readable.
Any Locations now have the option to create a Group based on it. Check the Admin -> Locations -> List Locations page. Organisations work the same (they were done for beta6).
I've changed the view PHP file for v_system_display to v_display_system. I'll be creating a view per "type" of item in the DB. I have currently done "printers", but this will change. I plan to create a few default views, but I plan to store the definitions for a particular type of system in the DB and dynamically create the view based on that. Hence what I mentioned above - don't rely on "other" items like your life depends on it at this stage... they will change.
If you have SNMP enabled in your PHP installation, when you submit an audit with details of a network printer, the processing PHP page will query the network printer for it's manufacturer, model and serial. This is new and experimental, but seems to work OK. It will only do this for new printers. Personally, I just deleted our 450 or so network printers and let it run again. There may be time-out issues in the VBScript. If so, please advise. I've already had to alter my script time-out because our print servers contain over a hundred printers each. If you have trouble, just post. It uses a community read string of "public" and uses SNMP v2. Because of those basic things it won't retrieve every detail perfectly. Printers have v1, v2c and v3 SNMP, they store items in different locations, in different formats (STRING and HEX) or not at all. SNMP is a pain. I do plan to expand upon the SNMP functionality though - first with colour and duplex capability, then for other items (think anything else with SNMP).
There's an option in audit_windows.vbs to attempt to ping a system before an audit is attempted. It is turned off by default, but works fine. It requires Windows XP and above to run but will not attempt to run if you do use Win 2000.
I'll add anything else I've done in here (am sure there's other bits I've neglected to mention).
Grab it from here - [url]https://launchpad.net/oav2/trunk/beta7[/url]
Any feedback appreciated.
Mark.