For awhile in that endless loops that happen within chronolabs we had an eric anonymous an SPC from the US defense turn up to test the miltary communication grade of XOOPS and its systems from my orintated waypoint on the keyboard.

We published some vugar crass iteration in no way reflective of the individual and associates and found in the news post like this one that is 2 weeks old there was only 11 hits from his regiment and commanding officers, I could only as a webmaster see the PhpMyAdmin index but the content was not in the impressions of my page view as this is in there guidelines a 'classified' tested for there own purposes.

This means XOOPS is the cake, it will only display data that is in pertanence to the command in a defence or miltary group and will obay the physical abstractions of there systems of governance and other depictions of communication and content management.

I would like to thank Eric for XOOPS'n me to the pizza box like that and welcome him to communcate as thust forth in any situation. Remember here at Chronolabs eric we salute you. In why programmer consoles are called a 'base' in that reference.

Today the domain chronolabs.org.au was renew to this local, as you can see it is in running for another 2 years, infact here is a little bit about the local process of renewal. The journey was like so, as we had to goto North Sydney anyway as we ended at this point with the NAT (10.0.0.1) - as per cisco's policies on where on the world is the NAT at the moment, we had to step into the internet cafe at there local main office (North Sydney).

So seeming it was beyond 10 days since sending www.mlc.com.au the form for 'financial hardship' we also made a call to them and discovered due to variences and cost and expenditure of light alone they could not see the JP stamp or signature on the org inal document mail closed to his location.

This involved meeting in what is not acting between business groups the directors and a member of the board, where in sound they have the ciggy not the durry that we where being hit up at a phone that doesn't work down the street.

I have been asked me to explore some of the older modules as a core developer, I have re-written the Content module so it falls in line with code standardisation as well as XOOPS Code protocol. It has been completely rewritten as well as a concession of other features added in. Now with the content module this has been renamed to X-Center as it is the center of your website. There is a new XML Power Block which will allow you to write and clone multiple blocks that scan other areas of your database for content in pertenance to the data in the article.

This means that you can have blocks in multiple places that are constantly changing based on various content types in the system, this off course with Search Engines the more you site expands and is used, mean you have a higher SEO rank cause your pages are reflecting a higher change in the system page impressions.

The X-Center is and will remain quiet popular as I have had many enquires about the content module so I have revamped it and released it to you.

Finally the wait is over!!! The XOOPS Development Team is pleased to announce the release of XOOPS 2.30 Final.

This is the most significant XOOPS release in years, as it merges the two existent branches of 2.0 and 2.2 and is building a bridge towards our next generation of system XOOPS 3.0.

With XOOPS 2.3 releases, users will be able to learn some of new features that will be available in XOOPS 3.0, while developers can understand better the direction of XOOPS development, and designers can learn what features will be supported in the future.

Both backward and forward compatibility are guaranteed as much as possible. Modules written for 2.0.* and 2.2.* will work with 2.3; applications developed for 2.3 will be compatible with XOOPS 3.0 automatically.

Developers are encouraged to write their application modules on XOOPS 2.3 so they can incorporate some of the new features and ensure easy migration to XOOPS 3.0.

This is a simple graphing system for system visits and usage, it will be extended further in the future but I hope you like this simple graph. You will need to add the block to the pages you want it to track the usage on.

With XOOPS Usage Graph you can follow the progress of your Xoops Usage with visits and click with this useful tool. This module requires the XOOPS Framework version of 1.35

This also tracks is integrity which should never drop below 100% unless you have some form of paranormal activities happening within your domain which in this graphs early stages of deployment we even noticed there was in our system.

This will display a graph over your selection of hours which will show you the user usage of your system. There is also multiple levels of Quarantine Tiers, you can expand this at your own means.