Matt

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.

Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.

Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.

Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.

We are excited to announce the Leaderboard as the latest all new feature of IPS Community Suite. The new Leaderboard is designed to better highlight your most active members and content based on reputation and other metrics. The Leaderboard will greatly enhance both member and content discovery on your community.

Leaderboard Home
First you will notice the new feature of member leaders based on a specific time frame. In the example above it is set to All Time showing those members with the most reputation overall on your community. It also shows the content with the most reputation for the same timeframe so you get a snapshot of both popular members and popular content in one view.

Past Leaders
The Past Leaders tab shows the "winners" of each day in a history. The system counts all reputation made each day and logs the members who had the top reputation counts that day. Using reputation rather than post count encourages your members to post quality of quantity which is really important to any site.

Winner Profile Badge
Those who win the day also get a badge on their profile page to highlight that they were the member with the most reputation for a particular day.

Top Members
Top Members shows you a list of all members sorted by various metrics. By default you will see members sorted by reputation but you can also easily sort by total post content Suite-wide or per-app. All of these views can be linked directly to so if you wanted a menu item to show members who post the most files in Downloads you can just directly link to that sort view.

Leaderboard Settings
There are various settings to control the default behavior of the Leaderboard. You can define the default view and how many members to show which is helpful to tailor it to your needs.
We hope you enjoy this initial launch of the new Leaderboard feature. We are excited about the new content and member discovery abilities this offers and look forward to adding new options to the Leaderboard as we continue to develop!
 
This change will be in version 4.1.17 which is scheduled to be released in early December 2016.

We are changing the existing Profanity Filters feature to become the new Word Filters feature. This change will allow you to define words that will initiate a moderator review before content is posted. With creative use of this new feature you can actually have the Suite self-moderate certain posts.
Right now the Profanity Filters are pretty basic. If you enter "stopword" you can have it change to *****. That's fine for basic profanity but sometimes you want to do other actions with a word. Perhaps someone might mention a competitor, you see common spam words, or you run a site targeted to children and want fine control over what is posted. There are a lot of reasons a simple replace word with *** might not be what you want.
Word Filters introduce an option to let you say "stopword" places a post in moderation queue.

Word Filters
So now you can define a list of words that are not necessarily profanity but are words you want to review if they are posted.
We have also extended this logic to the URL Filters which are now just called Links in the AdminCP configuration. You can now disallow all links and have a post go to approval if someone does post a link. This is also useful for sites where you need really tight control on content either for security or privacy reasons.

Link Options
With the new Links feature you can also set allow/disallow list of allows links and if someone posts a link outside those lists (depending on your mode) the post will go into review.
We hope these features allow you to introduce a bit of automatic moderation to your community and you can come up with creative ways to capture posts that need review either for security, privacy, or just keeping things in order.
 
 This change will be in version 4.1.17 which is scheduled to be released in early December 2016.

There are now two ways to get outbound RSS feeds in IPS Community Suite: Activity Streams and a new Custom RSS Feeds feature we are introducing.
Every Activity Stream you create also creates a related RSS feed. However, Activity Streams take into account recent activity and unread status per-user which you may not want if you want a simple, raw feed of content by date. The new RSS Feeds feature uses similar filter settings to Activity Streams but does a traditional by-date approach to the feed. It also only reports on the initial creation of a content item and does not update based on replies.

Configure RSS Feeds
You can finely select various content settings including selecting just certain categories within an application. So you might create an RSS feed that includes only content from an announcements forum and your blog section which would then be a total feed of all the news on your site.
RSS feeds are useful in the traditional sense for people to subscribe to a feed on your site but they are also useful for integration. Many clients use RSS feeds to pull content into external sources to embed content on a different site, mobile app, or other systems. For those of you looking for even tighter integration with external systems, be sure to check out our REST API.
 
This change will be in version 4.1.17 which is scheduled to be released in early December 2016.

In line with our aim to make incremental improvements in each release, I wanted to go over a few of the small but useful changes to the personal messenger that you'll find in our next release, 4.1.13.
 
Read/unread filtering
The first improvement is that you can now filter the message list by read and unread, making it a little easier to browse through just the messages you're interested in.
 
Search improvements
Next up, the messenger search has been improved in a couple of ways; first, you can now also search the names of both the recipients and the senders, and second, we've added a menu so you can specify which fields in particular you want to search by.
 
Easier moving
Finally, we've added a popular request - the ability to use the mass-move tool inside the messenger. You can now check multiple messages, and the usual mass-action toolbar will appear that will allow you either move them to another folder, or, has been the case in the past, delete them.
 
While these are each small improvements by themselves, we hope the incremental changes in each release add up to a more pleasant experience for users. 

Our Pages CMS is one of our most popular applications as we are continuing to improve it based on feedback. New in 4.1.13 includes:
Designer’s Mode HTML Editing
This update allows you to edit your HTML mode pages inside the designer's mode file system. Any edits you make, once saved in your text editor are instantly available which makes it much faster to build HTML pages with Pages.

 
Database Template Improvements
We listened to a lot of feedback about templating within the AdminCP for Pages and one common request was for a way to delete a group of database templates and to rename those groups. When you import databases, the template group names are created unique but you may want to change this to something more memorable. You will see here that the dialog also shows you which databases this template is used.

 
Page titles when using databases
Currently, when you add a database to a page, the page title is replaced with the database name. This may not always be desirable, and you may want the page title to remain in all database URLs (such as record view). There is now an option for this per database.

Relational Field Improvements
Now when you create a relational link between databases, you can opt to show which records link to the relational record. To give you an example, say you had a database for actors, and a database for movies, and you created a link on the actors record to show which movies they star in; now when viewing the movie, it will show you a list of the actors.

 
More Filterable Fields
We added both "Date" and "YesNo" field types to be filterable when viewing a list of records. When you use the Date type, you can select a date range for listing articles.

We also added the ability to use any custom field set as filterable to be used when creating a database feed widget.

 
Unique Fields
Another popular request was to allow a way to force unique entries for custom fields. This means that when enabled, only one record per database can have the same value. This is enabled when creating or editing a field.

 
Other improvements
You can now quickly delete an entire media folder via the AdminCP.

You can now quickly see which databases are used on which pages via the AdminCP page list.

 
And we added a way to programatically fetch a custom field value via the $record object. Currently, you need to use something like $record->field_12 which works well until you import that database to another installation. The fields are renumbered so this syntax no longer works. We made it possible to use the field key like so $record->field_{my_key_name_here}. Not only does this solve the issue when importing databases, it is also much more readable and easier to remember!

Recently, we had a post in our pre-sales forum that asked how to achieve a few different things with Pages. One of the questions asked was if it was possible to show topics from a particular forum in each database record. While Pages can create a topic for each record for you, there's no way to associate an entire forum with a record.
In my reply, I indicate that you'd need to have a forum ID stored with each record in a custom field, and then use PHP to interact with our API to pull the topic list.
As it turns out, however, there's an easier way that I discovered after some experimentation. In hindsight it's obvious, but I want to share it here because it could open up some other interesting possibilities with some creative uses.
Setting up blocks
The first thing we need to do is create our blocks. We're going to create a block for each of our forums. You can set whatever parameters you want here, but the important thing is that they're named consistently using the forum ID. So, for my forum ID 2, I've named the block forum_2. This will allow us to include our blocks later.

Creating one of the blocks we'll need
 
Adding the field
Next we'll need to create a field in our Pages database that will be used to set the forum ID that is going to show in each record. For simplicity, I'm creating a Number field and I'll enter the forum ID manually, but if you wanted to go further, you could create a Select Box field, with the key being each forum and the value being the name. This would give you a friendlier input from which to select the forum for each record.
Here, though, I've just created the Number field, and named it Forum ID.

Setting up the database field
 
Using the field formatter to show the correct block
Finally, we'll use the Field Formatting options to show the correct block based on the forum ID entered for each record. On the Display Options tab, I'm going to hide the field from the listing template, but show it on the display template. I've selected Custom as the format, then entered this format:
{{if $formValue}} {block="forum_{$formValue}"} {{endif}} That's it - that's all you need for this to work. It's very simple. All we're doing is passing the $formValue of the field (which is the raw value) into the {block} tag as a variable, so that the block that is rendered depends on this value. As long as a block exists with the correct key, it'll be shown in the display view:

End result, with the correct block pulled in based on the ID we provided to the record
 
Going further
So, given that we know we can use variables in block names to pull in different content (providing the block has been created ahead of time), what other possibilities are there? For starters, we aren't just restricted to using field formatters. Instead, we could use blocks directly in the database templates, using some of the data available there.
Here's one idea - if you have just a few staff members posting records, you could create a block for each staff member that lists their recent posts, status updates, etc. In your database template, you could include the correct block by doing this:
{block="content_for_{$record->author()->member_id}"}  
I hope this relatively simple approach gives you some ideas for more creative ways to use blocks. If you have any suggestions for other ways to use this approach, please let us know in the comments!

Security should never be an afterthought for your community. All too often, site owners consider beefing up their security only when it's too late and their community has already been compromised. Taking some time now to check and improve the security of your community and server could pay dividends by eliminating the cost and hassle of falling victim to hacking in the first place.
Let's run down 7 ways that you can protect your community with the IPS Community Suite, from security features you may not know about to best practices all communities should be following.
 
1. Be selective when adding administrators
Administrator permissions can be extremely damaging in the wrong hands, and granting administrator powers should only be done with great consideration. Granting access to the AdminCP is like handing someone the keys to your house, so before doing so, be sure you really trust the person and that their role requires access to the AdminCP (for example, would moderator permissions be sufficient for the new staff member?).
Don't forget to remove administrator access promptly when necessary too, such as the member of staff leaving your organization. Always be aware of exactly who has administrator access at any given time, and review regularly. You can list all accounts that have AdminCP access by clicking the List Administrators button on the System -> Security page.
2. Utilize Admin Restrictions
In many organizations, staff roles within the community reflect real-world roles - designers need access to templates, accounting needs access to billing, and so forth. IPS4 allows you to limit administrator access to very specific areas of the AdminCP with the Admin Restrictions feature, and even limit what can be done within those areas. This is a great approach for limiting risk to your data; by giving staff members access to only the areas they need to perform their duties, you reduce the potential impact should their account become compromised in future.
3. Choose good passwords
This seems like an obvious suggestion, but surveys regularly show that people choose passwords that are simply too easy to guess or brute force. Your password is naturally the most basic protection of your AdminCP there is, so making sure you're using a good password is essential.
We recommend using a password manager application such as 1password or LastPass. These applications generate strong, random passwords for each site you use, and store them so that you don't have to remember them.
Even if you don't use a password manager, make sure the passwords you use for your community are unique and never used for others sites too.
4. Stay up to date
It's a fact of software development that from time to time new security issues are reported and promptly fixed. But if you're running several versions behind, once security issues are made public through responsible disclosure, malicious users can exploit those weaknesses in your community.
When we release new updates - especially if they're marked as a security release in our release notes - be sure to update as promptly as you can so you receive the latest fixes. Your AdminCP will also let you know when a new version is ready for download.
5. Use .htaccess protection for your AdminCP
In addition to IPS4's own AdminCP login page, you can set up browser-level authentication, giving you a double layer of protection. This is done via a special .htaccess file which instructs the server to prompt for authentication before access to the page is granted. IPS4 can automatically generate this file for you - simply go to System -> Security in your AdminCP, and enable the "Add a secondary admin password" rule.
And it should go without saying, but to be clear: don't use the same username or password for both your .htaccess login and your admin account, or the measure is redundant!
6. Restrict your AdminCP to an IP range where possible
If your organization has a static IP or requires staff members to use a VPN, you can add an additional layer of security to your community by prohibiting access to the AdminCP unless the user's IP matches your whitelist. This is a server-level feature, so consult your IT team or host to find out how to set it up in your particular environment. If you're a Community in the Cloud customer, contact our support team if you'd like to set up this protection for your account.
7. Properly secure your PHP installation
Many of PHP's built-in functions can leave a server vulnerable to high-impact exploits, and yet many of these functions aren't needed by the vast majority of PHP applications you might run. We therefore recommend that you explicitly disable these functions using PHP's disable_functions configuration setting. Here's our recommended configuration, although you or your host may need to tweak the list depending on your exact needs:
disable_functions = escapeshellarg,escapeshellcmd,exec,ini_alter,parse_ini_file,passthru,pcntl_exec,popen,proc_close,proc_get_status,proc_nice,proc_open,proc_terminate,show_source,shell_exec,symlink,system Another critical PHP configuration setting you need to check is that open_basedir is enabled, especially if you're hosted on a server that also hosts other websites (known as shared hosting). If another account on the server is comprised and open_basedir is disabled, the attacker can potentially gain access to your files too.
Naturally, Community in the Cloud customers needn't worry about either of these steps - we've already handled it for you!
 
So there we go - a brief overview of 7 common-sense ways you can better protect your community and its users. As software developers, we're constantly working to improve the behind-the-scenes security of our software, but as an administrator, there's also a number of steps you should take to keep your community safe on the web.
If you have any tips related to security, be sure to share them in the comments!

When IPS4 encounters an error (be it a simple 404 Not Found or a more complex configuration issue), the user sees a standard built-in error page. That's fine in many cases, but did you know you can create your own error page using our Pages app?
This is a particularly good approach for communities that use Pages for their website too. If you have built a website theme, the standard error page may not fit with your visual style, so building your own error page allows you to improve it. You might want to show some helpful links to other parts of your website, for example.
 
Creating your error page
The first step is creating your error page in Pages. Note that for this page, you must create a manual page - the Page Builder tool can't be used in this case.
In order to show the error on your page, there's two special tags you should insert in the page content. When your page is shown in response to an error, Pages will swap out these tags for the relevant text. They are:
{error_code}
Replaced with the technical error code for this error. This code identifies the exact piece of code that triggered the error, and can be given to IPS support technicians to help diagnose problems. {error_message}
Replaced with a human-friendly description of the error that occurred.  
Configuring Pages to use the error page
Next, set Pages to display the error page. You do this in the Pages section; click the Advanced Settings button, and select your page from the list. Note that this will replace all error pages across the suite - not just errors triggered by Pages itself!
 
Have a request for a theme tip? Let us know in the comments and we'll try and help out in a future tip! 
 

When you use custom templates for a Pages database, you'll often need custom CSS to go along with it to provide the styling. There's two main ways of doing this:
CSS files within Pages
Pages allows you to create CSS files, and then associate them with particular custom pages of your community (you create these in the AdminCP, under Pages > Templates > CSS). So simply create your CSS file, and associate it to the page that your database is displayed on.
The benefit of this method is it applies to all themes, so it's great if you want your database to look the same on all themes. Of course, this is also the drawback - you can't easily use it for per-theme customization.
Targeting the database classname in theme CSS
Alternatively, you can target the database classname in your normal theme CSS files. When a database is inserted into a page, IPS4 helpfully adds a classname to the body element, which makes it really simple to style that page in particular. If your database key is myDatabase, then the classname added to the body element would be cCmsDatabase_myDatabase. Use this in your selectors and you can style everything exactly how you need:
.cCmsDatabase_myDatabase .ipsButton_important { /* Style important buttons differently in this database, for example */ } Combine both methods!
Of course, you can use both approaches when it makes sense. Create a CSS file within Pages for the basic structural styling that will apply regardless of which theme the user uses, and then in each theme target the database classname to customize it for that particular theme - perfect for the colors, font family and so on.