phpBB
Statistics
| Revision:
This repository is a mirror of the phpBB Git repository which is located at http://github.com/phpbb/phpbb3

Checking out phpBB from the subversion repository

In order to download the latest code from this project you need a subversion client. The URL for this repository is http://code.phpbb.com/svn/phpbb/. You will probably want to checkout the 3.0.x branch directory which contains the latest stable code using svn checkout http://code.phpbb.com/svn/phpbb/branches/phpBB-3_0_0/phpBB.

Please note that the trunk directory contains unfinished and unstable code. We highly recommend not using it, unless you know what you are doing. The code in trunk will not work most of the time.

If you want to learn more about how to use subversion then you should take a look at the Subversion Book which covers every part of subversion in great detail.

Repository (Subversion)

root / tags / release_3_0_0

Name Size Revision Age Author Comment
  phpBB 8278 about 4 years Meik Sievertsen clear the float to fix a display problem in fir...

Latest revisions

# Date Author Comment
8279 12/12/2007 05:46 pm

This commit was manufactured by cvs2svn to create tag
'release_3_0_0'.
8278 12/12/2007 05:46 pm Meik Sievertsen

clear the float to fix a display problem in firefox
8277 12/12/2007 05:45 pm Meik Sievertsen

- change adm/index,php, acp_attachments.html and acp_ban.html to be triggered by the next update
8276 12/12/2007 05:18 pm Meik Sievertsen

seems like there is an error within the udpater, skipping the first file changed. This is not good(tm). For Gold, we will provide update packages for going from RC7 -> gold and RC8 -> gold.
8275 12/12/2007 12:07 pm Meik Sievertsen

wrong call - utf8_clean_string() instead of utf_clean_string() :)
8274 12/12/2007 11:54 am Meik Sievertsen

and the final version number ;)
8273 12/10/2007 07:35 pm Henry Sudhof

Late fix for #16174
8272 12/06/2007 10:38 pm Meik Sievertsen
  • empty log message ***
8271 12/06/2007 01:27 pm Meik Sievertsen

commit all transactions on closing the db (there is only one, but we support inner transactions - logically speaking)
8270 12/06/2007 09:55 am Meik Sievertsen

- on database update, execute garbage_collection(). This ensures a proper closed db and written cache
- on sql errors returning (and not triggering an error) execute the rollback too

both "bugs" resulted in transactions left open if a query returned an error on database update preventing a clean update. Symptoms being for example oracle users not having all database info updated, the version number not changing or config variables not written.

View revisions

Also available in: Atom