-
phpBB moves source code versioning from Subversion to Git
Hello,
The phpBB development team would like to inform our users of a major change concerning the development infrastructure of phpBB. As you may well know phpBB has used Subversion for version control since January 2008, at that time we moved away from CVS which had been used since the project started. Effective from 1st March Subversion is no longer being used as the version control system of phpBB itself, we are now using Git with the main repository being hosted on GitHub.
This change doesn't concern end users who currently do not follow development, but users who use our Subversion repository need to be aware of these changes.
The development team had been looking at moving to a distributed version control system for a number of months, out of the candidates Git has always been the forerunner and we feel it has the best community and support to meet our needs for the coming years. Using a distributed version control system allows for greater community coding participation, meaning people outside the development team can easily develop their ideas for phpBB and contribute them back with greater ease.
Now we are aware Git has a steep learning curve, one which we are dealing with ourselves. One thing going for Subversion was that it is incredibly simple to use, as such we provide a read-only Subversion mirror of the phpBB repository for those of you who use Subversion for managing your sites and MODs. The Subversion URL has not been changed, all commits are now forwarded from Git. To facilitate the learning of this new version control system, and ensure the developers don't do anything daft, we have a number of Git related resources on our wiki. Git We are looking forward to your contributions!
Finally, we'd like to thank David Soria Parra for his assistance during the migration and continued support with all Git related queries.
-
Support Toolkit 1.0.0-PL1 released
Hi,
Due to the release of phpBB 3.0.7-PL1, we're releasing a small update for the Support Toolkit. This release will make sure that the database cleaner included in the STK will work correctly on a phpBB 3.0.7-pl1 installation.
Update notes:
When updating from 1.0.0 please make sure that you delete the old STK folder from your server before uploading the new version.
If you are unfamiliar with the toolkit, please see the Support Toolkit page.
As always, assistance with installation, updating or any of the tools provided with the Toolkit is available in the Support Forum. Please submit any bugs/suggestions to the Support Team Tools bugtracker.
Thank you, and enjoy.
The phpBB Team
---
You may discuss this announcement in the [Discuss] Support Toolkit 1.0.0-pl1 released topic.
-
phpBB 3.0.7-PL1 released
Hi everyone,
We are sorry to announce the immediate release of phpBB 3.0.7-PL1 to address a security issue which was introduced in 3.0.7, unfortunately the issue wasn't noticed during testing and has only surfaced a week after the release of 3.0.7.
We promised working feeds for phpBB 3.0.7. Sadly, we were not able to deliver on that promise - a critical bug in the permission handling for feeds slipped past. To all people who already have updated to 3.0.7, it is of critical importance to update to 3.0.7-PL1. Otherwise, it is possible for users to bypass permission settings under the following circumstances:
- Feeds are enabled
- Any of the posts or topics feeds are enabled
- The unauthorised user - or one of the groups they are a member of - have forum permissions set on a private forum
- If you have excluded a forum from the list of forums that provide feeds, it is unaffected
Note: We recommend the use of a regular update routine over manually editing your files. If you manually edit your files your board will not recognise the update.
The fix for the issue is a single line change inside of feed.php, line 525 has changed from:
- Code: Select all
$forum_ids = array_keys($auth->acl_getf('f_read'));
to:
- Code: Select all
$forum_ids = array_keys($auth->acl_getf('f_read', true));
There were no other changes, in particular neither style nor language changes.
Installation instructions
A short explanation of how to do a conversion, installation or update is included within the provided INSTALL.html file, please be sure to read it. You can find a list of requirements on our Downloads page.
Security
If you find any security issues please report them to our security tracker.
Available packages
If you experience problems with the automatic update (white screens, timeouts, etc.) we recommend using the "changed files only" or "patch" method for updating.
- Full Package:
Full phpBB 3 source code and english language files. - Automatic Update Package:
Update package for the automatic updater, contains changes from previous release to this release. - Changed Files Only:
Complete files, but only those that were changed since previous releases of phpBB 3. This archive contains changed files for every previous release. - Patch Files:
This file contains diffs against the previous phpBB 3 release, which can be applied with the patch utility.
Select the package most suitable for you. We recommend the following methods depending on your situation:
- For new installations you should use the Full Package
- For updates of boards without modifications you can use the Automatic Update Package (guided update) or the Changed Files Only package (manual update).
- For updates of boards with modifications you should use the Automatic Update Package. If you are confident with patch files and patching you can use the Patch Files Package.
- International Support Teams may use the Patch Package in conjunction with the Code Changes to better support users with problematic conflicts during their update process or to help them update code sections.
- If you are a hoster/provider, you may want to use the Patch Files Package to update all of your client installations.
Please ensure you read the INSTALL and README documents in docs/ before proceeding with installation, updates or conversions!
Download Locations
The download is of course available on our downloads page.
Our release archive provides all packages we build. If you do not find your desired package you can probably find it in the release archive.
These are the files with their md5 sums:
phpBB-3.0.7-PL1.zip (Full Package)
md5sum: 1125b615e13a5bb8787afab58a27c627
phpBB-3.0.7-PL1.tar.bz2 (Full Package)
md5sum: 67570654462c442c29080007c0af1e1b
phpBB-3.0.7-PL1-patch.zip (Patch Files)
md5sum: 44d163c6f945207f666b4b8ecbf179b8
phpBB-3.0.7-PL1-patch.tar.bz2 (Patch Files)
md5sum: 4d611e1160599835ff48fc6454bf85e0
phpBB-3.0.7-PL1-files.zip (Changed Files)
md5sum: 579f5685cc37c69dd6ce023b46ce2593
phpBB-3.0.7-PL1-files.tar.bz2 (Changed Files)
md5sum: 2779984411598d919a6a1e6adc35894d
phpBB-3.0.7_to_3.0.7-PL1.zip (Automatic Update Package from 3.0.7)
md5sum: e135fd3b43c17c0bdc69f3fc246e6524
phpBB-3.0.7_to_3.0.7-PL1.tar.bz2 (Automatic Update Package from 3.0.7)
md5sum: 589d21934c14a6517583316659f0225f
phpBB-3.0.6_to_3.0.7-PL1.zip (Automatic Update Package from 3.0.6)
md5sum: b93e31c7930ace5af89d9804b55d8c66
phpBB-3.0.6_to_3.0.7-PL1.tar.bz2 (Automatic Update Package from 3.0.6)
md5sum: cf9b3a42872be8afcddb42648a390861
Download & Documentation
-
MODX 1.2.5 Released
We are proud to announce the release of the 1.2.5 version of MODX.
This version adds several optional parameters in MODX and some minor bug fixes.
MODX is the format used for distributing modifications, therefore this announcement is primarily aimed at MOD authors. We will require all modifications submitted after this announcement to use MODX 1.2.5.
How to get it
As always, you can obtain the latest version of MODX at the MODX Resource Centre. Additional information and files can be found there too.
MODX Creator has been updated to MODX 1.2.5.
Required changes
Luckily for MOD authors, this release of MODX is almost fully backwards compatible.
If your install file contains the link attribute php-installer you need to replace that with the new php-installer tag.
Those of you that did not have time yet to use that attribute only need to include the revised XSL file and change this:
- Code: Select all
With this:
- Code: Select all
Full changelog
- [FIX] Removed php-installer as link attribute and added it as a tag in the actions group.
- [FEATURE] Added delete tag group for deleting files and directories.
- [FEATURE] Added link to the ISP page at phpbb.com.
- [FEATURE] Added and to the action group.
Development
Development of MODX and tools related to it takes place at the code forge. There is an SVN repository there for those who would like to follow the development.
Bugs
If you encounter any problems, we'd highly appreciate it if you reported them to the MOD Team Tools bug tracker.
The Modifications Team
-
Support Toolkit 1.0.0 released
We are proud to announce the availability of the first stable release of the Support Toolkit. This release fixes a number of bugs and contains two changes in the feature set.
Update notes:
When updating from RC3 please make sure that you delete the old STK folder from your server before uploading the new version.
feature set changes:
- The STK now ships with a tool that allows you to repopulate the moderators cache table.
- Due to large memory issues the "URL List tool" has been removed from the STK.
Full changelog:
- [Fix] Corrected some language related issues. (Bug #53725, #53835, #53845, #56865, #57815)
- [Fix] Display the correct "old" version number when triggering the outdated message after a STK update due to cached information.
- [Fix] Allow the use of a non default language pack. (Bug #54785)
- [Fix] Database cleaner removes non phpBB related tables. (Bug #55355)
- [Fix] Users added to the "Newly Registered Users Group" won't be automatically removed. (Bug #55695)
- [Fix] STK shouldn't remove "old" config entries for backwards compatibility. (Bug #55375)
- [Fix] Database cleaner removes feed related items from the database. (Bug #54765)
- [Fix] Reparse BBCode empties some posts. (Bug #55765, patch by D¡cky)
- [Fix] Database cleaner removes the Q/A captcha tables. (Bug #56605)
- [Fix] Correct error when attempting to remove groups. (Bug #56065)
- [Fix] SQL error on attempting to replace previously removed default bots. (Bug #56065)
- [Fix] Rename user_group section to usergroup to avoid triggering mod_security. (Bug #48225)
- [Fix] Select the "registered users" group as default in the Add user tool.
- [Fix] Reparse BBCode encodes some previously encoded entities. (Bug #56885, patch by D¡cky)
- [Fix] "Database Cleaner" doesn't work with PostgreSQL. (Bug #56565, patch by we3b)
- [Fix] Reparse BBCode does not properly handle UTF8 on PHP4. (Bug #56885, patch by D¡cky)
- [Fix] Reparse BBCode breaks link between posts and atachments. (Bug #57325)
- [Fix] Multiple runs of the BBCode reparser would break posts. (Bug #57245)
- [Fix] BBCode sets all topic first posters to "Guest".
If you are unfamiliar with the toolkit, please see the Support Toolkit page.
As always, assistance with installation, updating or any of the tools provided with the Toolkit is available in the Support Forum. Please submit any bugs/suggestions to the Support Team Tools bugtracker.
Thank you, and enjoy.
The phpBB Team
You may discuss this announcement in the [Discuss] Support Toolkit 1.0.0 released topic.
-
MODX 1.2.4 Released
We are proud to announce the release of the 1.2.4 version of MODX.
This is mainly a maintenance release for MODX. It only adds two optional parameters in MODX and bug fixes.
MODX is the format used for distributing modifications, therefore this announcement is primarily aimed at MOD authors. We will require all modifications submitted after this announcement to use MODX 1.2.4.
How to get it
As always, you can obtain the latest version of MODX at the MODX Resource Centre. Additional information and files can be found there too.
MODX Creator has been updated to MODX 1.2.4.
Required changes
Luckily for MOD authors, this release of MODX is fully backwards compatible. In addition to including the revised XSL file, the only change required to your modification is replacing this:
- Code: Select all
With this:
- Code: Select all
Full changelog
- [FIX] Altered the urging to backup files before installing a MOD to also include the database. Bug #52545
- [FIX] Now MODX should support all chars in links, even using Opera. Bug #52575
- [FIX] All links are translated. Bug #52135
- [CHANGE] Color coded add-after, add-before, replace with and operation. Grey, grey, grey and grey.
- [CHANGE] Changed text Increment to Operation.
- [CHANGE] Removed "For help on what each operator means, click here." from the language since there was no link to click.
- [FEATURE] Added attribute text to the link tag for text files. Bug #55275
- [FEATURE] Added attribute php-installer to the link tag. For php install files. Used by AutoMOD.
- [FEATURE] Added attribute uninstall to the link tag. For uninstall instructions.
Development
Development of MODX and tools related to it takes place at the code forge. There is an SVN repository there for those who would like to follow the development.
Bugs
If you encounter any problems, we'd highly appreciate it if you reported them to the MOD Team Tools bug tracker.
The Modifications Team
-
phpBB 3.0.7 released
Hello everyone,
We are pleased to announce the release of phpBB "Run bugs, run! Bertie is coming!" 3.0.7. This new version is a maintenance release fixing a number of a bugs as well as improving on usability and performance. We have entirely overhauled the Feed feature, fixing a lot of bugs and odd behaviours. Some problems with the automated updater have been solved, so if you are still on 3.0.5 this update should work a lot better for you.
We urge you to update your installation as soon as possible. The bugs fixed in phpBB 3.0.7 ensure the smooth operation of your board. Our support team will only support phpBB 3.0.7, updates to phpBB 3.0.7 and conversions to phpBB 3.0.7. Submissions to our trackers for older versions will not be accepted, please make sure you update before you submit a bug report.
If you use a language pack other than the default "English [GB]", you should check our downloads section, an update may already be available.
For a complete list of changes with attributed ticket numbers, please consult our comprehensive changelog. Below I have extracted the most important changes in phpBB 3.0.7.
Minor feature additions to phpBB 3.0.7
- You can now see private forums in your ATOM feeds using HTTP authentication by passing the GET parameter "auth=http".
- The INTTEXT token was added to custom BBCodes to allow for non-ASCII letters in html attributes.
- You can now enable quick reply in all forums with a single click.
Small functionality changes in phpBB 3.0.7
- Warn users about potentially dangerous BBcodes.
- Forum feed no longer includes posts of subforums.
- Speed up topic move operation by adding an index for topic_id on the topics track table. (Bug #56545)
- Move redirect into a hidden field to avoid issues with mod_security. (Bug #54145)
- Log user activations through inactive users ACP. (Bug #30145)
- Alter ACP user quick tools interface to reduce confusion with the delete operation.
- Show a proper preview for the Q&A CAPTCHA. (Bug #56365)
- Send time of last item instead of current time in ATOM Feeds. (Bug #53305)
- Split "All topics" feed into "New Topics" and "Active Topics" feeds.
- It is no longer possible to persist a solution for the login CAPTCHA.
- Friends and foes will not show up as private message rule options if their respective UCP modules are disabled. (Bug #51155)
- Offer for guests to log in for egosearch and unreadposts search before the search permissions check. (Bug #51585)
A list of important bugfixes since phpBB 3.0.6
- Allow ban reason and length to be selected and copied in ACP and subsilver2 MCP. (Bug #51095)
- Correctly set last modified headers. (Bug #54245, thanks Paul.J.Murphy)
- Make word censoring case insensitive. (Bug #54265)
- Fulltext-MySQL search for keywords and username at the same time. (Bug #54325)
- Various XHTML and CSS mistakes in prosilver and subsilver2. (Bugs #54705, #55895, #57505, #57875 - Patch by HardStyle)
- Cleanly handle forum/topic not found in ATOM Feeds. (Bug #54295)
- PHP 5.3 compatibility: Check if function dl() exists before calling it. (Bug #54665)
- PHP 5.3 compatibility: Disable E_DEPRECATED on startup to keep set_magic_quotes_runtime(0) quiet. (Bug #54495)
- Correctly replace table prefix before inserting schema data into the database. (Bug #54815)
- Use memcache::replace() instead of memcache::set() for existing keys to prevent problems.
- Check for required functions in eAccelerator. (Bug #54465)
- Use correct RFC 3339 date format in ATOM feed. (Bug #55005)
- Do not deliver topics from unreadable or passworded forums in the news feed. (Bug #54345)
- Restore user language choice to compiled stylesheets. (Bug #54035)
- Do not permit unauthorised users to delete private messages from folder listing. (Bug #54355)
- Handle export of private messages where all recipients were deleted. (Bug #50985)
- Add ability to disable overall (aka board-wide) feed.
- Do not pass new_link parameter when creating a persistent connection with mysql. (Bug #55785)
- Improved search query performance through sorting words by their occurance. (Bug #21555)
- Strictly check whether a moderator can post in the destination forum when moving topic. (Bug #56255)
- Do not unsubscribe users from topics replying with quickreply. (Bug #56235)
- Don't submit when pressing enter on preview button. (Bug #54395)
- Load reCAPTCHA over https when using a secure connection to the board. (Bug #55755)
- Don't send activation email when user tries to change email without permission. (Bug #56335 - Fix by nrohler)
- Correctly orientate quoted text image on RTL languages. (Bug #33745)
- Fall back to default language email template if specified file does not exist. (Bug #35595)
- Database updater now separates ADD COLUMN from SET NOT NULL and SET DEFAULT, when using PostgreSQL <= 7.4 (Bug #54435)
- Styles adjustment to correctly display an order of rtl/ltr mixed content. (Bugs #55485, #55545)
- Do not store email templates in database. (Bug #54505)
- Fix problems with firebird by no longer using 'count' as a column alias. (Bug #57455)
- Make user_email_hash() function independent from system's architecture. (Bug #57755)
- Global announcements could not be accessed on a board using Firebird as the database server. (Bug #57525)
- Do not delete unrelated attachments when deleting empty forums. (Bug #57375)
- Update process: Store expected resulting file contents in cache and do not suggest further merges if the contents match, also fixes infinite merge loop (Bug #54075)
Installation instructions
A short explanation of how to do a conversion, installation or update is included within the provided INSTALL.html file, please be sure to read it. You can find a list of requirements on our Downloads page.
Security
If you find any security issues please report them to our security tracker.
Available packages
If you experience problems with the automatic update (white screens, timeouts, etc.) we recommend using the "changed files only" or "patch" method for updating.
- Full Package:
Full phpBB 3 source code and english language files. - Automatic Update Package:
Update package for the automatic updater, contains changes from previous release to this release. - Changed Files Only:
Complete files, but only those that were changed since previous releases of phpBB 3. This archive contains changed files for every previous release. - Patch Files:
This file contains diffs against the previous phpBB 3 release, which can be applied with the patch utility. - Code Changes Package:
This package contains MOD instructions for changes to the following sections: Language changes, prosilver style changes and subsilver2 style changes.
Select the package most suitable for you. We recommend the following methods depending on your situation:
- For new installations you should use the Full Package
- For updates of boards without modifications you can use the Automatic Update Package (guided update) or the Changed Files Only package (manual update).
- For updates of boards with modifications you should use the Automatic Update Package. If you are confident with patch files and patching you can use the Patch Files Package.
- Style Authors and Translators may use the Code Changes Package to update their styles or language packs.
- International Support Teams may use the Patch Package in conjunction with the Code Changes to better support users with problematic conflicts during their update process or to help them update code sections.
- If you are a hoster/provider, you may want to use the Patch Files Package to update all of your client installations.
Please ensure you read the INSTALL and README documents in docs/ before proceeding with installation, updates or conversions!
Download Locations
The download is of course available on our downloads page.
Our release archive provides all packages we build. If you do not find your desired package you can probably find it in the release archive.
These are the files with their md5 sums:
phpBB-3.0.7.zip
md5sum: 034c556a436a1f7a3905c1dcd1271564
phpBB-3.0.7.tar.bz2
md5sum: a0a9b0eb3fd00267fea71b9938f9f989
phpBB-3.0.7-patch.zip
md5sum: 7d0bd2ac68f5da7c082f8f39bf10fced
phpBB-3.0.7-patch.tar.bz2
md5sum: 4ef0b9c58d022755d1e5c9b08f1ba593
phpBB-3.0.7-files.zip
md5sum: 43b0291fc649c62c8aa4c963355d414b
phpBB-3.0.7-files.tar.bz2
md5sum: 327e017dee7678e0bc1033a4f99d2e21
phpBB-3.0.6_to_3.0.7.zip
md5sum: 45bdc622489809f576f094a35ab27e80
phpBB-3.0.6_to_3.0.7.tar.bz2
md5sum: 507ab687f8ff35b68ce42e689337e26a
phpBB-3.0.6_to_3.0.7-codechanges.zip
md5sum: 346e5e098cdf1a8d503917413b8c5cb6
phpBB-3.0.6_to_3.0.7-codechanges.tar.bz2
md5sum: 5be3dd31a6dda10778ba05cda40bd2c2
Download & Documentation
we hope your update or installation is quick and easy,
the phpBB Team
-
DavidIQ is now the Permanent MOD Team Leader
DavidIQ will now be the permanent leader of the Modifications Team. I, wGEric, led the team temporarily during the transition period after evil<3 stepped down and helped David ease into the position. It is now time for me to step back and give David the reins.
David is very involved with MODs and very enthusiastic about phpBB. We believe that he will be a great leader while leading the MOD Team into the future of phpBB. Many MOD authors have probably had some interaction with him already since he has been a master at validating MODs that have been submitted to our database.
Everyone join me in congratulating David on his promotion.
-
Change in MOD Team Leadership
After being on the MOD Team for 2.5 years Igor Wiedler (evil<3) has decided to leave phpBB for personal reasons. While leading the Modifications Team for past year he oversaw the release of many tools including AutoMOD an automatic MOD installer, UMIL an framework for database install scripts, an online MODX creator, and a number of new MODX releases. He also released the source code to many of the tools the MOD Team uses internally. These tools can be found in the MODX Tools project on our code forge. The MOD Database continued to grow under Igor's leadership while maintaining a high level of quality.
I, wGEric, will go back to Modifications Team Leader to continue many of the projects Igor was working on and the Operations Manager will be left empty. We have found out that there aren't nearly as many task as we thought there would be for the Operations Manager so we have decided to go without one for the time being. In the future we will be looking into filling this position again.
Please join me in thanking Igor for all that he has done for the phpBB community as a MOD Author and as the MOD Team Leader and wishing Igor that he will continue to be successful throughout his life.
-
phpBB 3.1 to discontinue support for PHP versions below 5.2
After much internal discussion, the Development Team has decided that phpBB 3.0 "Olympus" will be the last in the line of phpBB releases that will officially support PHP versions less than 5.2.0. All future feature releases (and their maintenance releases), beginning with phpBB 3.1 "Ascraeus", will require PHP 5.2.0 or greater.
Following the release of phpBB 3.1 "Ascraeus", phpBB 3.0 "Olympus" will remain supported for a limited period of 6-9 months (further information on this will be released as it is decided upon) -- this version will remain compatible with PHP4.
As phpBB 3.1 "Ascraeus" is still in early stages of development, no release date has been set. Consequently, there is still plenty of time for you to upgrade your PHP installation.
Additionally, one should note that this announcement does not imply that phpBB 3.1 will see large portions of code rewritten in order to take advantage of new features in PHP 5.2. Instead, sections of code will be updated as needed in the 3.x release cycle.
|
