A critical issue impacting XNova (all versions, including XG Project) have been detected and fixed, it allows an attacker to become administrator if the game. You will find a patch and an archive containing modified files for XNova:Legacies 2009.2, you need only one of both to fix the issue.

The bug fix could be foud on the XNova boards

Long time since the last announcement, however lots of things have been done.

The core sources of XNova:Next-Gen has been forked into an independent project, designed to bring standard high-level functionalities to various projects, such as User management, Backoffice, CMS functionalities or web applications skelettons. For now this development platform will mainly be used to replace the admin panel of XNova:Legacies and will in the end become its core.

This new project is named One.Platform, you will find a public git repository at Github. It includes the Core module, the User module, a native CMS pages manager and an administration site engine on which the future version is based. The reason why I decided to cut the project in 2 is that what have been done until now can be reused by another project.

Lire le reste de cet article »

This is it! XNova:Next-Gen is coming, its core module has been released as an alpha, which will enable new development approaches for XNova:Legacies (discussed here). This means that the architecture is frozen and further functionalities won’t be added since XNova:Legacies 2010-alpha0 won’t be released. Also, be aware that this is a developer release, there is no interface, and it should be considered as a high-level application framework on top of the Zend Framework, documentation will be availiable on the wiki.

Next to come, the user module, which will be the 2nd part of the XNova:Legacies 2010-alpha0 release.

You can now fetch the core module from the SVN trunk :
svn co svn+ssh://svn.xnova-ng.org/svnroot/xnlegacies/public/branches/modules/core/trunk

Or from the SVN tag :
svn co svn://svn.xnova-ng.org/svnroot/xnlegacies/public/branches/modules/core/tags/release-1.0-alpha0

Today I’m writing an entry for the the developers, an opportunity for me to introduce the new architecture for XNova:Legacies and explain its differences with what may have existed so far on the project. It is worth remembering that the biggest evolutions of the upcoming version comes from a brand new source code written in PHP 5.2, this version becomes though a dependency to make XNova:Legacies work on your system, but don’t worry, this PHP verison exists since 2006 and is therefore widely deployed on PHP hosting providers since a long time.

To return to what we are all here, everything has been redesigned to facilitate simple and rapid modification of the functionnalities of the game without the need of applying neither 1 line of the original source code. Everything is built upon the configuration, if a functionality in the base source code does not work like you wanted : replace it! it is as simple as that.

Accessing to data from the database has never been as simple and safe Lire le reste de cet article »

Hi folks, it’s time to announce the coming of the new version 2010.1 of XNova:Legacies, which brings major changes in the sources : It includes parts of the Zend Framework 1.9.6.

This version will include an object-oriented data access API coming from XNova:Next-Gen, making the doquery() function deprecated – it will therefore be deleted little by little from the sources in future versions. As a matter of fact, multiple connections to the database can now be set up, using various database engines, this will be useful for a future migration from the deprecated ext/mysql database connector to either ext/pdo_mysql or ext/mysqli connectors.

Some other interesting changes for game administrators are the refactoring of the file “include/vars.php“, which will now be much more human-readable and the ability to easily display debug and deprecation messages.

For a long time, this version has been announced as the version 2009.3, some have made some remarks and as long as there are a lot of core changes, changing the main version number may be a good idea, then.

As like the 2009.1, there will be multiple releases before a “stable” version comes, a debug server will be launched very soon to launch some “Bug Hunt Days” and find more bugs, more bottlenecks to fix in early releases.