<meta name="description" content="phpBB 3.1.x Changelog" />

<title>phpBB &bull; Changelog</title>

</head>

<ol>

<li><a href="#changelog">Changelog</a>

<ul>

<li><a href="#v313">Changes since 3.1.3</a></li>

<li><a href="#v313rc1">Changes since 3.1.3-RC1</a></li>

<li><a href="#v312">Changes since 3.1.2</a></li>

<div class="content">

<a name="v313"></a><h3>Changes since 3.1.3</h3>

<h4>Security</h4>

</div></div>

<div>

</div>

</body>

phpBB Lead Developer: naderman (Nils Adermann)

phpBB Developers: bantu (Andreas Fischer)

dhruv.goel92 (Dhruv Goel)

Elsensee (Oliver Schramm)

marc1706 (Marc Alexander)

<meta name="description" content="phpBB 3.1.x frequently asked questions" />

<title>phpBB &bull; FAQ</title>

</head>

</div></div>

<div>

</div>

</body>

<meta name="description" content="phpBB 3.1.x Installation, updating and conversion informations" />

<title>phpBB &bull; Install</title>

</head>

<li>Oracle</li>

</ul>

</li>

<li>The following PHP modules are required:

<ul>

<li>json</li>

<p>If you are currently using a stable release of phpBB, updating to this version is straightforward. You would have downloaded one of four packages and your choice determines what you need to do. <strong>Note</strong>: Before updating, we heavily recommend you do a <em>full backup of your database and existing phpBB files</em>! If you are unsure how to achieve this please ask your hosting provider for advice.</p>

<a name="update_full"></a><h3>4.i. Full package</h3>

<p>First, you should make a copy of your existing <code>config.php</code> file; keep it in a safe place! Next, delete all the existing phpBB files, you may want to leave your <code>files/</code> and <code>images/</code> directories in place. You can leave alternative styles in place too. With this complete, you can upload the new phpBB files (see <a href="#install">New installation</a> for details if necessary). Once complete, copy back your saved <code>config.php</code>, replacing the new one. Another method is to just <strong>replace</strong> the existing files with the files from the full package - though make sure you do <strong>not</strong> overwrite your config.php file.</p>

<p>Once <code>install/database_update.php</code> has completed, you may proceed to the Administration Control Panel and then remove the install directory as advised.</p>

<p>The directory structure has been preserved, enabling you (if you wish) to simply upload the uncompressed 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 modifications (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.</p>

<a name="update_patch"></a><h3>4.iii. Patch file</h3>

<p>If you do get failures, you should look at using the <a href="#update_files">Changed Files</a> package to replace the files which failed to patch. Please note that you will need to manually re-add any 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.</p>

<a name="update_auto"></a><h3>4.iv. Automatic update package</h3>

<p>This update method is the recommended method for updating. This package detects changed files automatically and merges in changes if needed.</p>

<p>To perform the update, either follow the instructions from the <strong>Administration Control Panel-&gt;System</strong> Tab - this should point out that you are running an outdated version and will guide you through the update - or follow the instructions listed below.</p>

</div></div>

<div>

</div>

</body>

<meta name="description" content="phpBB 3.1.x Readme" />

<title>phpBB &bull; Readme</title>

</head>

<ul>

<li>Your server type/version, e.g. Apache 2.2.3, IIS 7, Sambar, etc.</li>

<li>DB type/version, e.g. MySQL 5.0.77, PostgreSQL 9.0.6, MSSQL Server 2000 SP1, etc.</li>

</ul>

<div class="content">

<p>Please remember that running any application on a development (unstable, e.g. a beta release) version of PHP can lead to strange/unexpected results which may appear to be bugs in the application. Therefore, we recommend you upgrade to the newest stable version of PHP before running phpBB. If you are running a development version of PHP please check any bugs you find on a system running a stable release before submitting.</p>

<a name="phpsec"></a><h3>7.i. Notice on PHP security issues</h3>

</div></div>

<div>

</div>

</body>

<meta name="description" content="This is an explanation of how to use the phpBB auth/acl API" />

<title>phpBB3 &bull; Auth API</title>

</head>

<p>Following are the methods you are able to use.</p>

<a name="acl"></a><h3>2.i. acl</h3>

<p>The <code>acl</code> method is the initialisation routine for all the acl functions. If you intend calling any acl method you must first call this. The method takes as its one and only required parameter an associative array containing user information as stored in the database. This array must contain at least the following information; user_id, user_permissions and user_type. It is called in the following way:</p>

<div class="codebox"><pre>

</div></div>

<div>

</div>

</body>

<meta name="description" content="Ascraeus coding guidelines document" />

<title>phpBB3 &bull; Coding Guidelines</title>

</head>

<div class="indent">

<p><code>$current_user</code> is right, but <code>$currentuser</code> and <code> $currentUser</code> are not.</p>

</div>

<p>In JavaScript, variable names should use camel case:</p>

<div class="indent">

<p><code>currentUser</code> is right, but <code>currentuser</code> and <code>current_user</code> are not.</p>

</div>

...

}</pre>

</div>

<p>In JavaScript code, braces always go on the same line:</p>

<div class="codebox"><pre>

</div></div>

<div>

</div>

</body>

acp_bbcodes_actions_append

===

* Location: adm/style/acp_bbcodes.html

* Since: 3.1.0-a3

* Purpose: Add settings to BBCode add/edit form

acp_email_options_after

===

* Location: adm/style/acp_email.html

* Since: 3.1.2-RC1

* Purpose: Add settings to mass email form

acp_forums_main_settings_append

===

* Location: adm/style/acp_forums.html

* Since: 3.1.2-RC1

* Purpose: Add settings to forums before prune settings section

acp_forums_rules_settings_append

===

* Location: adm/style/acp_forums.html

* Since: 3.1.0-b4

* Purpose: Add addtional options to group settings (after GROUP_RECEIVE_PM)

acp_main_actions_append

===

* Location: adm/style/acp_main.html

* Purpose: Add assets after stylesheets within the `<head>` tags in the ACP.

Note that INCLUDECSS will not work with this event.

acp_posting_buttons_after

===

* Locations:

* Since: 3.1.0-b4

* Purpose: Add content before BBCode posting buttons in the ACP

acp_ranks_edit_after

===

* Locations:

* Purpose: Add content after the last header-column (but before the action column)

in the ranks list in the ACP

acp_users_profile_before

===

* Locations:

* Since: 3.1.0-b3

* Purpose: Add user options fieldset to the top of ACP users view prefs settings

forumlist_body_category_header_after

===

* Locations:

* Since: 3.1.0-RC3

* Purpose: Add additional fields to the unban form in MCP

mcp_front_latest_logs_after

===

* Locations:

* Since: 3.1.3-RC1

* Purpose: Add content before latest unapproved posts list

memberlist_body_username_append

===

* Locations:

* Since: 3.1.0-b3

* Purpose: Add custom content to the user profile view before the main content

===

* Locations:

+ styles/prosilver/template/memberlist_view.html

===

* Locations:

+ styles/prosilver/template/memberlist_view.html

===

* Locations:

===

* Locations:

===

* Locations:

===

* Locations:

navbar_header_logged_out_content

===

* Since: 3.1.0-a3

* Purpose: Add content on all pages before the main content, after the header

overall_header_head_append

===

* Locations:

* Purpose: Add asset calls after stylesheets within the `</head>` tag.

Note that INCLUDECSS will not work with this event.

posting_editor_bbcode_status_after

===

* Locations:

* Since: 3.1.0-a2

* Purpose: Add field (e.g. textbox) to the posting screen before the subject

posting_pm_header_find_username_after

===

* Locations:

* Since: 3.1.4-RC1

* Purpose: Add content after the poll options on creating a poll

quickreply_editor_panel_after

===

* Locations:

* Since: 3.1.0-a4

* Purpose: Add content before the quick reply textbox

search_results_header_after

===

* Locations:

* Locations:

+ styles/prosilver/template/search_results.html

+ styles/prosilver/template/viewforum_body.html

* Since: 3.1.0-a1

* Purpose: Add content into topic rows (inside the elements containing topic titles)

topiclist_row_append

* Locations:

+ styles/prosilver/template/search_results.html

+ styles/prosilver/template/viewforum_body.html

* Since: 3.1.0-a1

* Purpose: Add content into topic rows (inside the elements containing topic titles)

ucp_agreement_terms_after

* Since: 3.1.0-b3

* Purpose: Add content before the terms of agreement text at user registration

ucp_pm_viewmessage_avatar_after

===

* Locations:

* Purpose: Add post button to private messages (next to edit, quote etc), at

the start of the list.

ucp_pm_viewmessage_print_head_append

===

* Locations:

* Since: 3.1.0-a1

* Purpose: Add asset calls directly before the `</head>` tag of the Print PM screen

ucp_prefs_personal_prepend

===

* Locations:

* Since: 3.1.0-a4

* Purpose: Add optional elements after list of friends in UCP

viewforum_buttons_bottom_before

===

* Locations:

* Since: 3.1.0-RC5

* Purpose: Add buttons after Post Reply button on the top of the posts's list

viewforum_forum_name_append

===

* Locations:

* Purpose: Add content to the bottom of the View topic screen below the posts

and quick reply, directly before the jumpbox in Prosilver.

viewtopic_body_poll_option_after

===

* Locations:

* Purpose: Add post button custom list to posts (next to edit, quote etc),

before the original list.

viewtopic_body_postrow_custom_fields_after

===

* Locations:

* Since: 3.1.0-b2

* Purpose: Add posts specific custom notices at the notices top.

viewtopic_body_topic_actions_before

===

* Locations:

* Since: 3.1.0-a4

* Purpose: Add data before the topic actions buttons (after the posts sorting options)

viewtopic_topic_title_append

===

* Locations:

location / {

# phpbb uses index.htm

index index.php index.html index.htm;

}

# Deny access to internal phpbb files.

}

# Pass the php scripts to fastcgi server specified in upstream declaration.

# Unmodified fastcgi_params from nginx distribution.

include fastcgi_params;

}

# Deny access to version control system directories.