Wow, it's been two years since our last release!

Jinzora 2.7.5 was released on March 4 2007 and marked a milestone for Jinzora. It was supposed to be the last 2.x release and the start of Jinzora 3 development.

With over 5,000 downloads each month, Jinzora 2.7.5 is still a very popular release for everyone who is looking for a stable, mature and free web based media manager.

Unfortunately, a few small problems arised over time. We moved to a new server which rendered the integrated Jinzora lyrics and metadata retrieval services useless. The increased interest for Jinzora from countries with other character sets asked for better Unicode support, etc.

Since the new Jinzora 3 backend still needs a lot of work, we are not able to provide a Jinzora 3 release to solve these problems soon. Fortunately, Sören stood up and decided to come up with another Jinzora 2 release to address known bugs. As a result, the Jinzora Team is very proud to announce the immediate release of Jinzora 2.8!

Some major changes in this version include:

• Integration of Fred Hirsch's Custom Metadata Retriever to replace the non functioning Jinzora Metadata Retriever. This is the first user contributed OpenDevelopment Project that made it into a stable Jinzora release.
• Integration of the LyricWiki Lyrics Retriever by Jan Kleinhans to replace the broken Jinzora Lyrics Retriever. This is another OpenDevelopment Project that was contributed by a community member.
• Enhancements that make Jinzora fully UTF8-compatible.

For a full list of changes, please read the Jinzora 2.8 Changelog.

I'd like to thank everyone who contributed to this release in any way. Specifically Sören who coordinated development and Wim who lead the test team.

On behalf of the complete Jinzora Team,

We hope you like this new version! Comments and suggestions are welcome.

Hi everyone,

For the last week or so, several of our users were unable to post to the forums.

They received an error similar to "You cannot make another post so soon after your last" due to problems with our server clock.

We've implemented a temporarily solution that has the clock running at the right time now.

This should enable anyone to post again, while we're working on a more definite solution.

We are very sorry for the inconvenience and like to thank everyone who made us aware of the problem.