[Fix] Ability to set permissions on non-mysql dbms (Bug #24955)
+
[Fix] Fixed blank style on setups having no username defined within config.php (Bug #25065)
+
[Fix] Made the compress_tar class tolerate archives that do not properly have their archived contents listed (Bug #14429 / thanks to JRSweets for his patch)
+
[Fix] Moved topics should not count towards the number of topics in a forum (Bug #14648 / thanks to Schumi for his patch)
+
[Fix] Properly check for invalid characters in MySQL DB prefixes during install (Bug #18775)
+
[Change] Generalize load check (Bug #21255 / thanks to Xipher)
+
[Change] Make utf8_htmlspecialchars not pass its argument by reference (Bug #21885)
+
[Fix] Bring the PostgreSQL backup system back to working order (Bug #22385)
+
[Change] Sort the tables at the database table backup screen
+
[Fix] Update correct theme for cached styles in style.php (Bug #25805)
+
[Fix] Also add PHPBB_INSTALLED check to download/file.php for inline avatar delivery
+
[Fix] Unable to login to some jabber server, reverted previous change (Bug #25095)
+
[Fix] Do not return BMP as valid image type for GD image manipulation (Bug #25925)
+
[Change] For determining the maximum number of private messages in one box, use the biggest value from all groups the user is a member of (Bug #24665)
+
[Fix] Correctly determine safe mode for temp file creation in functions_upload.php (Bug #23525)
+
[Fix] Correctly sort by rank in memberlist (Bug #24435)
+
[Fix] Purge cache after database restore (Bug #24245)
+
[Fix] Correctly display subforum read/unread icons from RTL in FF3, Konqueror and Safari3+. (thanks arod-1 for the fix, related to Bug #14830)
+
[Feature] Added optional referer validation of POST requests as additional CSRF protection.
+
[Fix] Added missing form token in acp (thanks NBBN).
+
[Feature] Added optional stricter upload validation to avoid mime sniffing in addition to the safeguards provided by file.php. (thanks to Nicolas Grekas for compiling the list).
+
[Fix] Do not remove whitespace in front of url containing the boards url and no relative path appended (Bug #27355)
+
[Change] Show email ban reason on registration. Additionally allow custom errors properly returned if using validate_data(). (Bug #26885)
+
[Feature] Streamlined banning via the MCP by adding a ban link to the user profile. Also pre-fills ban fields as far as possible.
+
[Feature] Added ACP logout to reset an admin session.
+
[Fix] reset forum notifications in viewtopic (Bug #28025)
+
[Fix] corrected link for searching post author's other posts (Bug #26455)
+
[Fix] HTTP Authentication supports UTF-8 usernames now (Bug #21135)
+
[Fix] Topic searches by author no longer return invalid results (Bug #11777)
+
[Change] Don't allow redirects to different domains. (thanks nookieman)
+
[Fix] Delete drafts and bookmarks when deleting an user. (#27585, thanks Schumi for the fix)
+
[Fix] Set last_post_subject for new topics. (#23945)
+
[Fix] Allow moving posts to invisible forums. (#27325)
+
[Fix] Don't allow promoting unapproved group members (#16124)
+
[Fix] Correctly fetch server name if using non-standard port (#27395)
+
[Fix] Regular expression for email matching in posts will no longer die on long words.
+
[Sec] Only allow urls gone through redirect() being used within login_box(). (thanks nookieman)
+
+
+
1.ii. Changes since 3.0.0
[Change] Validate birthdays (Bug #15004)
@@ -99,7 +142,7 @@
[Fix] Fixing wrong sync() calls if moving all posts by a member in ACP (Bug #18385)
[Fix] Check entered imagemagick path for trailing slash (Bug #18205)
[Fix] Use proper title on index for new/unread posts (Bug #13101) - patch provided by Pyramide
-
[Fix] Allow calls to $user->set_cookie() define no cookie time for setting session cookies (Bug #18025)
+
[Fix] Allow calls to $user->set_cookie() define no cookie time for setting session cookies (Bug #18025)
[Fix] Stricter checks on smilie packs (Bug #19675)
[Fix] Gracefully return from cancelling pm drafts (Bug #19675)
[Fix] Possible login problems with IE7 if browser check is activated (Bug #20135)
@@ -152,7 +195,7 @@
[Fix] Find and display colliding usernames correctly when converting from one database to another (Bug #23925)
-
1.i. Changes since 3.0.RC8
+
1.iii. Changes since 3.0.RC8
[Fix] Cleaned usernames contain only single spaces, so "a_name" and "a__name" are treated as the same name (Bug #15634)
@@ -161,7 +204,7 @@
[Fix] Call garbage_collection() within database updater to correctly close connections (affects Oracle for example)
-
1.ii. Changes since 3.0.RC7
+
1.iv. Changes since 3.0.RC7
[Fix] Fixed MSSQL related bug in the update system
@@ -196,7 +239,7 @@
[Fix] No duplication of active topics (Bug #15474)
-
1.iii. Changes since 3.0.RC6
+
1.v. Changes since 3.0.RC6
[Fix] Submitting language changes using acp_language (Bug #14736)
@@ -206,7 +249,7 @@
[Fix] Able to request new password (Bug #14743)
-
1.iv. Changes since 3.0.RC5
+
1.vi. Changes since 3.0.RC5
[Feature] Removing constant PHPBB_EMBEDDED in favor of using an exit_handler(); the constant was meant to achive this more or less.
@@ -269,7 +312,7 @@
[Sec] New password hashing mechanism for storing passwords (#i42)
-
1.v. Changes since 3.0.RC4
+
1.vii. Changes since 3.0.RC4
[Fix] MySQL, PostgreSQL and SQLite related database fixes (Bug #13862)
@@ -320,7 +363,7 @@
[Fix] odbc_autocommit causing existing result sets to be dropped (Bug #14182)
-
1.vi. Changes since 3.0.RC3
+
1.viii. Changes since 3.0.RC3
[Fix] Fixing some subsilver2 and prosilver style issues
@@ -429,7 +472,7 @@
-
1.vii. Changes since 3.0.RC2
+
1.ix. Changes since 3.0.RC2
[Fix] Re-allow searching within the memberlist
@@ -471,11 +514,11 @@
[Fix] Some jabber related bugs (Bug #12989, #11805, #11809)
[Fix] Added UTF-8 support for banning via the MCP (Bug #13013)
[Fix] Properly detect the script name in session::extract_current_page() if PHP_SELF is not defined (Bug #12705) - patch provided by ToonArmy
-
[Fix] Show role mask for global permission class under Permissions->Permission Roles (Bug #13057)
+
[Fix] Show role mask for global permission class under Permissions->Permission Roles (Bug #13057)
-
1.viii. Changes since 3.0.RC1
+
1.x. Changes since 3.0.RC1
[Fix] (X)HTML issues within the templates (Bug #11255, #11255)
This package is meant for those wanting to only replace changed files from a previous version to the latest version. This package normally contains the changed files from up to five previous versions.
-
This package contains a number of archives, each contains the files changed from a given release to the latest version. You should select the appropriate archive for your current version, e.g. if you currently have 3.0.0 you should select the phpBB-3.0.0_to_3.0.1.zip/tar.gz file.
+
This package contains a number of archives, each contains the files changed from a given release to the latest version. You should select the appropriate archive for your current version, e.g. if you currently have 3.0.1 you should select the phpBB-3.0.1_to_3.0.2.zip/tar.gz file.
The directory structure has been preserved enabling you (if you wish) to simply upload the contents of the archive to the appropriate location on your server, i.e. simply overwrite the existing files with the new versions. Do not forget that if you have installed any MODs these files will overwrite the originals possibly destroying them in the process. You will need to re-add MODs to any affected file before uploading.
@@ -285,7 +285,7 @@
The patch file is one solution for those with many Modifications (MODs) or other changes who do not want to re-add them back to all the changed files if they use the method explained above. To use this you will need command line access to a standard UNIX type patch application. If you do not have access to such an application but still want to use this update approach, we strongly recommend the Automatic update package explained below. It is also the preferred update method.
-
A number of patch files are provided to allow you to update from previous stable releases. Select the correct patch, e.g. if your current version is 3.0.0 you need the phpBB-3.0.0_to_3.0.1.patch file. Place the correct patch in the parent directory containing the phpBB3 core files (i.e. index.php, viewforum.php, etc.). With this done you should run the following command: patch -cl -d [PHPBB DIRECTORY] -p1 < [PATCH NAME] (where PHPBB DIRECTORY is the directory name your phpBB Installation resides in, for example phpBB3, and where PATCH NAME is the relevant filename of the selected patch file). This should complete quickly, hopefully without any HUNK FAILED comments.
+
A number of patch files are provided to allow you to update from previous stable releases. Select the correct patch, e.g. if your current version is 3.0.1 you need the phpBB-3.0.1_to_3.0.1.patch file. Place the correct patch in the parent directory containing the phpBB3 core files (i.e. index.php, viewforum.php, etc.). With this done you should run the following command: patch -cl -d [PHPBB DIRECTORY] -p1 < [PATCH NAME] (where PHPBB DIRECTORY is the directory name your phpBB Installation resides in, for example phpBB3, and where PATCH NAME is the relevant filename of the selected patch file). This should complete quickly, hopefully without any HUNK FAILED comments.
If you do get failures you should look at using the Changed files only package to replace the files which failed to patch, please note that you will need to manually re-add any Modifications (MODs) to these particular files. Alternatively if you know how you can examine the .rej files to determine what failed where and make manual adjustments to the relevant source.
diff --git a/phpBB/docs/coding-guidelines.html b/phpBB/docs/coding-guidelines.html
index 837ae55227..7d777056d9 100644
--- a/phpBB/docs/coding-guidelines.html
+++ b/phpBB/docs/coding-guidelines.html
@@ -1450,7 +1450,7 @@ div
What are Unicode, UCS and UTF-8?
-
The Universal Character Set (UCS) described in ISO/IEC 10646 consists of a large amount of characters. Each of them has a unique name and a code point which is an integer number. Unicode - which is an industry standard - complements the Universal Character Set with further information about the characters' properties and alternative character encodings. More information on Unicode can be found on the Unicode Consortium's website. One of the Unicode encodings is the 8-bit Unicode Transformation Format (UTF-8). It encodes characters with up to four bytes aiming for maximum compatability with the American Standard Code for Information Interchange which is a 7-bit encoding of a relatively small subset of the UCS.
+
The Universal Character Set (UCS) described in ISO/IEC 10646 consists of a large amount of characters. Each of them has a unique name and a code point which is an integer number. Unicode - which is an industry standard - complements the Universal Character Set with further information about the characters' properties and alternative character encodings. More information on Unicode can be found on the Unicode Consortium's website. One of the Unicode encodings is the 8-bit Unicode Transformation Format (UTF-8). It encodes characters with up to four bytes aiming for maximum compatibility with the American Standard Code for Information Interchange which is a 7-bit encoding of a relatively small subset of the UCS.
phpBB's use of Unicode
Unfortunately PHP does not faciliate the use of Unicode prior to version 6. Most functions simply treat strings as sequences of bytes assuming that each character takes up exactly one byte. This behaviour still allows for storing UTF-8 encoded text in PHP strings but many operations on strings have unexpected results. To circumvent this problem we have created some alternative functions to PHP's native string operations which use code points instead of bytes. These functions can be found in /includes/utf/utf_tools.php. They are also covered in the phpBB3 Sourcecode Documentation. A lot of native PHP functions still work with UTF-8 as long as you stick to certain restrictions. For example explode still works as long as the first and the last character of the delimiter string are ASCII characters.