Whiskey Bizness

Twenty years ago today, Invision Community was founded and within months the first version of Invision Community was released. Little did we know, this would be the start of a remarkable journey spanning several decades.
Our first version appeared shortly after we founded the company. It might be hard to imagine a time before social media and YouTube, but when we started out, the web looked very different.

The first version of Invision Community was called Invision Board, reflecting the popular term for forums back in the early 2000s. It was full featured and you may recognise some elements that persist today.
Like today, it even had a separate control panel where you could create new areas of discussion and customise the theme.

Twenty years is a long time and we've continued to adapt with the ever-changing needs of community managers. We've seen the rise of social media impact how people consume content and found ways to compliment Twitter and Facebook by offering a place for long-form permanent discussion.
Several elements remain from those early days but the concepts behind the theme have change significantly. New workflows, UI elements and views have helped the platform stay fresh and we've certainly innovated a few features that have since become industry standard over that time.
I can't express how proud I am of what we've built together. From those humble beginnings working until 2am to growing a creative and talented team around our passion for community.
I'm still as excited today as I was back in 2002. This year will see us build and release new tools to help guide and inform community managers. Our community platform continues to go from strength to strength.
Of course, the platform is only one part of Invision Community. Over the last twenty years I've been grateful to get to know many of you and watch your lives unfold.
This is as pure as community can get and I'm privileged to be part of it.

We have a few other surprises to celebrate our twentieth anniversary. We can't wait to share them!

I'd love to hear your memories of Invision Community! When did you first use our products and what was your community for? Please let me know in the comments below.

We are working hard to get Invision Community 4.2 ready to go! If you have not been following this upcoming version, check out the details:
Over the last month we have released several beta versions and feedback from those that have chosen to jump in on the beta has been great. We really could not be happier. Feedback has included amazement over how stable the beta is to reactions from community members enjoying all the new features.
Everyone here at IPS is very excited to get the full release out so everyone can enjoy it. Not everyone is comfortable using beta releases .
Back in March when we first announced 4.2 was coming soon we said that it would be out in mid-2017 and we are still on track for that. Be sure to keep an eye on announcements for the full release expected in the next 3 - 4 weeks.
We really hope everyone is as excited as we are about 4.2's full release. Based on the feedback from those already using 4.2 beta on their live sites we really think this will be a huge hit with your community.
 

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
 
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

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.

There are many strategies for growing your community, such as newsletters, mailing lists and advertising on other sites.
IPS Community Suite 4.2 puts a new tool at your disposal: promotions.
There’s no denying the popularity of social media. Worldwide, Facebook has 1.86 billion users active monthly. Every day, millions of people are using Facebook to speak with friends, to talk about their interests and to find new people to connect with.
Of that 1.86 billion people, a good portion of those are actively discussing topics your forum covers. There is a huge opportunity to tap into social media to join in the discussion and to promote your community and provide a venue to carry on the discussion.
For a while, we’ve had social media log in extensions, which means that your users can sign into your community simply by clicking a relevant button. We’ve also had the ability to share things to a personal Facebook account. These tools are great for your users, but how do they help you, forum owner?
IPS Community Suite 4.2 introduces a way to promote your content directly to your brand’s Facebook page and your brand’s Twitter account.
You can curate fun and engaging topics and share them. The workflow is simple. Simply browse your community and queue up interesting topics, comments, gallery items, blog posts or database articles for posting throughout the day to your brand’s social media accounts. You choose the schedule, the hashtags and the wording to send.
Let’s look at the feature set in more detail.
Your first stop is to set up the feature from the admin panel. The system will guide you through the necessary steps of connecting your Facebook and Twitter accounts. Once Facebook has been set up, you can select any page that you are an administrator of on Facebook.
 

The admin panel also offers scheduling options and permissions.
 

You can pre-set the times for when content will be posted. Facebook and Twitter both have analytic tools to determine when your visitors are most frequently online. A good tip here is to set the time to a slightly odd number, so 11:45am is better than 12:00pm as you are likely to catch the attention of someone waiting for lunch, or a lunchtime meeting.
 

You have full control over who can promote items to your social media accounts. You can specify by group or pick individual members who may not be in those groups.
Now that you’ve set up the backend, we can get promoting.
Each item, that is a topic, gallery album, blog entry or article has its own Promote button.

 
Each post and comment can also be shared individually, which is an easy way to share great content your visitors add to existing conversations.

 
Clicking this brings up the sharer.

 
This is where you can customize the text that is sent out to each social media channel. You’ll also notice space to promote this item within your own community in addition (or instead of) Facebook or Twitter, we will explore that shortly.
The sharer is smart enough to pull attachments already added in the post, and you can upload your own images to be sent. Generally, shared items that have an image get better organic reach than just text alone so you’ll almost always want to choose or add an image. Twitter can use up to 4 images, and Facebook allows 1000 pictures per album, but you’ll never want to upload that many!

 
Once you’ve filled out your content and picked your images, you can schedule the promotion. Generally, you’ll want to use the auto schedule option as this allows you to just stack up multiple items and let the auto scheduler post the items according to your pre-set schedule. You can also set a specific date and time if you are looking to run a promotion or other time sensitive event.


The promoted content viewed in Facebook and Twitter
It’s easy to see the status of your queued and sent items from the moderator view.

 
This area allows you to see previous promotions and modify pending promotions.
Earlier, we mentioned that the system has the ability to promote content internally. Promoting items to your own community lets you, the community manager, curate interesting items and comments and present this to your community. This is a great way to allow your visitors to explore content you think they’d enjoy.

 
Promoting content to your community via Our Picks also allow you to promote content if you cannot or choose not to use social networks. It has the advantage that social networks do not have over a community platform like IPS Community Suite: consistency. The content on your community is always there whereas a social network is all about right here right now. Miss it and you miss out. On your community you can engage and re-engage a subject all you want. 
Of course, we’ve built a widget that you can drag and drop to most pages to make this curated list more visible.
IPS Community Suite 4.2 gives you, the site owner and community manager the tools you need to reach out and engage new users already discussing the topics on social media your community covers. With single click sign in and the built in retention functionality the suite offers, you’ll have a powerful way of growing your user base. It furthers that goal by created a list of that promoted content for continual reference and promotion for visitors already on your site.
We’ve got lots more to discuss on this subject, and in the coming months we’ll be putting together some guides on social media best practices and how to leverage Facebook’s excellent post promotion / pay per click tools to further boost your site’s visibility to social media users.
We’re here to help you make a success of your community and to give social media users a venue for when they outgrow Facebook.

We are well into development on IPS Community Suite 4.2 and are excited to start announcing all the new features and improvements.
Our next big release is focused on engagement with your members. You will see enhancements to our Reputation system, new ways to encourage people to register on your community, and enhancements to existing features to make them more interactive. There are also entirely new capabilities we cannot wait to show you ranging from new ways to organize content to tools to help promote your community.
Version 4.2 also features a refreshed AdminCP and default front-end design. Theme changes in 4.2 are mostly in the CSS framework so your existing themes will either work without issue or require minor changes to work in the new version.
Over the next several weeks we will be posting news entries with previews of upcoming features fairly often. Be sure to follow our News section, our Facebook, or Twitter to stay up to date.
We expect IPS Community Suite 4.2 to be out in mid-2017 with a public preview available sooner.
Everyone at IPS has worked very hard on this update and we think you will love it!

IPS Community Suite 4.1.16 is nearing the end of development so I wanted to go over some of the new features in this upcoming release. Some are big and some are small but we always enjoy making any sort of enhancements to the Suite.
We expect 4.1.16 to go to public beta next week. If you are interested in using a public beta please check out our beta forum (clients only) with more info. We welcome as much testing as possible and our betas are considered safe to use on a live site. We do offer support for betas so, if you are technically minded, consider giving them a try.
Commerce: New Ticket Listing
We have redesigned the ticket listing view in Commerce to be much more user friendly and better use screen space. You can also now group by department which is great for organization.

 
Much like Activity Streams on the front end you can create custom views for tickets based on how you work.

The new My History view allows staff to quickly see their latest replies and actions along with some basic stats.

There are many other smaller improvement in Commerce in 4.1.16 as well. We think you will enjoy all the updates.
Security Questions
To enhance the security of your member accounts we now have a new security questions feature where you can allow your members to put in their own, personal security questions. The member will then be prompted to answer those questions for account actions you define.

Account Change Emails
Members will now receive confirmation emails when they change their email address...

and their password...

Topics per Page
You can now define the number of topics per page in forum view.

Remove all Followers
Moderators can now remove all followers from any item that allows follows. This is useful if you are archiving an old item or otherwise do not want people getting notified of new activity on an item.

Automatic Following
Your members can already choose to automatically follow content they start or reply to but now you can define this as the default behavior for all members. Your members can of course override this to their own preference.

Embed Failure Message
To answer the constant question "why didn't my media embed?" we now show you why. Regular members will just see a message indicating the Suite tried to embed but was not able to. Admins will get more information on what failed.

Suspended Member Page
When you banned/suspended a member previously they simply saw a generic permission denied message. We now show a more friendly page saying they were suspended and why.

The member can click to get the full information from the Warning System as well.

Contact Us
The contact us page now has configuration options to control where messages are sent. You can do email and even Commerce support departments now.

Announcements
Global announcements can now be restricted by member group.

And some technical stuff...
In addition to the new feature additions we have also fixed dozens of issues reported by clients. There was a particular focus on Commerce, Pages, and IPS Connect. Some other items of note:
Performance improvements in: profile view, sitemap generator, posting replies, and Activity Streams We now try to more reliably detect the AWS S3 endpoint for those using S3 file storage Tasks view will now show the last time a task ran More efficient license key checking to keep the keys from being checked too often which can slow your site down If group promotion based on date is enable the system will now auto-promote even if a member does not login If you move your site to a new URL you no longer have to update a constant if using the image proxy You can now press ctrl/cmd+enter in any editor window to submit the reply (yay!) In Commerce ticket view there are keyboard shortcuts to perform common actions (such as press 'r' to open reply box or 'n' for note) There is now logic to prevent double-posting when the initial post encounters an error on submit If your datastore (cache system) is not working properly the AdminCP will now show you a warning telling you that it needs attention.    

We are currently beta testing our next release, 4.1.12, which contains hundreds of bug fixes, dozens of improvements, as well as a handful of new features. I wanted to introduce one of those new features: post preview.
Long-time users of our software will know that a post preview function was a standard feature, but we took the decision to not include it in the initial IPS4 release. It had a couple of drawbacks:
it only applied to certain pages, such as topic view - other WYSIWYG editors simply didn't get a preview the workflow wasn't very good for modern web apps, requiring a round-trip to the server and a full page refresh When IPS4 was released, we felt that the built-in rendering of the editor was a sufficient preview of how the end result would appear. However, while analyzing ongoing customer and user feedback for IPS4 in its first year of release, we have seen that a preview still has a use. There are some circumstances when a true WYSIWYG experience is just not possible such as using more advanced formatting (like LaTeX) or when admins create certain custom editor plugins.
As a result, we rethought post preview. We wanted to ensure that all editors could be previewed, and that it didn't have a clunky workflow. In addition, since IPS4 uses a responsive theme, we wanted to give users the opportunity to preview how their post would look on different devices.
Here's the result, and what will be available in 4.1.12:

Post preview in IPS Community Suite 4.1.12
The preview is shown by clicking a new button on the toolbar (meaning it can be moved, removed, etc. just like the other default buttons). When the preview loads, the toolbar allows the user to resize it to different device sizes. If they are on desktop, they can also view it at tablet at phone sizes; on a tablet, it can also be viewed at phone size.
So now we not only show a true preview of what content will look like when posted, but we also allow you to preview how it will look on other devices. Of course that preview is just a best-guess since different devices have different window sizes but it does give you an idea.
We hope this reimagining of an old feature for a more modern web will please end-users and make posting content a more accurate process. Stay tuned for more updates on what's included in 4.1.12!
Version 4.1.12 is currently in beta testing and should be released in the next two weeks.

We are currently beta testing our next release, 4.1.12, which contains hundreds of bug fixes, dozens of improvements, as well as a handful of new features. In this post, I want to cover some improvements we've made to two key areas: activity streams and search.
Activity Streams
The first improvement we made is to change how the expanded/condensed toggles are displayed to improve their clarity. From studying the feedback from administrators and users, we discovered that many people did not realize the view could be changed. To improve this, the toggles now explicitly say 'Condensed' and 'Expanded', making it much clearer how the view can be toggled to your own preference.

More clearly marked expand and condense options for Activity Streams
Next, a common point of feedback about Activity Streams is that clicking a result and then hitting the Back button in the browser means you are put back at the first batch of results, losing your place in the stream. In 4.1.12 we improved this so that clicking Back will load the last batch of results you were viewing, enabling you to continue browsing from whence you left off.
Finally, in the Content Types menu we added an Apply button. We discovered that users were not always sure how to save the selection of content types they had made (which automatically happened when that menu was closed). To alleviate this, the new Apply button will save the selection and close the menu, updating the stream results in real-time as expected. You can still simply click out of the menu to apply changes as well.

The new Apply button in the Content Types menu
Search
While overall improvements to search (specifically the algorithms to match and return the results) are a matter of ongoing research and refinement which we will improve in the 4.2 series and beyond, 4.1.12 sees one small improvement to the options available to users. While you have always been able to search within a particular forum, category etc. while browsing that area, you were not able to retroactively filter into particular areas after performing a more general search. IPS Community Suite 4.1.12 adds this ability to the interface, allowing you to get more specific results from a particular area of the community.
Version 4.1.12 is currently in beta testing and should be released in the next two weeks.