Cyboman

Social media promotion should be a part of any marketing strategy. Curating interesting content from your community and sharing to social media channels like Facebook and Twitter is a great way to drive traffic to your site.
Invision Community 4.2 introduced Social Media Promotions to allow this. 
You hit the promote button, fill out the text to share with each service, click which photos to include and schedule the promotion or send it immediately.
We use this feature almost every single day to share highlights to our Invision Community Facebook page and Twitter.
This feature has had a significant impact in attracting visitors to our blog. This is now a core part of our marketing strategy.
So what's new in Invision Community 4.3?
Facebook Groups and Pages
A  popular feature request was to allow sharing to Facebook groups that you are an administrator of, as well as Pages you own.
Not only that, but we now allow you to share to many places at once.
When setting up Facebook, you can choose which Facebook properties to be used when promoting.

 
When sharing content, you can choose where to share it to right on the dialog.

 
Here you can see that we're sharing to two of three possible places. "It's a secret" is a Facebook Group (which makes it a pretty poor secret).
The "Lindy Throgmartin Fan Club" is my favourite page on all of Facebook. What it lacks in members, it makes up for in enthusiasm.
You may also notice that the Facebook box is empty. Facebook have very strict guidelines on sharing content. They prefer that you do not auto-populate the content.
You can always access the item's original content on the promote dialog, so you can refer to it.
Setting a custom page title
When you share to social media channels, you also have the opportunity to add to the 'Our Picks' page.
We've made it possible to add a custom title for the Our Picks page so you don't have to use the content item title, although this is still the default.

 
Editing an Our Pick
When editing an item shared to 'Our Picks', you now have the option of editing all the data, including the title and the images attached.

 

The Our Picks page showing the custom title
Thanks to your feedback, we saw several places that we can improve this already popular feature.
We hope you enjoy these changes which makes your social promotion strategy even easier to execute.
I know we'll be making good use of them!
 

Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

New AdminCP Member Page
Let's look at some of the improvements:
Easy Toggle between Member and Customer View
If you have Commerce installed, you can now toggle between "Member View" (which shows the screen above) and "Customer View" (which shows the current customer page in Commerce with the user's purchases, invoices, etc.). This makes it much easier to view all of a member's information in one place.
If you don't have Commerce installed, the top tab bar will not show.
Basic Information
The pane in the top-left shows the member's basic information like name, email address and photos. You can now reposition a member's cover photo and crop the profile photo (functions previously not available in the AdminCP). To change the display name or email address, you just click and hold on the information and a textbox appears. The buttons below allow you to merge, delete, sign in as, and edit the preferences or password for the member.
  
Basic Member Information Pane
In addition, this pane lists any social networks the user is logged in with. It shows you the member's profile photo and profile name on that network (for example in this screenshot, it is showing my Facebook profile's photo and name) and for many networks you can click on this to be taken directly to their Facebook/Twitter/etc profile. You can also edit the syncing options for the method and unlink the accounts, features which weren't available previously.
If you have Commerce installed, there is also an indicator if the user has an active subscription.

A member with an active subscription
 
Alerts
If a member is validating, banned, flagged as a spammer, or locked, a large banner will display drawing your attention to this. For validating and banned, it will explain exactly what the status is (for example, if they haven't responded to the validation email yet versus they are awaiting admin approval, or if they have been banned manually versus are in a group without permission to access anything).

A member that has been locked



Other possible alerts
 
Locations & Devices
This pane shows you, on a map, all of the locations the user has been when using the community (based on their IP address) as well as the IP address they used to register and most recently.

IP Address Locations
While the devices tab shows the most recently used devices.

Recently Used Devices
 
Content Statistics
Right in the middle of the profile you can see some statistics about the member's activity. This includes:
A sparkline graph of their recent content. Their content count and reputation count (with tools to manually change or rebuild). A breakdown of the amount of content they have made across all applications. A visual indication of how much of their messenger and attachment storage they have used. If Gallery and Downloads are installed, the existing statistics overview provided by these apps are also available here.
Content Statistics
Warnings & Restrictions
This block shows recent warnings on the account, and also highlights if any restrictions (i.e. content moderation, restricted from posting, or application-level restrictions) are being applied, which previously was difficult to see at a glance.

Warnings & Restrictions Block for an account which has content moderation in effect
 
Account Activity
On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
Recent Account Activity
 
Extensibility
The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.

Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

Uploading a video
When viewing an uploaded video, if it is in a format that the user's browser and platform natively supports, it will show an embedded player. This will have all of the features supported by the operating system - for example, almost all browsers support fullscreen, and Safari supports Airplay and picture in picture.

An uploaded video
If the video is in a format not supported, it displays exactly as it does now - as a download link.

An uploaded video in a browser without playback support for that format

"The world’s most valuable resource is no longer oil, but data", the Economist wrote recently.
Invision Community software stores a lot of important data that can be leveraged to analyze and improve upon the traffic and interactions with your site.
While there are some various statistics tools in the AdminCP already, we spent some time with 4.3 enhancing and improving upon our existing reporting tools, as well as adding some new analytics tools you may find useful.
Chart Filters
Beginning with 4.3, any dynamically-generated charts in the AdminCP that support filtering will allow you to save those filter combinations for easier access in the future. When you open the Filters menu and toggle any individual filters, the chart will no longer immediately reload until you click out of the menu, and 'All' and 'None' quick links have been added to the filters menu to allow you to quickly toggle all filters on or off.
Here is the 'Sales' chart for Commerce, for example. You will see that the interface is now tabbed.

Commerce's Sales chart
After opening the 'Filters' menu, selecting all of my products named 'test', and saving this filter combination as a new chart, I can quickly come back to this chart in the future.

Specific filter configurations allow you to run reports easily
Note that each user can save their own chart filter configurations independent of other users.
Top income by customer
Speaking of Commerce, we have also added a new chart to the 'Income' page, allowing you to view reports of your top customers. As with other dynamic charts, you can save filter configurations here for easy future access, and you can view the results as a table to get a raw list of your top customers' purchases. Further, we have tidied up the table views for the other existing tabs on this page.

Looks like brandon is my top customer
Reaction statistics
We have introduced several statistic pages to expose information about the Reactions/Reputation system and how your users are interacting with it. For instance, you can now view information about usage of each of the reactions set up on your site.

Yes, I'm definitely confused a lot
You can also see which users give and receive the most reputation (which is the sum of their reaction points, keeping in mind that negative reactions can reduce a user's total reputation score), you can see which content on your community has the most reputation (which might prompt you to promote it to the 'Our Picks' page, promote it to social media, or otherwise continue to encourage interaction with the content), and you can see which applications reactions are given in the most. This could allow you, for instance, to focus more efforts in areas of your site to drive more activity, or to foster activity in areas you did not realize were as active as they are.

Some areas of the community aren't as active as they could be
Additionally, when viewing user profiles on the front end you can now see a breakdown of which reactions each user has given and received when you click the "See reputation activity" link in the left hand column.

Apparently I'm not so much confused, as I am confusing
Tag Usage
Another useful statistic introduced with 4.3 is the ability to review tag usage on your community. As with other dynamic charts, you can filter however you like and save those filter configurations for easy future access.

Not all tags are equal
Trend charts for topics and posts
When viewing the New Topics and New Posts charts, there are now tabs for "New Topics by Forum" and "New Posts by Forum", allowing you to see which of your forums are the most active. Additionally, you will see a trend line drawn on the chart to show you the trend (e.g. whether activity is increasing or decreasing). You can also filter which forums you wish to review, so you can compare your most active forums, the forums that are most important to your site, or the forums that need the most attention/may not be relevant, for instance.

Viewing new topics by forum

New posts by forum, but viewing only a subset of my most important forums
Other Improvements
Some other miscellaneous improvements have been introduced as well, which you may be interested in:
When viewing Member Activity reports, you can now filter by group. We have also added the content count column to the table so you can quickly sort by top posters if this is relevant to the report you are running. Device usage is now also tracked (mobile, desktop, etc.) and can be viewed on a new Device Usage page. Developers: Dynamic charts now support database joins

We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
Paid Club Memberships
If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

Paid Club Settings
If enabled, the club directory will show the price for membership in each club.

Club directory with paid clubs
The process for joining works a little differently depending on the type of club...
For open clubs, the user will immediately be prompted to pay the joining fee. Once they have paid, they are added to the club as normal. For closed clubs, the user will need to request to join as normal. Once they have been accepted to join the club, they will then be able to pay the membership fee, after which they'll be added to the club. For private and read-only (a new type in 4.3, which we'll talk about below) users have to be invited to join the club Public clubs have no membership, and so cannot be paid.
Joining a paid club (a closed club in this screenshot)

Paid club after request to join has been accepted

Paying for club membership
Club leaders can also waive the membership fee, allowing certain users to join the club for free.

Waiving fee when approving request to join

Waiving fee when inviting members

Waiving renewal fees on an existing member
If a member fails to pay their renewal charge, they are moved into an "expired" state. The club leaders can see the status and renewal date for all members, and use the filter tools to just see active or expired members.

Club members management
Paying out membership fees works just as it does with paid files in Downloads. Users receive the amount as account credit. If enabled, they can then request a payout of this via PayPal or a manual payout method you want to use.

Viewing an invoice in the AdminCP where some payment has been given to a member

Viewing account credit with options to withdraw funds
 
 
Club content throughout the community
Currently content in clubs is only visible within the club itself. In 4.3 a new setting allows you to show the content from clubs throughout the community - for example, if a club contains a forum, that forum can show in the main forum list.
 
Club forums showing on main forum list
This is a single toggle: if enabled, all content from clubs that each user has joined will show throughout the community, appearing below the normal categories/etc in that application.
 
 
New Club Type: Read Only
In addition to Open, Closed, Private and Public, we have added a new club type in 4.3: read only. In a read only club, everyone can (without joining) view everything in the club, but cannot participate unless they are invited by a club leader.
 
Following
Users can now follow a club, and will then receive notifications about all new content in the club - the same as if they followed every content area in the club.
 
List View
In addition to the current grid layout of clubs, there is a new list-style.

Clubs List View
The admin can choose which views are available and what the default should be.
 
AdminCP Approval
You can now filter the list of clubs in the AdminCP to clubs requiring approval and approve clubs from within the AdminCP.

Approving clubs in AdminCP
 
Deleting Content Areas
Club leaders can now delete content areas within their clubs. This can be useful if, for example, the leader added a club feature by mistake.
Content areas can only be removed if there is no content within it, or if you have granted club leaders the ability to delete content in their clubs (since they would be able to empty it).

Ability to remove features from clubs
 
Other Minor Tweaks
You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).

Often it's the smaller changes that can make a big improvement in the day to day use of your community. We have made quite a few updates that will make your community flow better for you and your members.
Update files in Pages Media Manager
Previously when you wanted to update a file in the Pages Media Manager you actually had to upload a new file and then change the references to that file to the new one. This was obviously not so great.
When you select a file there is now a replace option. We're not sure why we didn't do this earlier but as they say: better late than never!
Tag Input when Optional
On communities with tagging enabled, we have often noticed that people tend to feel the need to tag everything even when it's not really necessary. If your site is about cars you don't really need everything people post to be tagged "car" as that's sort of obvious.

 
So to make it a bit clearer that tags are not required we have hidden the input field behind a Choose link so people have to actively choose to tag if they really think it's necessary. We hope this cuts down on tag noise. If tagging is required then the normal input box will always show.
Google Invisible reCAPTCHA
The new Google Invisible reCAPTCHA allows you to prevent bot registrations without the need for all users to fill out the normal captcha process. As often as possible your members will never notice there is even a captcha happening on the page. It's another way to make the flow from guest to member easier.
Whitelist for Spam Service
The spam defense service Invision Community provides works very well at combatting spam signups automatically. The issue is sometimes it works too well!
Let's say you are at work and all your colleagues share the same public IP. You are excited about your new community (of course you are) and your whole office tries to register at once. Our spam service would probably see your office IP as suspicious with that sudden influx of traffic and may even block it.
The new whitelist tool allows you to specify IPs and email addresses to always allow on your community regardless of what score our spam defense gives it.
Reply as Hidden
Sometimes it would be nice if your moderators could reply to an item with a hidden reply. You might want to leave a note for other moderators or perhaps you have a database and want some replies public and some private.

 
If you have permission you will now see a hide toggle when replying. This works in all apps anywhere you can reply to a content item and have hide permission.
Exclude Groups in Leaderboard
You can now exclude certain groups from being ranked in the Leaderboard. This is very useful if your staff or RSS bot tend to get all the reputation points. By excluding those groups you can focus on your actual member participation which is a better reward to encourage engagement.
On a personal note this will make me very sad as I usually win reputation counts on our site. But, being such a great person, I am willing to make this sacrifice for you.  
Complete Your Profile Order
The Complete Your Profile feature introduced in version 4.2 has been a great success for clients. We have heard many reports of increased engagement as the system can walk people through the sign up process. Not having a big, scary registration form is always a huge plus.
For 4.3 we added the new ability to change the order of completion for your members. This will allow you to stress the items you really want them to complete first and move your less important profile options later in the steps.
Mapbox Support
Mapping has been a feature of Invision Community for quite some time but up until now has been limited to Google Maps integration. For 4.3 we have added support for Mapbox which is based on OpenStreetMap data. The maps are beautifully designed and bring greater flexibility with an alternative look. The groundwork is now laid for some exciting new features still to come!
Some of our existing customers also found Google policies and pricing structure incompatible with their own internal policies which this addition addresses.

Stripe is the most popular payment method in Commerce, allowing communities to take payments by card securely with easy setup.
While there's no doubt that credit cards are still the most popular methods of making a payment, digital innovations such as Apple Pay are increasing in popularity.
For 4.3 we've deepened our integration to support some of their latest features.
Apple Pay & Google Pay
Apple Pay allows users to pay quickly with their iPhone, iPad or Mac (with Safari and either a paired iPhone or using the MacBook Pro with Touch ID) using the card details stored on the device, authenticated with Touch ID or Face ID.
Apple Pay
Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
Paying with card details stored in Google Chrome
 
Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
Commerce will automatically hide the option if the user's device does not support either method.
3D Secure
Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
 
Amex Express Checkout
American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
Amex Express Checkout
 
Alipay, Bancontact, Giropay, iDEAL, SOFORT
These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
All of these are also now supported through Stripe in 4.3.
 
Dispute/Chargeback Handling
A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

Disputed Transaction
All transactions with currently open disputes can be accessed quickly from the transaction list. The transaction page will show you the status and reason for the dispute, and links to your Stripe dashboard where you can respond.
When the dispute is resolved, the transaction screen will be updated, with either the transaction being marked as refunded if the dispute is lost, or going back to paid if the dispute is won and the funds returned to you.

A dispute that was lost

A dispute that was won
 
 
Radar
Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.

Search. Let's be honest, it's not the most exciting feature in the world. You ask to find things, and it shows you what it found.
Simple, right?
It's a lot more complex than that. After numerous tests, a few surveys and many discussions with customers, we've decided that there is no "right" or "wrong" way to search. Invision Community is used on many diverse communities and each has its own needs.
The bigger the community, the more of a headache search can be when you start hitting frustrating technical limitations of the database.
Happily, we've addressed all of these issues with Invision Community 4.3 and added a few extra treats.
Searchable Products and Pages
Products in the Store and custom Pages will now show in search results.

Store product in search results
More Customisable Search Experience
One of the most difficult challenges with search is anticipating the scope of the search. If, for example, you're looking for something you know you've seen before, you want the search to be narrow - matching only the exact terms you provide, probably only matching against the title, in the specific area you know where the content is located. If however, you're just doing a general search about a particular subject, you want the search to be wide - matching any of the terms you enter, anywhere in the community, in both titles and content.
For a while, Invision Community has had the option to choose which areas to search, defaulting to the area of the community you're in (for example, if you're in a forum, only that forum will be searched by default). We also provide a number of suggestions on the search result form (in the form of "Didn't find what you were looking for? Try searching for..." followed by a number of options) which adjust the scope of the search.
In Invision Community 4.3, we have a new interface for the quick search feature which makes some of these options more visible so you're more likely to find what you're looking for on the first search.

New Search UI
Along these lines we have also:
Changed the default "Search In" selection to "Everywhere", regardless of where the user is. Added a new setting which controls whether the "Any words" or "All words" option is checked by default. Added a new setting which allows you to adjust how much of a boost results receive for a match in the title, versus the content body, when searching both content titles and body. You can set default and/or operator.

New Search Settings
Elasticsearch
In Invision Community 4.3 we are adding native support for Elasticsearch, a third party search engine which offers a number of benefits over searching your MySQL database:
Elasticsearch, being designed and indexing data in a way optimised for search rather than data storage, is generally able to match and sort by relevancy with better accuracy than MySQL. Elasticsearch is generally faster. One user performing a search doesn't slow down other users trying to read and make posts at the same time (when searching MySQL, the data has to be "locked" from changes when the search is being performed). It scales very well with very large datasets, and runs very easily on multiple servers. Elasticsearch understands language. If for example, you search for "community", it will also return results which contain the word "communities", understanding that these are the same. Supported languages are Arabic, Armenian, Basque, Brazilian, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, English, Dinnish, Drench, Galician, German, Greek, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Persian, Portuguese, Romanian, Russian, Sorani, Spanish, Swedish, Turkish, Thai. Elasticsearch supports custom functions on the scoring algorithm. In our initial implementation this has allowed us to add settings to allow you to control the time decay (allowing newer results to show higher) and author boost (allowing content posted by the user to optionally show higher in results). Unlike with MySQL, there is no minimum query length and a very small list of stop words.
Elasticsearch Settings
When enabled, both searches and activity streams will be retrieved from Elasticsearch. The core_search_index database table in MySQL will no longer be populated, so you will not have to store the data twice.
To use Elasticsearch, you can either install it yourself on your own server, or use any of the many excellent hosted Elasticsearch options. The minimum required Elasticsearch version is 5.5.
REST API
Developers and those looking to integrate Invision Community features into their own sites will be pleased to learn that we've extended the REST API to accommodate searching. 

Good news!
We've taken Invision Community's Blog app by the scruff of the neck and dragged it into 2018!
There has been a growing trend for imagery to play a very important part of a blog entry. This update reflects that.
Introducing Grid View
We have added a new view that shows your blog entries as cards with space for a cover photo.
We've very visual creatures, and a good photograph can entice readers into your blogs to read more. 
As you would expect, you can disable this mode from the Admin CP for purists that prefer the traditional list format.

 
For those who's sense of adventure runs deep, the new grid mode allows you to show a list of latest blog entries as the blog home page.

 
This puts valuable and engaging content right in front of your audience.
This list view persists when you view a blog's entries giving a consistent feel.

 
Viewing an entry
We've given the blog entry page a little make-over by featuring the cover photo above the content. The slimmed down blog details bar allows your audience to focus on the content.

 
Default Cover Photos
You may have spotted that entries without a cover photo have a rather fetching geometric pattern in different colors.

 
This is a new micro-feature of Invision Community 4.3. Currently, if you do not have a cover photo on a blog, profile or event, the bar is a rather sad shade of black.
The new default cover photo feature makes it much more cheerful. Here's what a profile looks like.

 
Much better.
Here's a few technical details for those that love to know all the things.
The grid view feature can be turned off in the ACP (but doing so will make me very sad) You can choose the default home page view: Latest Entries or List of Blogs. You can still view a list of blogs when you're on the latest entries page. This choice is stored in a little cookie (GDPR friendly, it doesn't contain any identifying data) so navigating back gets you the last view you chose. Let us know what you think! We love it, and hope you do too.

The best way to convert guests into members is to make the onboarding process as simple as possible.
Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
These services used to use proprietary methods to link with other websites, but a new standard has emerged.
OAuth
You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
In Invision Community 4.3, we are introducing several exciting new features:
In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
Setting Up a Custom OAuth Provider
For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

Login Handlers List
When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
 
Choosing a Login Handler
You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

Inputting vk.com credentials
I then need to find the endpoints from vk.com's documentation and input those too.

Inputting vk.com endpoints
Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


Inputting vk.com User Information Endpoint and response parameters
Finally, provide a logo and a color for the sign in button and some final settings:

Inputting vk.com Logo and Button Color
And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

Signing in with vk.com
 
Using Invision Community as an OAuth Server
You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
You will set up the clients from the AdminCP:


Setting up an OAuth Client
When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

Defining OAuth Client Scopes
The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

Authenticating an OAuth Client
The REST API has new and updated endpoints to be aware of the authenticated user:

A new REST API endpoint which returns details of the currently authenticated user

An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
 
Other Login System Tweaks
Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 

Emoji: built in to Invision Community 4.3! ?
Invision Community has a long history. We remember the early days of forums, back when graphical "emoticons" or "smilies" were added.
We have always shipped our products with a basic set of emoticons with the ability to add your own images and has supported emoji from mobile devices.
Emoji has become a standard across mobile and desktop devices so it made sense to bring them to Invision Community fully.
You can choose from 3 different styles of Emoji:
The native style provided by the user's operating system (if you choose this option, users on different platforms will see different styles) Twitter style EmojiOne style
Emoji Settings
Once you have chosen one of these options, all of the available Emoji will show in the emoticons selector when making a post. Unlike in older versions, the entire list is scrollable (the categories drop down will jump you to the category rather than filter), you can search, and standard Emoji features like skin tone modifiers are fully supported, and of course, you can make them as big as you like.

Navigating Emoji

Skin Tone Modifier

Make Emoji any size
 
Autocompleting Short Codes
In addition to using the selector, you can also use optionally enable standard :short_codes:. These will be autocompleted as you type.

Autocompleting Short Codes
You can also enable more conventional ASCII emoticons to be automatically replaced too:

ASCII Short Codes
 
Don't Worry: Custom Emoticons Aren't Going Anywhere!
You can use custom emoticons either instead of, or even alongside Emoji. If you give your custom emoticons a text replacement starting and ending with : they will even show in the autocompletion alongside Emoji.

Custom Emoticons
 
Technical Details 
Whichever style you choose, Emoji is stored in the database as the actual Unicode characters, so you can even change the setting and all Emoji, even those in existing posts, will immediately change.
If you choose to use the native style (so the Emoji will match the style provided by the operating system), the system will automatically detect which Emojis are supported and the selector will only try to show the ones the platform can render.

We are happy to announce the new Invision Community 4.3 is available!
Some highlights in Invision Community 4.3 include...
Improved Search
We now support Elasticsearch for scalable and accurate searching that MySQL alone cannot provided. There are also enhancements to the overall search interfaces based on your feedback.

 
Emoji
Express yourself with native emoji support in all editors. You can also keep your custom emoticons as you have now.

 
Member Management
The AdminCP interface to manage your members is all new allowing you easier control and management of your membership.

 
Automatic Community Moderation
You as the administrator set up rules to define how many unique member reports a piece of content needs to receive before it's automatically hidden from view and moderators notified.

 
Clubs
The new Clubs feature has been a huge hit with Invision Community users and we are expanding it to include invite-only options, notifications, exposure on the main community pages, paid memberships, and more.
Custom Email Footers
Your community generates a lot of email and you can now include dynamic content in the footer to help drive engagement and content discovery. 
New Gallery Interface
We have reworked our Gallery system with a simplified upload process and more streamlined image viewing.
 
The full list follows. Enjoy!
Content Discovery
We now support Elasticsearch which is a search utility that allows for much faster and more reliable searching. The REST API now supports search functions. Both MySQL and Elasticsearch have new settings for the admin to use to set search-defaults and default content weighting to better customize search logic to your community. Visitors can now search for Content Pages and Commerce Products. When entering a search term, members now see a more clear interface so they know what areas they are searching in and the method of search. Member Engagement
Commerce can now send a customizable account welcome email after checkout. You can whitelist emails in the spam service to stop false-positives. REST API has many enhancements to mange members. Ability to join any OAuth service for login management. Invision Community can now be an OAuth endpoint. Wordpress OAuth login method built in. Support for Google's Invisible ReCaptcha. Groups can be excluded from Leaderboard (such as admins or bot groups). All emails generated by Invision Community can now contain admin-defined extra promotional text in the footer such as Our Picks, and Social Links. Admins can now define the order of Complete Your Profile to better control user experience. Clubs
Option to make a Club visible but invite-only Admins can set an option so any Club a member is part of will also show in the parent application. So if you are in a Club that has a Gallery tab then those image will show both in the Club and in the main Gallery section of the community. Club members can now follow an entire Club rather than just each content section. There is a new option on the Club directory page for a list view which is useful for communities with many Clubs. If you have Commerce you can now enable paid memberships to Clubs. Admins can set limits on number of Clubs per group. If a group has delete permission in their Club, they can now delete empty containers as well. Members can ignore invitations. Moderation and Administration
Unrestricted moderator or administrator permission sets in the AdminCP are visually flagged. This prevents administrator confusion when they cannot do something as they will be able to quickly see if their account has restrictions. You can choose to be notified with a new Club is created. Moderators can now reply to any content item with a hidden reply. Download screenshot/watermarks can now be rebuilt if you change settings. Support for Facebook Pixel to easily track visitors. Moderators can now delete Gallery albums. Automatic moderation tools with rules to define when content should auto-hide based on user reports. Totally new member management view in AdminCP. More areas are mass-selectable like comments and AdminCP functions for easier management. New Features
Commerce now has full Stripe support including fraud tools, Apple Pay, and other Stripe features. Commerce packages can now have various custom email events configured (expiring soon, purchased, expired). Full Emojii support in the editor. Complete overhaul of the Gallery upload and image views. Announcements system overhaul. Now global on all pages (not via widget) and new modes including dismissible announcements and top-header floating bar option. Many new reports on traffic and engagement in the AdminCP. Blog has new view modes to offer options for a traditional site blog or a community multi-member blog platform. The content-starter can now leave one reply to Reviews on their item. Commerce now makes it much easier to do basic account-subscriptions when there is no product attached. Useful Improvements
Forums has a new widget where you can filter by tags. If tags are not required, the tag input box now indicates this so the member knows they do not have to put in tags. Member cover photos can now be clicked to see the full image. Any item with a poll now has a symbol on the list view. Twitch.tv embed support. You can now update/overwrite media in the Pages Media Manager. Mapbox as an additional map provider to Google Maps. Technical Changes
Direct support for Sparkpost has been removed. Anyone currently using Sparkpost will automatically have their settings converted to the Sparkpost SMTP mode so your email will still work. Your cache engines (like Redis) will be checked on upgrade and in the support tool to ensure they are reachable. Third-party applications will now be visually labeled to distinguish them from Invision Community official applications. The queued tasks list in the AdminCP is now collapsed by default as queued tasks are not something people need to pay much attention to during normal operations. When upgrading from version 3 series you must convert your database to UTF8 and the system saves your original data in tables prefixed with orig. The AdminCP now alerts you these are still present and allows you to remove them to reclaim storage space. On new installs there are now reasonable defaults for upload limits to keep people from eating up storage space. Categories in all apps (forums, gallery albums, databases, etc.) no longer allow HTML in their titles. This has been a concern both in terms of security and usability so we were forced to restrict it. Large improvements to the Redis cache engine including use for sessions. The login with HTTPS option has been removed and those who were using it will be given instructions to convert their entire community to HTTPS. Images loaded through the proxy system now honor image limits for normal uploads. We now consider BBCode deprecated. We are not removing support but will not fix any future issues that may come up.
 
There's a lot to talk about here so we are going to lock this entry to comments so things do not get confusing. Feel free to comment on upcoming feature-specific entries or start a topic in our Feedback forum.
 

As we make our final commits, merge in the last of our branches and wait for Charles to move more tasks to the development list, we pause to reflect on our year together as a company.
Pour some egg nog, grab some snacks and lets take a look at our journey this year.
Our year in numbers
In 2017 we made 72 Invision Community releases, 6584 code commits, read 157,203 customer replies and made an average of 177 staff replies to tickets per day.
Our year in dates
We were certainly busy this year. We launched Invision Community 4.2, started work on Invision Community 4.3, started two new blog series and a newsletter. Lets take a look at the key dates.
March 10th
We started talking about our upcoming release, Invision Community 4.2 which saw us drop "Invision Power Services" in favour of the sleeker and less awkward "Invision Community".
March 28 - 30th
During our series of blogs on 4.2, we launch a triple whammy of blog entries outlining reactions, clubs and social media promotions. Three new tent-pole features that drove 4.2 to be our most successful release.
July 19th
We release Invision Community 4.2 to deafening applause (most of it was our own, but it still counts). We give the development team a 15 minute break and then drop the 4.3 task list internally.
September 15th
We start a new blog series "Team Talk". The idea is to show that we're not a bunch of code writing robots, but we're real people with personalities, hopes and dreams. So far, it's proved that we're mostly a bunch of code writing robots without personalities. The irony.
October 18th
Not content to just talk about silly things in Team Talk, we launched our new long form blog series "Community Management". Here we give our many years of community building insight to help you become successful in running your communities. We've tackled a number of subjects from SEO to security so far with many more planned for 2018.
October 30th
Our development team have been busy working on Invision Community 4.3 and we announce it to the world. And being the huge tease we are, we've said nothing since. Rest assured, we've got a lot done and its shaping up to be another great release. We'll be talking about it in more detail next year.
It's all about you
Of course, we couldn't finish without saying a massive THANK YOU to all our customers. We are so lucky to do something we love for a living and that is only possible because you choose to use us to build your community.
We are committed to keep moving forward to ensure that we serve you in the best way possible. We'll keep innovating to give you the tools you need to succeed and we'll keep posting blogs packed full of tips and advice.
Here's to 2018 and all the adventures it brings.

 
 

The General Data Protection Regulation (GDPR) is a regulation (EU 2016/679) that is intended to strengthen and unify data protection for EU residents from 25th May 2018.
How can Invision Community help?
While Invision Community enables you to collect and store information, it's important to note that you as the site owner are the data controller. If your site can collect data from EU citizens, then we recommend that you research your responsibilities.
We have introduced several new tools in Invision Community 4.2.7 to help you with compliance, and we'll run through them and the relevant sections of the regulation in this blog.
Individual Rights (More information)
Right to be informed
Invision Community has an area for you to edit your own privacy policy. This is found in the Admin CP > Settings > Terms & Privacy Policy.

 
Guidance on what the policy should contain can be found here.
Right to erasure (More information)
Invision Community allows you to delete a member from the Admin CP. If the member has left posts or comments on your community, you can elect to delete the content, or keep it but remove the author's details thereby making the content anonymous.
Lawful bases for processing (More information)
Consent (More information)
Invision Community now features a setting to not automatically opt in to administrator emails such as those sent by the bulk email system often used for newsletters when registering a new account on your community.
This feature is found in the ACP > Members > Registration Settings

 
Part of the consent regulation is to record when consent was given. The consent to opt-in for administrator emails such as bulk emails sent via the Admin CP is recorded at registration, and each time they change the setting. This record can be found in the member history log when viewing a member in the Admin CP.

If you change the Terms & Conditions, or the Privacy Policy, you can request that members accept these changes when they next log in thus giving their consent for those changes.

Cookies (More information)
Invision Community stores a small amount of data in cookies. These are used to authorize you when you re-visit a community. Other cookies are used to provide a service at the user's request, such as changing a theme or using Commerce's cart.
We have added additional features for Invision Community 4.2.7 to permit acknolwedgement that cookies will be set, and a brief page outlining the types of cookies that are set.
Invision Community has a feature that shows a small message to new visitors to the community. This is found in the Admin CP > Terms & Privacy Policy page.

 
We have pre-configured a cookie acknowledgement message using the short-tags {cookies}.
This will display as follows:

 
This links to a new page showing brief information about the types of cookies that Invision Community stores.

 
Although at the time of writing this blog entry, the regulation states that there is no exact information that you need to show on the cookie page, you can edit it to add more detail if you wish.
Summary
We hope these new tools available with Invision Community 4.2.7 make it easier for you to seek compliance with GDPR if you choose to do so.
It's worth pointing out that we are awesome at making community software and know a huge amount about making communities successful, but we are not experts in EU regulation. We offer this blog entry as a way to assist you in seeking compliance but you must do your own research and are responsible for your own community.
Invision Community 4.2.7 is currently in beta testing. We're aiming to release it early next week.
We hope this is a good starting point for you!

Unlike a regular website, where you write content for each page, target keywords and optimize text, a forum community's content is predominantly written by users. They don't know or care about your site's SEO and just want to interact with other users or find answers to their questions.
To keep your community moving forward, Invision Community implements many best-practice SEO techniques and approaches for you automatically, without you needing to lift a finger.
Even still, there are a few additional steps you can take to potentially help your site rank better.
 
How Invision Community helps you automatically
Invision Community does a lot of automatic SEO for you behind the scenes to help your site rank better or to help search engines understand your content. Some of those include:
Sitemap generation
A sitemap file helps search engines to locate pages within your site. This helps search engines find pages so they will be crawled quicker. Invision Community automatically generates a sitemap for you that points to all of your content URLs, and submits it to Google. JSON-LD
Another way a site can help search engines is by providing metadata about a page. For example, if the page contains a review, additional data can be supplied to the search engine with rating count, average, and so on. There are dozens of items that can be described in this way, and doing so can mean your results in search engines display this additional data. This makes results more useful to users, potentially leading them to click on your result versus another. It can also help search engines understand your content better. Canonical URLs
Search engines can penalize your site in situations where the same content can have multiple URLs. With software that generates pages dynamically, such as a community, this can happen frequently because there are URLs to get the last read post, the latest post, the first post and so on, all ultimately pointing to the same topic page. Invision Community takes care of this for you by setting a canonical URL for every page, telling the search engine which is the definitive URL it should use. Semantic markup
The HTML markup used to generate a page is possibly the most important factor impacting SEO. Each HTML tag has a specific meaning (e.g. H1 is an important title) and allows search engines to determine the structure of the page. It's therefore important that tags are used correctly and in the appropriate context - known as semantic markup. Invision Community has been built with semantic markup principles in mind right from the start. Responsive theme
Google has been transitioning to a mobile-first approach when crawling sites and it's likely this does or will factor into its PageRank system. Now more than ever it is important that your community offers a genuine mobile experience. Invision Community achieves this by supporting responsiveness - where the theme adapts depending on size of the screen being used - by default.  
What you can do to improve ranking
Let search engines see your content
One of the most important things you can do to help with SEO might seem obvious, but we've seen many people unwittingly neglect it: ensure that search engines can see your content!
It's tempting to lock down your community so that users have to log in before being able to see your content, and for some communities this might be necessary. However, a search engine can only see content accessible to guests, and so by locking your community down a search engine won't be able to see very much at all, and your pages won't show in search results.
Wherever possible, we suggest allowing guests to read your content, though you can require registration to reply.
Enable HTTPS
Even ignoring SEO this is a good idea, because it's more secure for your users and browsers are increasingly alerting users about sites that don't use HTTPS, showing them as insecure.
In terms of SEO, research has shown a correlation between between sites using HTTPS and their ranking position, and in 2014 Google indicated that HTTPS would be a “ranking signal” going forward. Given the other benefits of HTTPS, it would therefore be wise to enable it across your community.
Ensure your site loads fast
A fast-loading site is very important for rankings, and so you should do what you can to keep your community running quickly. This includes:
Enable guest caching
Invision Community includes a built-in caching system for pages viewed by guests, ensuring they don't have to be re-generated for every page view. This can greatly speed up your site for guest users and therefore search engines. This is automatically configured on our Cloud services. Don't go overboard with plugins
A few good plugins can set your community apart from others, but going overboard can significantly slow down your load times or clutter your interface. Be wary of image-heavy themes
As with plugins, a great theme is a good thing to have, but try to avoid one with extensive use of very large images. Choose a good host
Some website hosts are slower than others, so ensuring your host is up to scratch is important. Of course our Cloud services are a great solution here!  
Use 301 Redirects if migrating
If you're migrating from another community platform, your page URLs will change to reflect Invision Community's architecture. You can greatly improve SEO retention by using special redirects (known as 301 Redirects) to send users from your old URLs to the new. Search engines understand this method and will update their records.
We include redirects in our free migration packages to help you retain your SEO standings after migrating to Invision Community.
Write relevant content
If your site targets a particular niche, you may see benefit in writing longer-form content as articles on a site blog. This kind of content ranks well and allows you to ensure keywords are used (versus content posted by members, which can be anything). You can also encourage further discussion of the article in the wider community, amplifying its benefit.
For a site news page/blog, our Pages app can be used to build an articles section for this purpose.
Use social media profiles to your benefit
You should register social media profiles for your site on the popular platforms and make them a part of your presence. These sites rank very highly of course, and so if your social profiles can also rank highly for your name, they can be a good way of directing traffic to your site.
Use the ‘About' section of the profile to write an interesting blurb about what your site offers. Create eye-catching header images and profile photos to use on the profiles too. Cross-link each social profile to the others (and back to your site, of course). Finally, link to your social profiles from your site too. Invision Community allows you to easily do this and insert icons in your header or footer.
Beyond that, you can also use social media to your advantage by cross-linking some of your best content to it. We'll go into more detail on how best to leverage social media in a future article, but the new Promote functionality in Invision Community is a great way of achieving this.
 
Summing Up
As always, content is king when it comes to ranking, and that should be your most important focus. Fostering a vibrant community that creates and shares interesting content is key. You can then use SEO methods boosted by Invision Community features to expand your community's reach in search engines.
If you have any SEO tips that have helped your site, we'd love to hear them. Share them in the comments below!

Whether you run an existing community or are taking tentative first steps into setting up an online community forum around your brand, an important choice you need to make is between social networks like Facebook or having a community you own and control.
Let's take a look at the benefits of an owned community versus a Facebook group - as well as how you can still use Facebook (and other social media platforms) to your advantage.
 
You own your data
The biggest point to consider when using Facebook groups is that you do not own your own data. Facebook owns it and does not even allow you direct access to it. If you decide later to move to a different platform, need to run reports to extract meaningful insights, or otherwise work with your community data: you are out of luck.
In contrast, with an Invision Community, your data is your data. You can use it in any way that makes sense for your goals; be it analyzing trends, sending promotions to users, or generating reports and statistics. We never hold your data hostage and there's no fee to get it.
Beyond owning the data, you also control how it's used and presented. Facebook is notorious for changing algorithms for when (or even if) people see your posts. When you run your own community the experience for your and your users is in your control.
 
Branding opportunities
This is a big one. An owned community gives you the tools you need to make your community a seamless part of your user's interaction with your business. This naturally includes your brand styles (your logo, colors, site navigation and so on) but also your community web address (URL). With an owned community, your URL will be easy to find - customers normally opt for something like forum.yourname.com or community.yourname.com. 
Users will have more confidence that they're in the right place, and more closely associate your community and your message with your brand.
Emails sent out by your owned community can also carry your branding, consistently reinforcing that connection between your business and your community.
And, of course, when users share content from your community to Facebook and other social networks, they're sending users directly to your website where you have the opportunity to lead with your most important call to actions.
 
More control over user experience
All Facebook groups are, essentially, the same experience and yet your business needs almost certainly aren't the same as every other. One size doesn't necessarily fit all when it comes to community!
When you control your own community, you have the ability to control your user's experience. Need to show specific types of data in specific places? You can do that (and more) with Invision Community's easy to use Blocks feature. Need to create a custom community application to serve as a resource center for product support? You can do that too.
Another huge benefit of this control is that, unlike a Facebook Group, users won't be seeing ads and 'recommended content' from competing businesses and communities. With user attention being pulled in so many directions these days, the last thing your community needs is for users to leave because Facebook has suggested a competitor!
 
No barriers to monetization
Not all communities require a monetization strategy. In many cases, the community is part of a larger customer relationship strategy rather than a revenue-generating destination in its own right.
But for those communities that do plan to monetize, options with a Facebook group are at best difficult to act upon, and at worst practically non-existent.
In contrast, Invision Community gives you the opportunity to explore monetization strategies that work for you. These might include paid subscription plans (a particularly attractive option for fan club communities), traditional advertising through Google AdSense and other networks, or sponsorship deals with other businesses that might be relevant to your members. Invision Community has tools for each of these approaches built in, allowing you to start monetizing with minimum fuss.
 
Fine-grained permission controls
Facebook groups struggle to reflect the real-world roles that staff members play in your organization, limiting your choices to 'administrator' or 'moderator'. And the same is true of users, too - your options for recognizing different levels of user (such as VIPs, or brand ambassadors) are limited.
Invision Community is different. Since you are creating and configuring each member group, you can precisely control who can see what, and how they are recognized within the community. You can even sync these roles via Single Sign-On (SSO) making setup and assigning users to groups painless.
For staff groups, you can limit access to key community functions based on roles or responsibilities, ensuring access is granted on an as-needed basis only.
For users, you can get creative and find a group structure that works best for your specific needs. For example, support communities often find that recognizing the most knowledgeable and helpful members with a new member group (complete with elevated permissions) is a great way of engaging users.
And finally, with this control over access, it's very easy to create restricted areas of the community. Whether you want to create a private subforum that staff can use to coordinate tasks or a file repository that's only available to subscribers, Invision Community can achieve it.
 
You can still reap the Facebook benefits
Setting up your community within Facebook's walls might not be the best approach for you. That doesn't mean you should ignore Facebook, however. On the contrary, it's an influential platform and there's a very good chance your users are already using it.
Invision Community offers a number of tools that allow you to benefit from Facebook while avoiding the drawbacks we discussed. We'll go into more detail on utilizing social media in a future article, but to summarize:
Invision Community features social sign-in options, enabling users to register and log in using their existing social media accounts, substantially reducing onboarding friction. Content can promoted by staff back to your social network pages, automatically and on a schedule you decide. Invision Community supports automatic embedding of a wide number of social networks (and other services), allowing users to share their favorite Facebook and Twitter posts and spark a whole new conversation - but this time in your community.  
Summary
When you are creating an online community for your business or hobby it is important to think about your goals and future growth by choosing a platform that is there to work for your needs.
When you establish your community on Facebook, you're helping to grow someone else's business (including, potentially, your competitors!) and hoping that some of those spoils fall to you. With an owned community, the rewards of your hard work belong to you and your business alone.
Invision Community has been enabling users and businesses to communicate online since 2002, and we're proud of our reputation as a platform that puts control in your hands. Contact us if you'd like to discuss how we can help you too.
 

Whatever the purpose of a community - be it customer support, fan engagement, interest-based groups and so on - there's usually a need for site staff to communicate important information to users.
Of course, in some cases this information is best suited to a site announcement, which by design has a lot of visibility and authority. But it's important that day to day staff posts stand out too. As we'll discuss in future articles, a key part of engagement is that users see your organization's team interacting with the community. In many cases, users will expect and appreciate acknowledgement from your community team, and by highlighting those responses you can add a visible stamp of authority.
Invision Community has a few different tools to help you highlight staff posts, so let's take a look at them in more detail. 

Group badges
With group badges you can upload a small image that is shown beside a user's posts. It's shown alongside the user's group name, so you don't need to repeat that text.
Each group can have a different badge, perfect for communities that structure their staff groups based on role type. It's common to color-code group badges for easier identification - support as green, product development as blue, and so on (and you may want to coordinate these colors with the prefix and suffix you use, which we cover later in this article).

 
It's not just staff groups that can have badges, either; your regular member groups can too. However, a word of caution! If every group has a badge, they may lose their distinctiveness. We recommend reserving group badges for those groups you specifically want to draw attention to.

Post highlights
Second is a feature more explicitly designed to highlight a post rather than simply draw attention to the author. Group settings in Invision Community enable you to choose to have posts by users in each group show with a distinctive background color and border. The color is defined by your theme and so is easily configurable, too.

 
As with group badges, it may be tempting to highlight every group's content, but we recommend not doing so as that reduces the overall impact of the feature. Keep it reserved for your key staff groups, and especially those that regularly interact with the community.

Group prefix/suffix
Invision Community allows you to define a custom prefix and suffix for each group. This is used in key locations, including to highlight usernames in the Active User block and to style member group names alongside content.
An important part of this feature is that it accepts HTML tags, which gives you a lot of scope for customizing the display by adding an opening and closing HTML tag to the prefix and suffix settings, respectively. For example, let's say we want to add a shield icon before the name, and make the text purple.
Prefix: <span style='color: #9013FE'><i class='fa fa-shield'></i>
Suffix: </span>
Simple! Now our staff members will display in the Active User block and elsewhere like this:

 

Bonus feature: Staff activity streams
I wanted to also mention a feature that achieves a slightly different goal to those we covered above, but nonetheless is an important way to bring additional visibility to staff content: activity streams.
As well as an overall “All Activity” stream that shows everything happening in the community, Invision Community allows you to define pre-made streams that are available to all users. You can use this to build streams of content with particular tags, certain types of content - or, as in this case, content by users in specific groups.

 
Simply create a new activity stream in the Admin Control Panel, set the configuration so that it only pulls content from members in your staff groups, and you're done. Users will now be able to visit the stream page to get a handy overview of everything staff members are doing in your community.

 
I recommend checking out the other filter options available for streams while you're setting this up - there's a huge amount of power available!

Summing up
I hope this quick overview of content highlighting features has been useful. When users visit your community, they're usually looking for authoritative information and that often comes right from your own team. By utilizing the features we've discussed here, you can make that information stand out more against the other content in your community.

This entry is about our IPS Community Suite 4.2 release
 
Improved Stripe Integration
Stripe is a popular payment gateway that supports card payments. In IPS Community Suite 4.2 we have made some improvements to our integration:
When viewing a transaction in the AdminCP, it will show the last 4 digits of the card used, and the result of Stripe's risk evaluation. More information is sent to Stripe for easier cross-reference between Stripe's control panel and your AdminCP. This includes the customer's name, billing and shipping addresses, email address, associated transaction/invoice/customer IDs, and the invoice title.  

Stripe Transaction in the AdminCP showing risk evaluation and card details

Transaction in Stripe's control panel showing customer and invoice details
 
Anti-Fraud Improvements
Anti-Fraud Rules now have some additional filters:
Products being purchases includes... Account was registered more/less than [x days] ago Customer is/isn't in group Customer has previously spent more/less than Time since last purchase is more/less than [x days] ago Custom profile fields (both at member and customer level) IP address is x (exactly, contains or matches regular expression) Customer has previously made transactions that failed (opposed to "were blocked by fraud rules") Email address matches regular expression
Some of the new Anti-Fraud Rule options
 
MaxMind per gateway
A new setting has been added that allows you to run MaxMind only against transactions using particular payment gateways.

New MaxMind gateways setting
 
Transaction Search
You can now enter the transaction ID provided by the payment gateway in the AdminCP search box to find a transaction.

Looking up a transaction by gateway ID
 
Renewal Savings
If you have a product with multiple renewal terms, a new setting allows you to show alongside each option how much is saved. This can be shown either as a monetary value, or as a percentage.

Product showing savings for different renewal options

Completing long and complex forms online is tedious. It can be off putting having to fill in a lot of information before you can join a site or service. You may find that potential members never bother to convert from a visitor.
How to convert guests into regular members is an often asked question. The simple answer is to lower the barrier to entry. Invision Community 4 already allows you to register with Facebook, Twitter, and other networks with ease.
"Complete My Profile" is a system that will lower the barrier of conversion. Guests only have to complete a very basic form to gain membership. Members are then asked to complete any custom profile fields you require.
You can also set up steps that group items together to encourage existing members to add more information to their public profile.
Members with a complete profile and user photo provide others with much more engagement and personality.
Registering
If we look at registering first. Clicking "Sign Up" will only show a simple modal form with as few fields as possible.

 
If you have required steps, and after any member validation flow, the complete your profile wizard is shown.

 
This enforces required fields and the member cannot skip them or view other pages until completed.
Of course, you may have steps that are not set to required. These are available too, but are skippable. Members can complete skipped steps later.

 
A dismissible progress bar shows to members that have uncompleted steps. Once dismissed, it no longer displays in the header of the site.

 
This same progress bar is always shown in the members' settings overview panel, in the user control panel. This will prompt members with incomplete steps.

 
If you set up a new required step, members have to complete the step before being able to browse again. This will ensure that all regular members have completed profiles.
Admin Control Panel
You will create new steps in the Admin Control Panel. Each step can contain multiple elements of a single group. This step can be set to required to enforce completion or suggested to allow it to be skipped.

 
The basic profile group contains things like user photo, birthday and cover photo. Choose any of these for this step.

 
The custom profile field group contains any fields you have set up already.

 
You can switch off this system if you feel it does not fit your needs. When disabled, you get the normal registration form.

 
Reducing the complexity of membership can only help convert more guests into contributing members. Enforcing required steps ensures that you capture data across your membership.
We hope you enjoy this feature and you see an increase in guest conversion with Invision Community 4.2.
 

This is an entry about our IPS Community Suite 4.2 release.
The ability to automatically promote users from one group to another based on set parameters has been a staple of community software for some time. Traditionally, the most common determination of promotion has been post count. Additionally, the 4.x Community Suite supports promoting members automatically based on the time elapsed since the user joined the site and based on their total reputation count.
With 4.2, we have completely overhauled and enhanced the group promotion feature bringing many new options to administrators looking to promote members through different group levels.
To start with, the group promotion options have been removed from the groups configuration pages into their own area.

Group promotion rules overview page
You will notice that rules are no longer strictly tied to a single group, and that rules can be sorted however you desire. When you create and edit rules, you can choose which groups the rule applies to, what parameters the user needs to meet in order for the rule to be activated, and then finally, which primary and secondary groups the user will be moved in to. You can also configure the rule to remove specified secondary groups, which can be useful if one rule adds a secondary group for users, and then the next rule should change them to be part of a different secondary group (i.e. add a new secondary group, but also remove the previously awarded secondary group).
The system uses the same member filters available when configuring bulk mail, and we have made some updates to the member filters area (and have introduced some new filters) in this release as well. For example, you can create a rule that only applies to members who have won the daily leaderboard at least once, or members who have created a blog.

Some of the group promotion filters, which are also available when sending bulk mails
Any time a member account is updated for any reason (a new visit, editing the member, the member makes a new post, etc.), the software will loop through all configured rules and the last rule in the list that matches the member will be applied. This approach allows you to create promotion levels, for instance when a member reaches 100 posted content items they will be promoted to a new group, and when they reach 1000 posted content items they will be promoted to yet a different new group.
Groups can be wholly excluded from any promotion rules, which is useful when you have administrator and/or moderator groups and you want to ensure that they are never moved to a different group. These groups will be disabled from selection when configuring group promotion rules, and these groups will be ignored if "any group" is selected for a promotion rule.
Finally, if a user is moved to a new primary group by Commerce because they have purchased a product which moves them to a new group, they will also be excluded from group promotion rules (however, Commerce purchases that only adjust secondary groups will not exclude users from being checked by group promotion rules).
 
Developer note: You can add your own filters for group promotion rules (and bulk mails) by adding MemberFilter extensions in 4.2, available in the Developer Center for your application.

This entry is about our IPS Community Suite 4.2 release.
IPS Community Suite has long had a reputation system; first we had a simple up/down system, later updated to introduce a Likes system as an alternative. Whichever system you chose to use, it tied in with our reputation system.
We're pleased to introduce the latest updates to the reputation system, and it's something that has been requested for quite some time: Reactions.
Quite simply, reactions allow users to offer more fine-grained sentiments towards content than a simple up/down or 'like'. They are now in common usage on social networks, and so users expect to be able to be more nuanced in their response to something they see.
Let's see how they work in a post, and then cover the options you'll have available.

What you see above is the default setup for a site that has used the Like system in version 4.1. We include 5 reactions by default:
Like Thanks Confused Sad Haha If you currently use the older style up/down reputation system, don't fret - you'll still get the new reactions on upgrade, but they'll be disabled by default and instead the new reaction UI will show up/down reactions. This gives you the flexibility to decide which of the new reactions, if any, you want to allow.
So, those are the basics - but what configuration options can you expect to see? First, you can of course add your own reactions! We expect that beyond the default reactions you'd expect to find, some sites will want reaction types specific to their use-case. On an intranet, you might want to have 'agree' and 'disagree' reactions for staff to use when responding to discussions. On a gaming community, you might replace the icons to be some graphic from a video game that means something to your particular userbase. There's a wealth of possibilities.
Each reaction you set up can be configured to adjust the original author's reputation count - a reaction can be positive (i.e. award a reputation point), negative (i.e. subtract a reputation point), or neutral (i.e. leave the reputation count unchanged). Our default set won't include any negative reactions, but you are free to configure these and new reactions to suit your own use-case. A user's total reputation count is still shown alongside their content and in their profile, of course.
If you don't want to use the new reactions for whatever reason, you can disable all of them except Like, and it'll behave just the like 4.1-and-earlier system:

 
Sites that currently use the up/down system don't show a list of names of users, and instead show an overall reputation score for the content. With the new reaction system, you can enable this even if you don't use up/down reactions. This is great if you plan to use reactions as, for example, an agree/disagree system, or where the content score is more important to your site than the individual reaction types.

How the reaction UI looks with the 'count only' setting enabled
As you'd expect, you can click individual reaction counts (or the overall reputation score, if you enable that setting) to view who reacted to the content. This remains a permission setting that you can apply per-group.

On touch devices, on-hover functionality is not suitable, and so for these devices the reactions UI looks like this:

Reactions play well with all areas of the suite, including Recommended Replies:

...and activity streams...

...and a couple of places we aren't quite ready to reveal yet  
 
We hope you're looking forward to this new feature as much as we are. It's already been a hit on our internal testing site, and we're looking forward to seeing how clients customize it for use on their own community.
Developer note: Reactions are one of two new features (the other currently unannounced) so far that make use of PHP Traits.