EXT:mm_forum¶

Install extension¶

The first step to install the mm_forum extension is – of course – to import it into your TYPO3 environment using the extension manager. To do so, go to the extension manager and select “Import extensions” in the drop-down menu on the top of the page:

Then select the extension file you downloaded from in the select box labeled “Upload extension file directly” and click on “Install”:

Before using mm_forum,you need to tell mm_forumwhere to find and store its data. For this, you should create a new page where your forum data are to be stored. Probably the best solution to do this would be to create a SysFolder for the data. You will also need an additional SysFolder for user data. If you have already a login system running on your site, you will probably be using this for your forum. Then you do not need another SysFolder for user data.

Now it is time to configure your extension. You will have noticed that an additional menu item appeared in your TYPO3 navigator that is labeled “mm_forum”. If you do not see this button, reload the page once.

This menu item will take you to the mm_forum backend module, which will allow you to properly configure your mm_forum. If you see a scrollbar at the right part of the TYPO3 backend click on the bar between the tree and the forum backend module to see the complete backend module.

The first thing you will have to do is to specify the mm_forum data storage page (which you have just created) and the TYPO3 frontend user page:

Hit the folder icon next to the input field to open a page tree where you will be able to select your mm_forum data storage page. In the next installation step, you will be asked to specify the user page. You can do this the same way as you did with the storage page.

In the following installation step, you will be asked to specify two groups, the default user group and the administrator group. These two groups will be used by the mm_forum to distinguish different user authentications. Later on you can add more groups, but these two are the only ones that are really required.

If you have already some user groups existing, you can select these using the folder icon next to the input field. Just like in the steps before, you will have a page tree where you will be able to select the regarding group. Notice that all groups have to be located on the user storage page which you specified one step before.

If you do not have any groups at all yet, you can create a new group by hitting the plus icon. After you hit this icon, a form will be displayed where you can input all necessary options for the new user group. When you have specified everything, just click “Save and Close” and you will get back to the mm_forum installation. Now you can select the newly created user group using the folder icon. The new user groups was stored automatically on the page you specified as user storage page. Do so with both groups.

After setting all these values, the basic installation of the mm_forumextension is complete. Now you will see the complete mm_forum configuration tool, where you can set a lot of properties. As you can see, most of these fields are already filled out with the values you have specified during the installation or with default values, so regularly you do not need to change anything to run the mm_forum.

To use mm_forum you must set is the Board page property in the Forum category. This is the page where you have placed your main mm_forum plugin (too see how to do this, read the following chapter).

Create Page Content¶

Now you have successfully configured everything that is necessary to get started with the mm_forum extension. All you have to do now is to create some pages and insert the required mm_forum plugins on these pages.

Very important: You have to include some mm_forum static templates on the pages where mm_forum plugins are used. It it recommended to include the static templates only where needed because they are quite huge. You can find a step by step tutorial is at the end of this chapter.

As you will notice, the mm_forum extension contains six different plugins, all with different functionalities (and different importance). The central plugin is the mm_forum : Forum plugin. Since this plugin offers plenty functionalities, you will have to specify what the plugin has to show, by specifying a value in the “What to display” field. Consider the following table to get to know which plugin uses which configurations:

Setup the forum¶

Now you have inserted the message board on your page. However, at this moment, there are no categories at all. To change this, go to the mm_forum backend module in Web ► mm_forum .

In this module you have the opportunity to do all the forum administration. You have access to the following administrative settings:

• User administration : Offers functions for administrating the mm_forum users.
• Board Administration : Create categories and message boards.
• Templates : Edit the HTML Templates.
• Tools : Add new smilies and post parser functions.
• Data import : Import all your data from an existing phpBB board or the chc_forum extension.
• Extend user profil Add additional fields to the user profil.
• Install Configuration options for the forum.
• Statistics View statistics like new posts per month.
• User ranks Configure user ranks.
• Updater Update the extension from SVN. Use with care, as the svn- version might be unstable.

How to include the static templates¶

Click on the “Template” menu item on your TYPO3 navigator.

Go to the site(s) where you are using mm_forum plugins. Create an extension template (if none exists).

If there is an extension template, edit the whole template record.

Go to the “Includes” tab an include static templates (from extensions). Please note that in mm_forum uses by default a new pagebrowser that needs the extension “pagebrowse” and the static template included.

Static templates: Prototype or jQuery¶

New in mm_forum 1.9.0 is the support of jQuery. As a result there are two static templates: One for prototype and one for jQuery.

Warning: Only one static “mm_forum Javascript” template is allowed to be included. If you include all mm_forum templates you will get Javascript errors and mm_forum will not work as expected.

Choose one of the following configurations (Prototype or jQuery):

Attention: Please include the static “mm_forum Javascript” template before the main static mm_forum template. Otherwise some functions will be broken!

::¶

[b]...[/b]

[b]Bold text[/b]. Normal text.

::¶

[i]...[/i]

[i]Italic text[/i].

::¶

[u]...[/u]

::¶

[color=COLOR]...[/color]

[color=red]Red text[/color]
[color=#00ff00]Green text[/color]

::¶

[url]...[/url]
[url=...]...[/url]

[url]http://www.typo3.net[/url]
[url=http://www.typo3.net]Click me[/url]

::¶

[link]...[/link]

[link]http://www.typo3.net[/link]

::¶

[img]...[/img]

[img]myimage.jpg[/img]

::¶

[size=...]...[/size=...]
[size=...]...[/size]

[size=2]Bigger Text[/size=2]
[size=2]Bigger Text[/size]

The moderated forum mode¶

As of version beta 0.1.2, you can set the mm_forum to the moderated mode. In this mode, postings made by users will not appear instantaneously in the forum, but will rather be stored in an inactive status until they are published by a moderator. The idea behind this feature is the possibility for moderators to be able to better control what their users write.

To be able to publish the post that are stored in the so called „post queue“, you have to insert a „List post queue“ content element (see section „Getting started“). You should protect this page against unauthorized access using the TYPO3 internal access control functionalities.

The moderator panel for publishing posts looks like on the following screenshot.

The moderator has different options on what to do with the queued posts. The posts can either be marked to be

• published (P): In this case, the queued post or topic will be inserted into the public area of the forum. At the same time, the post/topic will be removed from the post queue so that it disappears from this list view. The post/topic will be visible as any regular post in a usual (non-moderated) mm_forum instance.
• ignored (I): If a moderator does not know what to do with a post, maybe because the post's content is, although it does not violate any board regulations directly, highly questionable, while at the same time he wants to publish the remaining unquestionable posts, he can select a queued post/topic to be ignored. The post/topic will neither be published nor deleted and remains in the post queue list.
• deleted (D): If a posts violates board regulations or any laws, the moderator can decide to just delete the post without publishing it. The post will not be published and not appear on the post queue list any more.

The moderated mode can be enabled using the mm_forum configuration module.

The administration panel¶

If you have defined administrators in the backend they will have some more possibilities in the forum. For example, members of the administrator group see a special administrator panel on the top of every topic they visit, where a moderator has got some special options:

• Topic title: Here you can change the topic's title.
• Topic prefix: You can apply a specific prefix to a topic. A list of predefined prefixes is defined in plugin.tx_mmforum_pi1.prefixes. In the prefix listing special view, users have the possibility to have only topics with a certain prefix listed.
• Move topic: Moderators can move a topic from one forum to another.
• Close topic: If a topic is closed, regular users will not be able to write in it anymore. However, moderators and administrators will still be able to reply to this topic.
• Fix topic: Regularly, in the topic listing view, topics are ordered descending by the time the last reply was written. Topics marked as fixed will always be displayed on the top of the topic list, no matter when the last reply was written.
• Delete topic: Ok, this should be self-explaining...

Post reports¶

Each user is allowed to report a post to the moderators and administrators. He/she must input a reason for this post being reported.

Regularly, this feature is used for users to report posts that violate either the board rules or even laws so that these posts can be deleted and the authors be warned or banned.

If you create the content element Plugin: mm_forum :: Forum and select Reported posts in What to display ,all moderators and administrators get a list with the reported posts and check the reported posts.

NOTE: Since the mm_forum extension does not check the user authentication in the post alert listing, it is necessary that you protect this page using the TYPO3 internal user authentication functionality.

BB Codes¶

With this tool, you can define your own BBCode elements. In the mm_forum extension, a BBCode consists of three elements. First the code itself, second a regular expression telling how the code is recognized in a post's text and third a replacement pattern. The second and the third value are parsed by the PHP function preg_replace(see http://www.php.net/preg_replace for further information).

Furthermore, you can take a look at the already existing BBCode elements that were installed along with the mm_forum in order to understand how the BBCode implementation system works.

Smilies¶

You can also add custom smilies to your mm_forum. Defining a new smiley is very simple. You just have to define which image file should be used for the smiley (the backend module looks for smiley images in the directory EXT:mm_forum/res/smilies) and the code this image is associated with. This code will be replaced later on with the actual image.

Syntax Highlighting¶

The mm_forum extension uses the Generic Syntax Highlighter plugin (GeSHi) by Nigel McNie in order to offer syntax highlighting of code samples in various programming languages. To configure which highlighting options you want to offer, you can select the Syntax highlighting option in the Tools menu. The syntax highlighter options work pretty much like the BBCode options. You can specify a programming language (you can only select languages that are supported by GeSHi) and a replacement pattern (again, see http://www.php.net/preg_replace for further information).

phpBB data import¶

Using the phpBB data import tool, you can import nearly all data from an already existing phpBB board into your newly created mm_forum board. The import tool is specified for the newest phpBB version, which is 2.0.22.

CHC Forum/CWT Community data import¶

Using the CHC Forum import tool, you can import all data from the CHC Forum TYPO3 extension. Please notice that all mm_forum data will be erased before the CHC Forum data import.

NOTE: Although TYPO3 handles database record deletion by just setting a “deleted” flag to 1 while the actual record remains in the database, this is not practiced if you select all data to be deleted in the import tool. The records will be deleted by a MySQL DELETE order, so be careful when deleting the entire *mm_forum* database.

**You will not be able to get back your data once it has been erased.**

The manual Mode¶

If you are logged in as an administrator, you will see a link labeled Start indexing below the search function. If this link is clicked, the script will automatically update the search index. However, this has to be done manually in regular intervals.

A more elegant solution is the automatic indexing using a CronJob.

The CronJob mode¶

-*/15 * * * *   user Lynx "http://www.domain.tld/forum/search.html?tx_mmforum_pi4[ind_auto]=1&tx_mmforum_pi4[indexingPassword]=admin" –accept_all_cookies > /dev/null

Prefix listing¶

As you may have noticed, moderators and administrators have the possibility to apply a certain prefix to a topic, like e.g. “HowTo” or “Info”. The mm_forum extension offers a functionality to display all topics with a certain prefix.

The idea behind this feature is that moderators can e.g. apply the prefix “HowTo” to topics where a solution to a certain problem is explained in a very easy and comprehensible way or that contain a detailed description on how to do something, and that users can later on see all topics marked as e.g. “HowTo”.

To implement a prefix listing functionality on your site, you just have to create a link to the page the mm_forum :: Forum plugin is placed on, supplemented with the following parameters:

&tx_mmforum_pi1[action]=list_prefix&tx_mmforum_pi1[list_prefix][prfx]=PREFIX

Replace PREFIX with your own custom prefix (without brackets).

Unanswered posts¶

You can also list all posts that have not yet been answered. To go to this special list view, you have to create a link to the page the mm_forum :: Forum plugin is placed on, supplemented with the following parameters:

&tx_mmforum_pi1[action]=list_unans

Unread posts¶

Furthermore you can list topics that contain replies the user that is currently logged in has not yet read. To access this special list view, you have to create a link to the page the mm_forum :: Forum plugin is placed on, supplemented with the following parameters:

&tx_mmforum_pi1[action]=list_unread

Link to special listing pages using FlexForms¶

As of mm_forum version 0.0.4, you have a FlexForm configuration field for the mm_forum :: Forum plugin. There you will have the possibility to create a shortcut to one of these special listing without specifying such a complicated url as mentioned above. You just have to create a new page in the page tree, insert a new instance of the mm_forum :: Forum plugin on it. In the FlexForms configuration of this new instance, you set “What to display” to “Message board” and “Show special page” to “List unanswered topics”, or to whatever you like.

NOTE: You will have to save the plugin instance once after setting “What to display” to “Message board” before you will be able to see the “Show special page” item.

If this plugin is called in the frontend, it will redirect the visitor to the main instance of mm_forum :: Forum (defined in the TS constants in plugin.tx_mmforum_boardPID), with the URL being supplemented with the correct parameters (that are also explained above).

Basics¶

The mm_forum extension offers the possibility to extend the user profile by a (theoretically) unlimited amount of additional fields. These fields can then be filled out by the users on registration and edited later on. The administrator can define whether the information entered in these fields shall be public or only visible to the administrator.

To extend the user profile, go to the menu point Extend user profile in the mm_forum backend module. Here you will see a list of fields the user profile was already extended with. Here you will see that most of the input fields that are displayed during user registration and editing are actually handled as a custom user field. These default user fields are imported with the static table data during the installation of the extension. You can use the button labelled New field to create an additional profile field. You can sort the profile fields using the up and down buttons.

The delete , up and down buttons should be self-explaining. Using the Edit button, you get to the user field editing form. Here, you have the possibility to configure your user field to the finest detail:

• Field Name . This is the title of the user field. It will be used as label in the registration and editing form and the public profile overview. This field is multilingual, so by clicking the flag, you can add a translation in a language of your choice.
• Required . This check box defines whether this field is required to be filled in by the user. If the user leaves a required field empty on registration or an update, an error message will be displayed.
• Restricted visibility . If this field is checked, its contents will only be visible to the user him-/herself and to the administrator.
• Link with fe_user table . Here you can define, in which column of the fe_user table the contents of this field are to be saved. If you leave this property empty, the contents of this field will be stored in an additional table and not in the fe_user table.
• Field Type . Here you can specify the field type of you user field. There are four predefined field types (text field, radio button, check box and selection list). However, by using the custom field, you can specify a user field of any type you like. See the section Custom user fields of this manual for more information.

Custom user fields¶

Although the interface presents a set of predefined field types, every user field is defined by a certain typo script configuration. If you choose one of the four predefined types, this configuration will be written automatically. If you choose Custom , you are on your own.

In the typo script configuration, three content elements have to be defined. These are called label , input and output . The label object is used for generating the field label in forms and the public profile. The input object is used to generate a input field for the registration or user editing form, while the output object is used to render the read-only output for the public profile. All these objects have to be regular typo script objects. The rest is up to you.

A variable named “fieldvalue” will be loaded into the data array, allowing you to dynamically access the user field's field value. Furthermore, the markers ###USERFIELD_NAME###, ###USERFIELD_UID### and ###USERFIELD_VALUE### will be substituted in the generated content.

To make the whole topic more understandable, you will find an example field configuration in the following paragraph. This will create a simple checkbox in the user settings field. The field value will be translated to “1” or “0” in the public user profile:

label = TEXT
label {
     value = Likes beer
}
input = COA
input.1 = TEXT
input.1.value = <input type="hidden" name="###USERFIELD_NAME###" value="0" />
input.2 = CASE
input.2 {
  default = TEXT
      default.value =  <input type="checkbox" name="###USERFIELD_NAME###" value="1" />
        0 = TEXT
    0.value = <input type="checkbox" name="###USERFIELD_NAME###" value="1" />
       1 = TEXT
    1.value = <input type="checkbox" name="###USERFIELD_NAME###" checked="checked" value="1" />
   key.field = fieldvalue
}
output = CASE
output {
  key.field = fieldvalue
      0 = TEXT
    0.value = No
        1 = TEXT
    1.value = Yes
}

Another example field configuration for extending the user profile with a dropdown field:

label = TEXT
label {
     value = Design
}
input = CASE
input {
    stdWrap.wrap = <select name="###USERFIELD_NAME###">|</select>
 default = TEXT
      default.value = <option value="1">Night</option><option value="2">Tag</option>
  1 = TEXT
    1.value = <option selected="selected" value="1">Night</option><option value="2">Tag</option>
  2 = TEXT
    2.value = <option value="1">Night</option><option value="2" selected="selected" >Tag</option>
 key.field = fieldvalue
}
output = TEXT
output {
  value (
             <select name="###USERFIELD_NAME###">
                <option value="1">Night3</option>
             <option value="2">Tag</option>
                </select>
     )
}

Available cronjobs¶

In the following section you will find a list of all cronjobs you can set up:

Setting up a cronjob¶

First of all, in order to set up a cronjob on your system, you need – of cource – SSH access, except your hosting provider offers the possibility to set up a cronjob automatically. After logging in, you can edit the crontab using the shell command

crontab -e

Alternatively, you can put your cronjob into an own file and place it into the /etc/cron.d or /etc/cron.hourly directory.

All cronjobs are started by the script cli.tx\_mmforum\_cron.php . This script expects a parameter telling the script what exactly to do. To identify the cronjobs, you can use the cronjob names mentioned above.

Please regard that it is necessary to start the cronjob script using it's absolute path; not a relative path.

For example, a typical cronjob entry could look like the following:

*/15 * * * * /srv/www/typo3conf/ext/mm_forum/cron/cli.tx_mmforum_cron.php indexing > var/log/mm_forum/indexing.log

This cronjob will start the indexing process every 15 minutes and write the results of the cronjob into a logfile.

((generated))¶

plugin.tx_mmforum.adminGroup = 1;
plugin.tx_mmforum.moderatorGroup = 2;
plugin.tx_mmforum.userGroup = 3;

General¶

File paths¶

Message Board¶

Search¶

Private messages¶

plugin.tx_mmforum (General settings)¶

The plugin.tx\_mmforum object contains general configuration variables that are used by all plugins. The specific plugins inherit all configuration from this object. This means that changing a value here will affect all mm_forum plugins.

{$plugin.tx_mmforum.storagePID}

{$plugin.tx_mmforum.userPID}

{$plugin.tx_mmforum.boardPID}

{$plugin.tx_mmforum.userProfilePID}

{$plugin.tx_mmforum.pmPID}

{$plugin.tx_mmforum.adminGroup}

{$plugin.tx_mmforum.userGroup}

uploads/tx_mmforum/

{$plugin.tx_mmforum.path_img}

{$plugin.tx_mmforum.path_smilie}

{$plugin.tx_mmforum.informal}

{$plugin.tx_mmforum.dateFormat}

{$plugin.tx_mmforum.userNameField}

{$plugin.tx_mmforum.boardName}

{$plugin.tx_mmforum.team_name}

{$plugin.tx_mmforum.site_name}

{$plugin.tx_mmforum.disableRootline}

{$plugin.tx_mmforum.realURL_specialLinks}

{$plugin.tx_mmforum.notifyMail_sender}

< plugin.tx_mmforum.buttons_text

none

auto

0

specialchars

_blank

link_10

1

1

1

1

#gggggg

#ghfghf

tx-mmforum-pi1-pt-quote

tx-mmforum-pi1-pt-code

plugin.tx_mmforum_pi1 (mm_forum :: Forum)¶

{$plugin.tx_mmforum.rssPID}

100

100

{$plugin.tx_mmforum.topic_hotPosts}

{$plugin.tx_mmforum.user_hotPosts}

{$plugin.tx_mmforum.postsPerPage}

{$plugin.tx_mmforum.threadsPerPage}

{$plugin.tx_mmforum.prefixes}

Test

{$plugin.tx_mmforum.spamblock_interval}

{$plugin.tx_mmforum.signatureLimit}

.open = #ffdddd
.work = #ffffdd
.done = #ddffdd

{$plugin.tx_mmforum.enableShadows}

typo3conf/ext/mm_forum/res/scripts/editor_javascript.inc.js

{$plugin.tx_mmforum.topicIconMode}

{$plugin.tx_mmforum.polls_enable}

2

1 = #ff0000
2 = #00ff00
3 = #0000ff
4 = #ff00ff
default = #ff0000

{$plugin.tx_mmforum.polls_restrict}

{$plugin.tx_mmforum.attachment_enable}

{$plugin.tx_mmforum.attachment_count}

uploads/tx_mmforum/

{$plugin.tx_mmforum.attachment_filesize}

{$plugin.tx_mmforum.attachment_allow}

{$plugin.tx_mmforum.attachment_deny}

{$plugin.tx_mmforum.attachment_preview}

<span class="tx-mmforum-pi1-listtopic-prefix">[ | ]</span>&nbsp;

<div class="tx-mmforum-pi1-listtopic-pages"> | </div>

<div class="tx-mmforum-pi1-listtopic-pages" style="display:inline; padding:0px;">(&nbsp; | &nbsp;)</div>

1

<span style="font-size:10px; font-weight: bold;">[ | ]</span><br />

<span style="font-size:10px;"> | </span><br />

<span class="tx-mmforum-pi1-administrator">[ | ]</span>

<span class="tx-mmforum-pi1-moderator">[ | ]</span>

<span style="font-size:10px;"> | </span><br />

<span class="tx-mmforum-pi1-highlight"> | </span>

 » 

tx-mmforum-button

tx-mmforum-list-even

tx-mmforum-list-odd

<div class=“tx-mmforum-pi1-smilies“> | </div>

<div class="tx-mmforum-pi1-smilie"> | </div>

plugin.tx_mmforum_pi2 (mm_forum :: User registration)¶

plugin.tx_mmforum_pi3 (mm_forum :: Private messaging)¶

<span class="tx-mmforum-pi3-pminbox-unread"> | </span>

plugin.tx_mmforum_pi4 (mm_forum :: Search)¶

<strong> | </strong>

plugin.tx_mmforum_pi5 (mm_forum :: User settings)¶

plugin.tx_mmforum_pi6 (mm_forum :: Portal information)¶

<span style="font-weight:bold;color:#8e8d8d;"> | </span>

<span style="font-weight:bold;"> | </span>

::¶

button_iconname

::¶

button_label

::¶

button_link

::¶

button_atagparams

By default, the mm_forum contains two button templates, one for text based buttons and one for image buttons. These are stored in plugin.tx_mmforum_pi1.buttons_text and plugin.tx_mmforum_pi1.buttons_image. This allows you to switch between text and image buttons by just copying the regarding object into the buttons object:

plugin.tx_mmforum_pi1.buttons < plugin.tx_mmforum_pi1.buttons_text

In version 0.1.6, text buttons are enabled by default.

::¶

unread

::¶

unanswered

::¶

closed

::¶

solved

::¶

hot

Team leader¶

Martin Helmich , m.helmich@mittwald.de

Developers¶

• Björn Detert , b.detert@mittwald.de
• Benjamin Mack , benni@typo3.org
• Georg Ringer , mail@ringerge.org

User manual¶

• Ines Willenbrock , icy@icys-scholle.de
• Stefan Lang

Bugtracker organization and testing¶

Ines Willenbrock , icy@icys-scholle.de

Initial development¶

• Holger Trapp (now Steinmeier)
• Ines Halstenberg
• Stefan Horenkamp
• Steffen Kamper , steffen@dislabs.de
• Markus Walter , markuswalter@airpost.net

Contributors¶

Beta 1.9.0¶

• Frontend administration: The forum extension now features a frontend administration plugin that allows administrators to manage categories and forums using a frontend plugin.
• Data import: The data import module has been completely redesigned. Please note that this module has been outsourced into the mm_forum_import extension.
• Salted passwords: The mm_forum extension now supports the mechanism for salted passwords introduced in TYPO3 4.3.
• Extensible backend module: The backend module can easily be extended using a special typoscript configuration. Have a look at the mm_forum_import extension in order to see the mechanism working.
• Pagebrowser: The forum now uses the pagebrowse Extension by Dmitry Dulepov to display the page navigation.
• Miscellaneous: The version 1.9 includes a lot of minor new features and bugfixes. Please see http://forge.typo3.org/versions/show/212 for a full list.

Beta 1.8.0¶

• New backend module: The backend module has been completely overworked in both function and aesthetics.
• User fields: The extended user field handling has been improved. While in older versions, all fields had to be configured using TypoScript, there are now predefined templates for creating text fields, check boxes, radio buttons, drop-down selection lists, …In the same step, the user editing forms (i. e. registration and profile editing) have been revised. Now, all fields (except user name and password) can be fully configured in the backend module.
• Ratings: The mm_forum uses the ratings extension provided by Netcreators BV for rating forums, topics, posts and users. The rating option can be enabled or disabled for each element type separately using a Typoscript option.
• Documentation: The documentation has been brought up-to-date regarding both content and layout. Thanks to Ines Willenbrock.
• Compatibility with TYPO3 4.3: The extension has been thoroughly tested with TYPO3 4.3.0-alpha3 and a lot of compatibility issues have been fixed. If any more problems should occur with the final version of TYPO3 4.3, feel free to report them at http://forge.typo3.org .
• Performance tuning - Caching mechanisms: Some caching mechanisms were added to the extension which improves the performance of the mm_forum frontend plugins. When used with TYPO3 4.3, the extension used the built-in caching interface, otherwise an self-developed interface will be used.
• Performance tuning – Database layout, code structure: Both the forum and topic index views and messaging inbox view have been optimized by adding some missing indexes to the database tables (remember to bring your database structure up-to-date when upgrading) and by tweaking the mm_forum source code. Credits to go Christopher Lörken.
• Extensive code reorganisation: The source code of the mm_forum extension has been reorganized in order to reduce redundancies in the code and to make the code conform to the official TYPO3 coding guidelines. Thanks to Benjamin Mack of the TYPO3 Core development Team.

Beta 0.1.7¶

• Multiple file attachments: The maximum number of file attachments can now be set using an attribute in the Configuration module. Thanks to Georg Ringer for contributing to this feature.
• Improved cronjob features: Crobjobs can now be started using a command line call instead of calling a script in the browser. Furthermore, there are more available cronjobs.
• Updated default design template: The default design template was modernized and the orange color was replaced with a dark blue.
• RSS Feeds: The mm_forum extension now supports an RSS export of forum data
• Documentation: Added a FAQ section and removed the Todo section since it was out of date anyway.

Beta 0.1.6¶

• Updated icon generation: Implemented a new method if topic and board icon generation. However, the old icon generation mechanism is still available. Both mechanisms can be switched using the install module. See Customizing ► Topic icons for more information.
• German manual: There is a german version of this manual available in the docs/ directory of the extension. Thanks to Stefan Lang for translating this document.
• Extensive bug fixing: See http://bugs.typo3.net

Beta 0.1.5¶

• Cronjobs: The mm_forum now supports cron jobs in order to perform regulary occuring events, like for example informing users about new private messages once a day. See Administration ► Cronjobs for more information. More cronjob features will follow in the next versions.
• Captcha support: The mm_forum extension now offers support for the captcha extension. The extension is implemented in the registration plugin in order to validate new user registrations. Captcha validation can be enabled/disabled using the mm_forum installation tool.
• Board subscriptions: Additional to the possibility to subscribe certain topics (meaning the option of being notified when somebody replies to a subscribed topic), users can now subscribe entire boards. In this case, the user will be notified when a new topic was opened in this board. This feature was implemented by Cyrill Helg ( cyrill.h@solnet.ch ).
• Translations: Implemented a Russian translation. Credits go to Stas Kobzar ( http://doodo.info ).
• Minor improvements:
  • User profile linking: Link generation to user profiles is now being handled by a single function (tx_mmforum_pi1::getUserProfileLink) that can be extended by the hook profileLink_postLinkGen. This makes it easier for developers to connect the mm_forum extension with other community extensions.
  • Longer BB code replacements The maximum length of a BB code replacement was incremented from 255 bytes to 65535 bytes. This makes it possible to implement more complex BB codes.
  • Notifications Email notification about new PMs is now optional (though enabled by default) and can be enabled/disabled in the user settings plugin.
• Bug fixes: See http://bugs.typo3.net .

Beta 0.1.4¶

• Translations: Implemented a French and a dutch translation for the mm_forum extension. Credits go to Guy Sinden ( http://abis- freiburg.de ) for the French translation and to Rob Vonk ( http://www.robvonk.com ) for the dutch translation.Furthermore, an informal German translation was added (using the address “Du” instead of “Sie”). The informal language mode is theoretically available for all languages and can be enabled using the mm_forum configuration module.
• Bug fixes: See http://bugs.typo3.net .

Beta 0.1.3¶

• Security issues: Several security issues have been fixed. See the official security bulletin 20070919-1 for more details
• Translations: Implemented a finnish translation for the mm_forum extension. Credits to Katja Lampela.
• Bug fixes: Bug fixing as usual. See the official mm_forum bug tracker on http://bugs.typo3.net for more information on which bugs were fixed.
• Changed design templates: change_user/main.html (modified)forum/list_post.html (modified)forum/favorites.html (modified)forum/polls.html (modified)forum/search.html (deleted)forum/post_del.html (deleted)

Beta 0.1.2¶

• User ranks: An optional user ranking functionality was implemented. Users now can obtain a higher rank by writing more posts. See Administration ► User ranks for more information.
• Moderated forum: Implemented a functionality to use the mm_forum as moderated board. This means that topics and posts have to be cleared by a moderator before becoming public. The feature can be enabled/disabled using the configuration module.
• Bug fixes: Some minor bugs were fixed. See the official mm_forum bug tracker on http://bugs.typo3.net for more information on which bugs were fixed.
• Changed design templates: forum/login_error.html (modified)forum/postqueue.html (added)

Beta 0.1.1¶

• Improved user name verification: The user name verification in the mm_forum :: User registration plugin was changed to a “deny all, allow some” directive. The list of allowed characters can be changed in TypoScript. This guarantees a higher security and flexibility.
• Fixed some security issues: Some security issues were fixed. Before, users were able to insert Javascript on a mm_forum page using manipulated BBCodes. This was fixed by a more restrictive regular expression syntax. It is necessary to re-import the static data after updating.
• Added some minor features: Some minor features were added:
• After changing something in the mm_forum configuration module, the cache does not have to be cleared anymore, since the configuration module does this automatically now.
• BBCodes in user signatures can now be disabled. The regarding option can be found in the “Forum” section in the configuration module.
• A user list can now be displayed. It is part of the mm_forum :: Forum plugin and can be selected using the FlexForms configuration.
• Bug fixes: Some minor bugs were fixed. See the official mm_forum bug tracker on http://bugs.typo3.net for more information on which bugs were fixed.

Beta 0.1.0¶

• Statistics module: A statistics module was implemented allowing the administrator to see interesting statistics, like the development of the post or topic amount.
• Bug fixes: A lot of minor bugs were fixed. See the official mm_forum bug tracker on http://bugs.typo3.net for more information on which bugs were fixed.

Alpha 0.0.7¶

• Poll system: Implemented a poll system. A poll can now be attached to a topic where users can participate on it. Authorization for poll creation can be handled by restricting poll creation to certain user groups. The phpBB import was updated to import phpBB polls (see Users Manual ► Polls on page 21 for more information).
• File attachments: Realized file attachments. Users can upload files to the server and attach them to posts. The file attachment system can be configured easily using the configuration tool (see Users Manual ► File attachments on page 22 for more information)
• Extend user profile: Implemented a possibility to extend the user profile. The user profile can be extended with an unlimited amount of additional fields which may be configured freely using a TypoScript configuration (see Administration ► Extending the user profile on page 32 for more information)
• Latest posts: Implemented the possibility to display a list of the latest topics. This means a list of the topics that was last written in. See Introduction ► How to install on page 5 for more information.
• Bug fixes: A lot of minor bugs were fixed. See the official mm_forum bug tracker on http://bugs.typo3.net for more information on which bugs were fixed.

Alpha 0.0.6¶

• Implemented a dynamic backend configuration form allowing a much easier installation. Administrators do not have to enter page and group UIDs in two different forms in the backend anymore. Instead, users have a very comfortable installation form in the backend module.
• Improved template handling by relocating custom design set folders to a directory outside the mm_forum extension directory.
• Improved RealURL support.
• Fixed some minor bugs (see mm_forum bug tracker on http://bugs.typo3.net )

Alpha 0.0.5¶

• Implemented a better RealURL support by fixing some bugs related to RealURL and adding an option to add more parameters to a url in order to generate nicer links (see section Administration ► mm_forum and RealUrl on page 36).
• Implemented the CHC Forum/CWT Community data import. See Administration ► Data import ► CHC Forum/CWT Community data import for more information. Credits to Nepa Design ( http://www.nepa- design.de/ ).
• The BBCode buttons that are displayed above a post creation form are now created dynamically in dependence of the BBCodes that were specified in the backend module.
• Implemented a better design template handling using different design sets (See Administration ► Changing Look and Feel on page Fehler: Referenz nicht gefunden)

Alpha 0.0.4¶

• Updated some MySQL-table and -field names to TYPO3 guideline conform values (like for example tx_mmpm_inbox to tx_mmforum_pminbox ). It is required to run the update wizard after upgrading to version 0.0.4 (see section Administration ► Updating )
• Implemented a FlexForm configuration for the mm_forum :: Forum plugin. Furthermore, the configuration of special listing pages was simplified. For the configuration of the mm_forum :: Forum plugin using FlexForms, see Introduction ► How to install on page 5. For more about special listing, see Administration ► Special listings on page 31.
• Added a possibility to limit the categories that are displayed to a certain predefined set of categories. This offers a functionality similar to multiple mm_forum instances, as it is described in the To-Do list (page Fehler: Referenz nicht gefunden).
• Added a possibility to display the users' real names in the post listing view, that can be enabled/disabled using the TypoScript constants (see Configuration ► Constants Reference ► Message board on page 41)
• Resolved a big problem denying users access to their own topics, furthermore some minor bug fixes (see mm_forum bug tracker on http://bugs.typo3.net )

Alpha 0.0.3¶

• Implemented a more flexible user rights administration using different fe_groups (see section Administration ► User rights management in the documentation, page 31)
• Implemented a function to automatically start an indexing process for the mm_forum :: Search plugin (see section Administration ► Search index in the documentation, page 30)
• Replaced the registration form with a table free layout (credits to Claudia Höhne )
• Some minor bug fixes (see mm_forum bug tracker on http://bugs.typo3.net )

Alpha 0.0.2¶

Some minor bug fixes (see mm_forum bug tracker on http://bugs.typo3.net )

Alpha 0.0.1¶

First release of mm_forum

0 See http://en.wikipedia.org/wiki/Cross- site_scripting for more details on this topic.

0 See http://www.php.net/strftime for more information

0 See http://www.php.net/date for more information

0 See http://www.php.net/htmlspecialchars for more information on quotation character replacement

0 See http://www.php.net/strip_tags for more information

0 See http://www.php.net/htmlspecialchars for more information

0 See http://www.php.net/htmlentities for more information

0 See TSRef, page 22 or http://typo3.org/documentation/document- library/references/doc_core_tsref/4.1.0/view/5/1/

0 See TSRef, page 75 or http://typo3.org/documentation/document- library/references/doc_core_tsref/4.1.0/view/8/6/

62