[kbeeveer46]

I'm not sure if this is going to work or not but I'm going to try and get a place going where people can just post nightly build bugs. The bug tracking system pligg uses on the trac won't work very well because Ash has to make an account one-by-one for everyone. So what I did is throw together Pligg bug tracking on Google code. The bad thing about this is that you need to have a gmail account and I'm not sure how many people do. If you have a gmail account and would like to post a bug report from any nightly build then here's where to:

http://code.google.com/p/pligg/

This is the first time the public has really had any input in bug tracking so we'll have to see how it goes. Remember, the better detailed you are the easier it will be for the developers to fix. Give me some feedback and what you think. This is not the official Pligg code repository or bug tracking, it's just being put together for nightly build bugs. Thanks.

If you don't want to get a gmail account then feel free to post all bugs in this thread. If you already posted them in the bug report that's fine, we didn't miss them.

[kbeeveer46]

Thanks to everyone who has posted a bug. Keep 'em coming.

[nickaster]

Out of curiosity, since I'm new to this bug tracking stuff - when the 210 bugs get fixed, then you have a new build called something else? Or does 210 periodically change?

So If I want to avoid any problems at the momment (the primary one being that i can't edid the language file from the admin panel) should i downgrade?

[kbeeveer46]

Since builds are changing so fast I decided to make it a general nightly build bug tracker. It's not speciifically for build 210 anymore. If you find any bugs in any of the nightly builds go ahead and use the link in the first post.

To answer your question, we went from build 210 to 215 in one day (today). Everytime a bug gets fixed or a feature gets added etc etc a new build is created. So one day there might not be anything done and others there could be 10 new builds in one day.