CP_User

Cue the music; switch on the dramatic lighting, we've got fantastic news!
We're now running Invision Community 4.3 on here for some advanced testing before we unleash the first beta release.

There's a subtle hint above
If you need a recap of what was added, take a look at our product updates blog which takes you through the highlights.
As this is a pre-beta release, expect some funkiness as we scurry around and tidy up our custom theme wrapper and other areas as we spot them.
If you you find a bug, we'd love for you to report it with as much detail as you can muster in the bug report area.
We'd love to know what you think, let us know below.

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.

 
 

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

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

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

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

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

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

 
This feature color also works on the table view.

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

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

Next week, IPS will be implementing the pricing changes to our product lineup that we published in 2015. In the spirit of Black Friday and Cyber Monday, we are extending an opportunity to purchase a new license or add new applications to your existing suite at 15% off our current pricing.
To take advantage of this offer, please use coupon code IPSPROMO16 at checkout. This promotion is active starting now and valid until 1 December 2016 (EST) and applies to new purchases only. We are unable to retroactively apply the discount.
This promotion also applies to Community in the Cloud for your first month of service!
If you’ve been waiting to purchase a new license or add products to your suite, this is the last opportunity to obtain this level of pricing! Happy shopping!

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.