Following the beta testing period that was started a few weeks ago, pLog 1.0.1 has just been released. It includes many fixes for issues and problems that were found in the previous 1.0 release. Nobody likes releases with bugs but we are confident that we squashed most of them and that 1.0.1 is as stable as it gets. As usual, thanks to all of you who have submitted patches, discovered bugs, sent good feedback or just left a "good work!" message in the forums.

The release can be downloaded in a zipped package: plog-1.0.1.zip or in a tar.gz package: plog-1.0.1.tar.gz Please remember that there is no need to re-run the wizard.php installer when upgrading from 1.0 to 1.0.1. Just upload the files so that the old ones are overwritten and you are good to go.

Please use the forums for support requests and report any bug in our bug-tracking system.

Please read on for more details on which issues were fixed in this release.

The first maintenance release of pLog 1.0 is ready to be tested. pLog 1.0.1 fixes most of the issues that have been found in pLog 1.0 and also adds a few small new features. Even though 1.0.1 is looking much better than 1.0 and there should not be any major issues with it, we will still hold a beta testing round for about 2-3 weeks.

The current 1.0.1 development version is available from svn from the http://devel.plogworld.net/svn/plog/plog/branches/plog-1.0.1 folder (please see our instructions on how to access the pLog subversion repository) and packages are available in tar.gz or tar.bz2 format. Previous packages can be downloaded from the snapshots folder if interested.

Following the trend of pLog maintenance releases, there is no need to run the wizard.php script in order to upgrade your current installation from pLog 1.0 to pLog 1.0.1. Just download the package, unpack the files and upload them to your web server making sure that you are overwriting all of the old files. As soon as the process is complete, you will be running a pLog 1.0.1 installation.

In case you find any bugs or need to report something, please use the project's bug tracking system

For those interested in the issues that have already been addressed in this version, please read on.