...be in the files as well, including version information, author and package id. Packages should not be double archived or double foldered. ...rmation displayed in this file is important - particularly the id, package id, name, and contact information. There are two different versions of this fi

...d in and to refer to cookie then session, otherwise it represents the user id. ...nting the member's name (since that is guaranteed to be consistent, member id is not)

{{ambox | text = This page is a work in progress of the new features that are available in SMF 2.1}} == New features for users ==

* When a column is an ID, it should prefixed with ‘id_’ as in ‘id_member’. * ID and class names should be lower case.

...re written. Code has been restructured for greater efficiency, several new features have been added (which make certain mods obsolete), etc. Due to the volume ...QL features (eg. '''ON DUPLICATE KEY UPDATE'''). If you stick to SQL92 SQL features, you can be assured that your mod ''should'' work on the majority of modern

This is located in Features and Options -> Layout and Options or Server Settings -> General in RC1 and ...hines.org/community/index.php?topic=76249.0 Ben has a post about disabling features according to server load here] in the GUI for SMF 2.0 RC2====

$helptxt['featuresettings'] = '<strong>Features and Options</strong><br> There are several features in this section that can be changed to your preference.';

...rmit other {{llink|SMF1.1:Membergroups|text=membergroups}} to access these features via the {{llink|SMF1.1:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.

...rmit other {{llink|SMF2.0:Membergroups|text=membergroups}} to access these features via the {{llink|SMF2.0:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.

...rmit other {{llink|SMF1.1:Membergroups|text=membergroups}} to access these features via the {{llink|SMF1.1:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.

...rmit other {{llink|SMF2.0:Membergroups|text=membergroups}} to access these features via the {{llink|SMF2.0:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.

...rmit other {{llink|SMF2.1:Membergroups|text=membergroups}} to access these features via the {{llink|SMF2.1:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.

...rmit other {{llink|SMF2.1:Membergroups|text=membergroups}} to access these features via the {{llink|SMF2.1:News_and_newsletters|anchor=Settings|text=settings}} *<code>{$member.id}</code> - The current member's ID.