Developer News: XOOPS 2.1.0 Development is on the road
Posted by: MithrandirOn 2005/4/9 10:03:57 12385 readsThe development of Xoops 2.1.0 has started and developers and other interested parties can follow the development as it progresses.
The goal of the development is to take on as many of the bugs reported on SourceForge as possible as well as adding new features and preparing the move to the next major version of XOOPS (Codenamed "XooSphere") so it has as little impact on current themes and modules as possible.
Anyone interested in the code can download a Nightly CVS build which is taken from the development branch in the XOOPS CVS repository.
NOTE: The nightly build is NOT in any way guaranteed to work - although we do aim at only committing working code. Fixing one bug or adding a feature in one place may result in other code malfunctioning and we cannot test all parts of the core for every addition. So while we hope for the nightly build to be installable and working, there may be inconveniences.
As the development progresses, the risk of getting a nightly build with major errors should diminish.
Read on for a more in-depth description of what is in the nightly build as of this moment.
Re: XOOPS 2.1.0 Development is on the road
. If the items I mentioned above have never been a problem, then why are you unable to set module and block caching for blocks/modules using them? For instance read counters for articles do not increment (immediately anyway) when module caching is enabled, admin only links appear to non admin users if the page is cached by someone with admin priviledges, and the main meny block shows menu items that the current user might not have permissions to depending on who was last to refresh the cache. I have a feeling I'm talking about apples when your talking oranges, but if these have not been a problem I wsa just wondering how you could go about setting up your XOOPS site so that these kind of items where never cached? 
