We are pleased to announce the availability of the second release candidate of phpBB 3.0.7 aimed at experienced users in an effort to increase the quality of final releases.

Please scrutinise this release in-depth and report issues to the bug tracker. Critical bugs halting the board's operation should be reported immediately. Feel free to contact developers directly about such problems.

We recommend that international support sites update their sites to RC2, too. We are able to provide direct support to them within our international support sites forums.

*Mistake in code changes package for 3.0.7-RC1*
Please note there were 3 edits missing from the code changes package for 3.0.7-RC1. This was caused by a bug in our build script. The missing edits can be found at the end of this announcement. Make sure to apply these before the edits from RC1 to RC2.

*Tagging/Reviewing fixes*

This is very important! Please help verify fixes so that we can release a stable final version.

Every QA team member can now mark bug fixes as verified using our bugtracker. To mark a bugfix verified go to the bug and click "I have verified the fix of this ticket" in the "Options" section on the right. Of course prior to clicking you should have properly checked whether the bug was really fixed. Comment on the respective bug if you find problems so the fix can be corrected.

To easily get an overview over fixed bugs you can access the QA overview page. It lists unfixed critical bugs at the top. Then a list of critical bugs that have been fixed - these should be thorougly checked to confirm that the problem has really been solved. And then all other bugs that have been fixed since the last release are listed. You should focus on the least tested bugs when choosing which one you are going to test next.

We already gave out instructions to language pack authors to let them update their language packs in a timely manner. The changes are provided with the code changes package (see downloads section below). Style authors should also download the code changes package and adjust their styles accordingly. Please post within our Styles forums if you have questions or encounter problems.

*New features, changes, bug fixes*

Since 3.0.7 RC1 we have made a small number of changes.

We have added two small new features:
- Add INTTEXT token type to custom bbcodes to allow non-ASCII letters in html attributes.
- Add ability to enable quick reply in all forums.

A performance improvement and an alteration of the custom bbcode creation for administrators have also taken place:
- Speed up topic move operation by adding an index for topic_id on the topics track table. (Bug #56545)
- Warn users about potentially dangerous BBcodes.

And a number of bugs have been fixed:
- Fix javascript bug in the smilies ACP. (Bug #55725)
- Unify BBCode Selection across browsers. (Bug #38765)
- Allow convertors to read in configuration from files. (Bug #57265 - Patch by Dicky)
- Fix problems with firebird by no longer using 'count' as a column alias. (Bug #57455)
- Small language correction for the FAQ page. (Bug #57825)
- Restrict search for language/../iso.txt to folders. (Bug #57795)
- Make user_email_hash() function independent from system's architecture. (Bug #57755)
- Correct behavior of "force_approved_state" when value is false. (Bug #57715)
- Global announcements could not be accessed on a board using Firebird as the database server. (Bug #57525)
- BBCode parser now uses the user object for all settings rather than taking some from the template object (Bug #57365)
- Ensure a database connection is available before logging general errors. (Bug #57975)
- Do not delete unrelated attachments when deleting empty forums. (Bug #57375)
- Update: Store expected resulting file contents in cache and do not suggest further merges if the contents match, also fixes infinite merge loop (Bug #54075)

The complete list including previous releases can be found in the changelog file within the docs folder contained in the package.

*Available packages:*

This release is available in five packages.

Full Package: Contains the entire phpBB3 source and British English language files.

Automatic Update Package: Update package for the automatic updater, contains changes from the previous release to this release.

Changed Files Only: Contains only the files modified in this release of phpBB3. Please note this archive contains modified files in comparison to every previous release.

Patch Files: Contains patches against previous versions of phpBB3 that can be applied with a patch programme.

Code Changes Package: This package contains all changes to language files, the prosilver style and the subsilver2 style.

Select the package most suitable for you. As a tiny guide we recommend the following methods based on the requirements:

- For a new installation, use the Full Package
- For updates of boards without modifications you can use the Automatic Update Package (guided udpate) 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 directly.
- International Support Teams may use the Patch Package in conjunction with the Code Changes to better support users having problems with conflicts or specific 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!*

To correctly perform an update, do not forget to re-enable the PHPBB_QA constant in your includes/constants.php file. Otherwise you are not prompted for an update in the ACP and the automatic update will eventually fail.