As it was advanced in a previous post, the list of tasks in the TODO for PhpReport 2.0 milestone was shrinking… now it’s finally complete, so I’ve made the 2.0 release available from PhpReport site.

This is the list of changes since the previous release, beta 2:

• Written user documentation, integrated in the application.
• Implemented a screen to create, edit and delete hour compensations.
• Implemented a screen to create, edit and delete cities.
• Implemented a screen to manage work calendars.
• Upgraded Ext JS framework to the latest version in 3.x series, 3.4.0.
• Reviewed permissions of the admin/user groups on some screens and services.
• Reordered the menu bar, deleting the unused entries.
• [Bug #131] Correct authorization problem related with project creation.
• [Bug #136] Fix size of template creation and delete buttons.
• [Bug #155] Prevent wrong calculation of project deviation.
• [Bug #161] Prevent blank project details screen due to a null end date.
• [Bug #168] Added holidays project to default installation.

You can see the latest version of the application in action in the public demo site, as usual [EDIT: demo site not available any more].

I’m just publishing this announcement but I already have my mind in the future, with more features, fixes and improvements. The first steps are written in the new TODO.

That’s all for now. Happy summer hacking!

It’s been a long time since the last post about this tool. It was the announcement of beta 2, and a lot of things have been done in the >50 patches committed since then. Let’s review and update the TODO file of the last release:

• Features:
  • Screen to manage cities and calendars DONE!
  • Screen to manage compensation of extra hours. DONE!
• Documentation:
  • Write the basic end-user documentation WORK IN PROGRESS

Besides, there are bug fixes and usability improvements. All these changes can be seen in action in the public demo site [EDIT: demo site not available any more].

As you can see, there’s little left to do to announce the final 2.0 release. But that won’t be the end of the road, but a milestone to take breath and keep coding.

I’ve been asked whether it was possible to install PhpReport in a Windows box or not, so I tried it and wrote the steps down in the INSTALL file. And now we have more concrete and precise installation instructions for Debian/Ubuntu, RedHat/Fedora or Windows systems, I felt like it was a good idea to package the application again, together with the bug fixes we pushed along the way. Take a look at the list of changes in the NEWS file.

Files can be downloaded here:

• Version 2.0 (Beta 2) ( .tar.gz ) ( .zip )

And they are also available in the project page.

Yesterday I silently added a link in PhpReport web page:

• Version 2.0 (Beta 1) ( .tar.gz )

Lately I’ve been working on the simplification of the installation process; now it’s not necessary to download external libraries or set any special php.ini parameters, and I’ve added a database setup wizard taken from PhpReport 1.x series, which in turn was based on the one from WordPress project. So now to install PhpReport, you only have to extract the tarball, create the database and open the installation wizard from a browser to let it create the tables and initial data. More work will be needed anyway, to set up other installation methods (.deb packages, for example) and write specific instructions for different operating systems or distributions.

And this is the beginning of a release process. I will try to release new versions as I implement new features, giving priority to those listed in the TODO file, and provide update paths between them (unlikely at the moment, but it could happen in the future). And now I’ve mentioned the TODO, it lists the changes I consider essential to release a final, stable 2.0 version. Any volunteers? 😀