Khalat Jalal

This is an entry about our IPS Community Suite 4.2 release and features content specifically aimed towards developers. If you are not interested in developing for 4.2 you may wish to skip this entry. Don't worry we still have lots of exciting core feature announcements still to come. 
We are expanding on the already available REST API endpoints to include more support for nodes. This significantly increases the flexibility of the API and now allows forums, downloads categories, calendars etc. to be created programmatically via external sources.
 As is usual with the existing content item endpoints, access for nodes is configured via the admin control panel for each API key that is generated.

Configuring API Permissions via the Admin Control Panel
For those new to the REST API, documentation can be found in the developer resources section and within the admin control panel.

Endpoint Documentation
New endpoints in 4.2 include;
GET /core/groups - Get a list of groups GET /core/groups/{id} - Get information about a specific group DELETE /core/groups/{id} - Delete a group GET /forums/forums - Get a list of forums GET /forums/forums/{id} - Get information about a specific forum POST /forums/forums - Create a forum POST /forums/forums/{id} - Edit a forum DELETE /forums/forums/{id} - Delete a forum DELETE /blog/blogs/{id} - Delete a blog GET /calendar/calendar - Get a list of calendars GET /calendar/calendar/{id} - Get information about a specific calendar POST /calendar/calendar - Create a calendar POST /calendar/calendar/{id} - Edit a calendar DELETE /calendar/calendar/{id} - Delete a calendar GET /downloads/category - Get a list of downloads categories GET /downloads/category/{id} - Get information about a specific category POST /downloads/category - Create a category POST /downloads/category/{id} - Edit a category DELETE /downloads/category/{id} - Delete a category We are continuously looking for ways to improve developer functionality so if you have any ideas for additional endpoints or suggestions for improved documentation please feel free to share them in the comments below.
We are really looking forward to seeing the new and imaginative ideas 3rd party developers can create using these additional capabilities.
 

This is an entry about our IPS Community Suite 4.2 release.
You are probably already familiar with our content embedding feature in IPS Community Suite. When a link to content in the community is pasted into the editor (e.g. a topic, or a post, or a gallery image, etc.) it is automatically expanded into a preview of the content, usually with an accompanying image, allowing users to click through to that content if they are interested.

An embedded Gallery image in IPS Community Suite 4.1
While it has proved a useful feature to members, each embed used essentially the same structure - a small thumbnail on the left, a title, and a few lines of text. This works fine for topics, but isn't ideal for other kinds of rich content that might be posted.
In IPS Community Suite 4.2, we greatly improved upon our embedding handling, giving every type of content within every application its own customized embed style, allowing that content to be displayed however works best. This means larger high-res previews of Gallery images, a button to download a file right from the embed for Downloads files, showing a map for Calendar events, and so on. We worked to keep a consistent overall style between apps, but allow each to display its own relevant information.
For users, things will work exactly as they do now - they simply paste a link to content, and it will continue to expand automatically. The changes are also backwards compatible. Any existing embeds in your community will automatically show the new styling you see below - no rebuilding necessary.
So with that in mind, let's take a look what the new embeds look like! I won't show every single embed here because there's a huge number, but I'll try and give you a feel for how we approached the embed styles for each app.

Gallery Image

Comment on a Gallery Image

Gallery Album

Forum Topic

Downloads File

Review on a Downloads File

Calendar Event

Comment on a Calendar Event

Commerce Product

Record from a Pages database
I hope that gives you a good overview of what to expect when your users try out the new embeds for themselves. As always, please share your feedback in the comments below!
 

This is an entry about our IPS Community Suite 4.2 release.
When you have a diverse range of topics within your community, it makes good sense to separate topics within forums and categories. This will ensure that the viewer can find relevant content by scanning the list of forums first.
If you have a more focused community with fewer forums, presenting your community with a list of them can be daunting. This is especially true for less experienced visitors raised on social media.
Fluid forum view allows your visitors to get right to the meat of your community; the topics.
A fan site for a band is a good example of a community that will benefit with fluid view. There will likely be forums for album reviews, tour dates, general discussion and so on. Even though there are many forums, the common topic is the band. This makes fluid view ideal as your members can see all those related topics in one view. If your members wanted more specific topics, they could select a single forum to view.
Let us take a look at fluid view in action. We will then break it down and explain how it works in more detail.

 
The video shows the topic list and the forum filter box. As you can see, it is easy to change the topic list by changing the selected forums. This view replaces the traditional list of categories and forums.

 
Of course, you can permit your members to change the view to better suit their way of working.

 
You will notice a "grid" option. We have moved the grid forum theme setting into the main forum settings. This makes it an option for your members to choose, if the administrator permits it.

 
You have full control over the display options. This screenshot shows that the control panel option to choose the default view. There is also an option to control which views your members can select. You may also decide to not allow your members to switch views at all. This will ensure that they all use the view you choose.

 
You may have spotted that forum names have a colored background in some screenshots. We added the ability to define a feature color per forum. This feature color helps the forum stand out in a more visual way. This is especially useful when you select many forums in a single view.

 
This feature color also works on the table view.

 
We added a feature color hint to topic view to enforce the association between the forum and its color.
 

 
This screenshot also shows the removal of the forum breadcrumb in fluid view mode. Fluid view remembers your last forum selection so you don't lose your place when you go back to the listing.
The benefit of this feature is easy to see. It removes a potential barrier of entry for your audience. It puts the spotlight on topics themselves, and not the hierarchical forum structure. Your members will enjoy viewing many forums at once and switching between them without leaving the page.
We hope that fluid view is an asset to your community and your members enjoy this new functionality.
Technical notes.
The database stores the members' view choice. This remembers the selection across devices. Guests are not permitted to change between views.
 

This is an entry about our IPS Community Suite 4.2 release
In previous versions of IPS Community Suite we have had an account history feature in our Commerce application. This feature showed many important actions that may be relevant to the customer such as when an invoice was generated or when a customer changed their account details.
In IPS Community Suite 4.2 we have expanded this functionality and moved it into the core functionality of the suite.

Member History Member Overview
Member actions that will be logged include (but are not limited to)
Email address change Display name change Password change Account merge Primary group change (The reason will be shown when triggered by an automatic group promotion) Secondary group change Flagged/Unflagged as spammer Multi-Factor Authentication (Enable / Disable / Opt-out) Social media (Twitter, Linked In, Facebook, Google, Twitter, IPS Connect) for enabling, disabling and which (if any) were used to register an account. The Commerce customer account page will now show actions that may be related with a transaction or account.

Member History on the Commerce customer view
Discoverability
Each action is also discoverable via the IP Address tools built into IPS Community Suite 4

Member History in IP Search
We’ve also made the data table filterable

Member History Search
Notes for developers:
The new Member History system has been designed with interoperability in mind. In IPS Community Suite 4.2 you will be able to integrate your own applications into this system. Member History replaces the display name changes system.

This entry is about our IPS Community Suite 4.2 release
In 4.1.18 we added Two Factor Authentication. Already in 4.2 we have announced a new setting to trigger 2FA when logging in from a new device, and in 4.2 we are also adding Authy as an authentication handler.
Authy can send a user a text message, make a phone call, or send a push notification to a smartphone app to authenticate the user. You can enable whichever of these options you like.
 
Set Up
To set up Two Factor Authentication with Authy, the user will enter their phone number. To verify their phone number they will then enter a code shown in the Auhy app or have a code sent by text message or phone call. The system will automatically show an appropriate interface based on what options you have enabled - for example, if you don't want to enable the app as an option, it will not reference Authy.

Setting up Authy with the app available as an option

Setting up Authy with just phone or text message options enabled
 
Verification with Authy
When the user needs to verify their account, the system will automatically show an appropriate interface. If you allow verification with the Authy app and either it is the only option you allow, or the system knows that the user has installed the Authy app, the system will prompt them to use the app. This can either be done using Authy's OneTouch option (where the user will receive a push notification to the app, and when they click approve, the screen will automatically refresh) or their SoftToken option (where the user will be instructed to open the Authy app and enter the code they see). If you allow authentication by text message and/or phone call as well, the user will also see options for using those instead.
These screenshots show the process for OneTouch authentication:

The user is shown a waiting screen
 
Simultaneously they will receive a push notification and when opening it be able to approve
Once the user has approved, the waiting screen will automatically refresh with the user authenticated.
For SoftToken authentication, the user is prompted to enter the code shown in the Authy app:

Authy SoftToken option
 
Phone Verification
If you have disabled the Authy app as an option, or the user does not have it installed, they will be prompted to choose from the available options how they want to authenticate.
These screenshots show the process for authenticating by text message:

The user is asked how they want to authenticate

The user receives a text message or phone call with a code

The user enters this code to authenticate
 
Management
If the user changes their phone number they can reconfigure the system in their account settings. The system automatically shows "Phone Verification" rather then "Authy" if the app is not available as an option.

Account Settings showing Authy as Phone Verification