I’ve been quietly hacking away at my local videoDB installation and added some wonderful new features to the elegant template. All changes have now been committed to CVS and are available for testing.
Our site has lately been subject to misuse.
Especially the demo installation has been abused to place spam. In fact, about every 5 to 10 seconds, a new spam entry has been created in the database. I’ve taken measures to prevent this and hope the demo system is usable again. Please report any new problems here.
Finally, after over a year of development, videoDB 3.0 has finally been released. New feature and improved functionality include:
To grab your copy, please visit our SourceForge projcet site:
If you want to support videoDB, you can nominate it for the SourceForge Community Choice Award. To participate (category Multimedia?), see here:
Thank to all you for your support!
Just released 3.0b5.
Main changes are bugfix of user cookie error when public access was disabled and removal of Amazon ECS (amazonxml) engine. Amazon has discontinued this service. Potential replacement could be the new A2S- plugin is under development.
After upgrading demo site to PHP5, the youTube search is now publicly available for testing. To evaluate, drill down to a single movie and click the “Show trailers” link.
Upgraded videoDB demo to current CVS version. Contains new multi-user code that should fix some of the open issues. Generally, we should see some performance increases and more secure, better maintainable code.
Demo no longer requires login but can now be accessed as anonymous user.
To see all the latest features, make sure you’re using the “elegant” template. Currently “elegant” is the only ajax-enabled tempalte providing all functionality.
videoDB v3.0 beta 3 has just been released.
This beta contains ajax enhancements (image zoom) and partial rewrite of the multiuser permissions systems- this was necessary as the old code contained various bugs and ambiguities. Rewrite also allowed drastic decrease in number of SQL queries which should improve performance in hosting environments.
I’ve investigated using ProtoFlow for the next version of videoDB. Initial results look _very_ promising: