• Introducing Community Content System
• Blocks Overview
• Pages Overview
• Media Manager
• Templates

{parse template="header_template" group="ccs" params=""}

You can even include skin templates within your page templates, just like you would within forum skin files.

Using page templates with pages

With your page templates created you would add a new page using the page manager. On the first page of the wizard, select to use one of your page templates (such as your single column page template). You then have the capability to edit the entire page, or only the page content - this option allows you to either "import" the page template and edit the entire page area (if you select no), or edit only the content that should be placed within your page template appropriately (if you select yes).

If you edit only the page content (the preferred method in most cases) any future changes to the page template will automatically be inherited by the page; otherwise, you would need to update the pages individually. This allows you to decide if you want a system where changes to templates are inherited by pages automatically, or if you want to instead use page templates as a starting point but ensure each page is edited and updated independent of every other page. If you elect to edit the content of the page only, when your page is saved the page content is placed within the page template where you specified when editing the template, the page is compiled and pieced together, and the page is then ready to be displayed.



Page templates are an extremely simple yet extremely useful feature designed to help facilitate quick production and deployment of pages on your site. You don't even have to make use of page templates if you want, but we believe once you start using them you will see just how much time it will save you in the long run.

• Recurring subscription cancelation immediately ending subscription and demotes member
• Multiple currency issues
• Inaccurate reporting of totals
• Incorrect end date calculation after upgrading
• ...and many more
  

• Pre-installed hook to display current subscription settings (You are subscribed to package X which runs out in X days)
• Force the user to cancel a current recurring subscription before upgrading to another
• Ability to renew a subscription before it expires (ACP configurable).
  

• Several areas have been changed to fit in with the look and feel of IP.Board 3.0.
• IP.Tracker now supports the option to return to the issue listing the issue was originally in when replying to an issue.
• Each status can now have a 'canned message'. If you update a report to a status with a canned message, but do not provide a reply yourself, IP.Tracker will automatically insert this canned message for you.
• Statuses can now be marked as 'fixed statuses'. If you change the status of a report to a 'fixed status' but forget to fill in the Fixed In version, IP.Tracker will automatically scan the versions for that particular project and mark the fixed in version as the latest version available
• Each issue now contains its own timeline view. As the name suggests, this view will provide a brief history of the issue. It will outline important changes in the issues history such as status, severity, and version changes. We implemented a change in IP.Tracker 1.2 in preparation of this new view, so that the timeline view has a lot of data to already work from!

• Mini-calendar
• Poll
• Welcome block
• Online friends
• Online users
• Watched content

• RSS
• Forums
• Members
• Calendar
• Blogs
• Downloads
• Gallery

• Featured blog entry block
• Latest topics block
• Top posters block
• Random gallery images block
• Upcoming calendar events block
• Latest news from CNN

$this->registry->output->addMetaTag( 'name', 'content' );

This is used internally to add a meta tag for 'indentifier-url' and 'description'. The description is the first post of a topic; a forum description or the user's "About Me" information using the signature if no "About Me" information is present. You can use this interface in your own code to add more tags if desired.

Robots.txt
A primary concern for those interested in SEO is duplicate content. There are many ways to access a single topic due to the different variables that are used; pagination and search strings are a few examples. To help limit the duplicate pages indexed, IP.Board now ships with an example "robots.txt" file for you to edit and upload to your root directory.

Redirecting 'old style' links
Another concern was that the old style links, for example: index.php?showtopic=10, are still able to access pages. This is necessary so that you do not lose bookmarks or traffic from currently indexed links. You can now choose to redirect with an optional "301 Moved Permanently" header to the new link format. This is transparent to the end user but will help search engines locate the correct copy of your content.

Incorrect Permalink Handling
The new friendly URLs are often based on user generated content. For example, a topic called "My Great Topic" will have the permalink "/topic/10/my-great-topic/". Now, when this topic title is edited, the permalink will change too. For this reason IP.Board allowed access to the topic as long as the topic ID was present, so all of the following links resulted in the same topic being shown:

/topic/10/my-great-topic/
/topic/10/my-edited-topic-title/
/topic/10/
/topic/10/i-just-made-this-up/

The downside to this is that some may consider this duplicate content. You can now opt to redirect with a "301 Moved Permanently" header to the correct permalink. This again is transparent to the end user but it will help search engines locate the correct copy to index. You can also opt for IP.Board to simply add a 'robots' meta tag with the value 'noindex' if you do not wish to redirect. This will tell the search engine to not index that URL.

We hope that these improvements will be seen as a good first step in basic SEO without impacting performance.

1. You must first register an "application" on Facebook's website pointing to the integration file included with IP.Board 3. You then must enter some basic keys that Facebook provides in your ACP.
2. Users will have the ability to use Facebook Connect to login to your site. They will also have the ability to either associate their Facebook account with an existing IP.Board account, or create a new IP.Board account.
3. Basic profile data such as avatar, profile picture, "About Me", and status will be synced to IP.Board from Facebook

• PHP v5.1.0 or higher (5.2.0 or higher preferred)
• MySQL 4.1 or higher (5.0 or higher preferred)
• SPL, GD2 and libxml2 PHP modules installed

• Upload the file to your server somewhere that is web accessible. For example, you can upload the file to your forum root directory where "conf_global.php" is located.
• Visit the file in your webserver. For instance, visit http://yoursite.com/forums/check_requirements.php (replacing yoursite.com/forums/ with the appropriate domain and path to the script you just uploaded).
• Verify there are no "FAIL" marks reported. If there are any items that fail the check, you will need to consult with your host about updating your server, moving you to another server that supports all of the requirements for IP.Board 3, or contacting another host that does.

• Option to "ban" a member permanently from the warn panel
• Increase or decrease warn value by a custom value (rather than just +1 or -1) for super moderators only
• Ability to unapprove (hide) all member's posts and/or topics made with the last X days/hours
• Member's current reputation and other general information now displayed on warn panel