[ INFO ] vBulletin Status

[Ordovicium]

Vielleicht gibt das einigen Leuten die Antwort, wie lange wir noch im Beta Stadium sein werden:


Here is the current update of the vBulletin 3 Development.

The conversion of the administration control panel to register global compliance has now been completed and the beta testers have commenced finding any problems with that. The documentation project is also proceeding well.

vB3 Bugs
Total fixed bugs: 110
Total unresolved Bugs: 9

Current Unresolved Bugs Large table scans on the post table RSS feed problems with multibyte languages List parser crashingCurrently Active Tasks Using a JavaScript method to detect DST is currently in the implementation stage Phrasing of the administration control panel is about to proceed The majority of functions removed from templates and placed into the code Using a code standard to define the function names Replace Contact Us with a form to prevent bots harvesting emails

[Ordovicium]

Here is the current update of the vBulletin 3 Development.

The past two weeks have focused greatly on the syntax that exists throughout the entire code. In an attempt to homogonize code that has filtered down from vB1 and vB2 we have created a new function-naming system in order to make the code more immediately accessible. So far, around 330 functions of 606 have been renamed to use the new schema. We estimate that this process will be complete in the next couple of days.

Additionally, we have been removing redundant code used to support older versions of PHP (older than 4.0.6). SQL query formatting is also being standardized, mostly by splitting individual SQL clauses onto separate lines for better readability.

vB3 Bugs
Total fixed bugs: 131
Total unresolved bugs: 5

Current Unresolved Bugs Locking issues on last post in member profile Buddy list error when parent window is closed DST JavaScriptCurrently Active Tasks Function renaming, currently 55% complete SQL Syntax Code Cleanup Admin Control Panel rephrasingNew Features / Improvements
Note: Both of these changes are the result of bugs being resolved, rather than an active effort to add new features. Threads that do not contain polls now contain a link at the bottom of the posts list that allows users with permission to create polls to add a poll to that thread. Attempting to post a duplicate thread now results in an error message, and the user being sent back to the forumdisplay listing. This has been done because on large boards with slower processors a queue of thread insert queries can build up, which in turn causes the duplicate thread check to fail. A completely new system has been implemented and all problems with duplicate threads should now be resolved.

[Ordovicium]

Here is your fortnightly insight into what is happening with vBulletin 3 Development.

Over the past two weeks attention has been focused squarely on ironing out any remaining bugs, and tidying up the code and back-end systems in preparation for the imminent public beta release.

Function name homogenization is now complete. The changes were made with a tool I wrote which allows the developers to associate an existing function name with its new name, which complies with the newly-established function naming rules. All that remains to do for this process is to run the batch script included in the tool which will replace the old function names in the PHP scripts themselves. This should happen in the next couple of days.

Another major effort in process at the moment is the rationalization of the language system. The vast majority of text in vBulletin is now in the language system but there is a lot of phrase duplication (ie: multiple phrases that say edit etc.) so we are currently going through the phrases making sure that we don't have any overly verbose phrases, and combining separate phrases into a single phrase wherever possible (such as Edit This Forum and Edit Forum being merged into Edit Forum).

Currently Unresolved Bugs Table locking issues on last post in member profile (solutions being discussed) DST Javascript (solution being implemented)Currently Active Tasks Function renaming (90% complete) Language/Phrase rationalization

[Ordovicium]

Here is your fortnightly insight into what is happening with vBulletin 3 Development.

There are now no bugs to be addressed in the vB3 Private Beta Bugs Forum, we have been working hard to insure that any identified are immediately solved to try and keep this forum empty.

Recently Completed Tasks DST auto detection using JavaScript Reorganisation of AdminCP navigation Install Script (still requires testing) Remaining function renaming issuesCurrently Active Tasks Language/Phrase rationalizationRemaining Bugs What is left in the Public Bugs Forum

[Ordovicium]

I find myself with a few moments to spare, so I thought I'd just write a quick update on progress with vB3.

This has been a very busy week, in which Freddie, Scott and I have all put in some very long hours towards what I consider to be the final sprint for the finish line in the race to get vB3 into the hands of you, the customer. As an added bonus, long time vB developer Mike 'Ed' Sullivan (http://www.vbulletin.com/forum/member.php?userid=37), who has been absent from the development team for several months, approached me this week about coming back and doing some more work for Jelsoft, and of course I was happy to oblige.

The last remaining task before we can release vBulletin 3.0.0 Beta 3 to the public is to get the language system into shape. While the back end of the language system has been in place for a long time now, a lot of the text that you see in the control panel and the front end interface is still hard-coded into the PHP and the templates. We are now working feverishly to get all hard-coded text into the language system, and to improve on previously defined phrases.

With an application the size of vBulletin 3, especially considering the huge control panel, there is an awful lot of text to manage so the methodology behind putting all that text into phrases is critical. If we were lazy and wanted to get the task done in the shortest possible time, we would simply create a unique phrase for every single text element in vBulletin. However, this would result in an extortionate number of phrases, which would be a nightmare for people to translate. Rather, what we are doing is identifying text elements that can be re-used and rewriting a lot of the text to be less verbose.

For example, we could create the following phrases as unique entities: Modify this forum Edit this post Change your avatar Alter this eventRather, we simply create a phrase that can be passed through our phrase parser in order to create Edit Forum, Edit Post, Edit Avatar and Edit Event, using separate phrases for Forum, Post, Avatar and Event, as those can be used elsewhere in other phrases.

Using this approach, it is important to find a balance between putting enough description into the text to make its function intuitive, and making the text so terse that although we have a small number of phrases this is to the detriment of the ease of use of the system.

In order to do this, I created a set of tools in order to make sure that text is re-used wherever possible and that new phrases are not created when it's not specifically necessary. Meanwhile, Freddie wrote an extension to the tools to allow us to check the scripts for text and verify that all text has been successfully put into the language system.

http://www.buffalomuff.com/bbsimg/phrasedev/phrasedev1.png

http://www.buffalomuff.com/bbsimg/phrasedev/phrasedev2.png

As far as I can see, the vast majority of the control panel text is now complete, so that's the biggest hurdle overcome. Now we need to decide if we are going to give the front-end interface the same treatment before we release the public beta, or wait until the new templates are complete so as to avoid creating new phrases unneccessarily.

I think this will be the last status update before we release the public beta, barring unforseen problems. In the meantime, look out for a patch to vBulletin 2.3.0 in order to fix a problem that seems to have been introduced with MySQL 4.0.13. We will release this patch some time next week.

[Ordovicium]

Soda, wir haben nur beta3 Status erreicht, und somit ist vB kein privater Betatest mehr. Das neue Layout konnte aufgrund des Zeitdrucks noch nicht geliefert werden, wird aber bei der Final Version (max. in 3 Wochen) vorhanden sein.

mfg
Ordovicium