DawPi

You’ve probably already noticed that something looks a little different in our community today.
As part of our ongoing community improvements, we’ve performed some housekeeping to streamline the forum structure, make more distinction between areas and open up a few areas to guests and friends.
The big visual change is that we now have four separate areas: support, community, marketplace and developers. It should hopefully be clear what each section does, but let's go through a few examples.
Support
This area is where you can leave feedback on existing features, help shape Invision Community’s future by suggesting new functionality and also where you can get quick support from fellow Invision Community owners and our team.
Starting today, you can post in the Help & Support forum to get help from our team. If you’re unsure what a feature does, or think you’ve spotted an issue that needs our help, then you’re welcome to start a topic. Of course, if you want private support, then you are welcome to create a ticket in the client area as normal.
Community
Even the most seasoned community manager needs a little help from time to time. This section is the place to ask about strategy, to blow off steam in the lounge or to ask for fellow owners to help with support requirements outside of official support, such as configuring servers, databases and so on.
Marketplace
Our Marketplace brings hundreds of new features, themes, language translations and plug-ins to your Invision Community. If you need support or have a request for something you’ve purchased from the Marketplace, drop into the forums here.
Developers
Invision Community is blessed with a strong developer community extending the rich functionality of Invision Community. If you’re looking to develop an idea for Invision Community, these forums will let you connect with our development team to answer questions as well as get help from other marketplace authors.
Other Changes
There are a few other changes of note that I’d like to go through. Firstly, ‘Visitors’ (that is a registered member without an active license) are now ‘Friends’. Who doesn’t need new friends? Guests and Friends can now view the official support forums, but cannot post a new support request or reply to existing ones.

We’ve merged ‘General Chat’ in with the Client Lounge to form ‘The Community Managers’ Lounge’. This is still a perk for active customers and the topics are not viewable unless you have an active license.
Finally, we’ve gone through and spruced up some of the forum rules, descriptions and custom error messages.
I hope these changes make it easier to find what you need and get a little help when you need it.
 

I'm thrilled to introduce the newest member of team Invision Community.
You may recognise Jordan from his photo as he's been an active member of our community as BreatheHeavy. Jordan has been running his site BreatheHeavy.com using Invision Community for nearly a decade.
Jordan's official title is "Community Advocate" which means that he will be working very closely with our community to guide and curate feedback, assist with support questions, to help educate and inform and to bring you news of the latest developments being cooked up by our development team.
Jordan says:
Your feedback, ideas and questions matter.
I've spent the last decade discovering what it means to be a community leader in my own Invision Powered community, BreatheHeavy. Community building is an ongoing journey that's taught me invaluable lessons, namely the importance of absorbing feedback from the community then taking decisive action. I'm excited and honored to share that insight with the Invision Community. My new role is designed to shed light on what Invision Community members (that's you!) want and share it with the team.
I'm looking forward to getting to know you! 
We're very excited to start a new chapter within Invision Community to improve communication, engage more Invision Community owners and make the most of the excellent feedback we receive.
You'll be seeing more of Jordan on the forums in the coming days.

The support tool has served us well for many years. You can identify, at a glance, potential issues with your community both presently and down the road, right from the comfort of your AdminCP, and you can often resolve those issues with just a few clicks.
But what if we could do better? What if we could make this useful administrative area of the software even more useful?
The next version of Invision Community introduces a new "Health Dashboard" which replaces the previous support tool and helps you get a better overview of potential issues within your community while retaining all of the functionality you've come to know and rely on to resolve issues with your community.

When you launch the new health dashboard, the first thing you will notice is that the previous "Wizard" process is now gone, in favor of a single page giving you access to everything you might want or need.
Central to the page are blocks that identify specific areas of your community, server, and configuration which could be problematic now or in the future. Invision Community will check for available updates, modified source files, server software configuration issues, whether your server is running required and/or recommended versions of important software and more.
Additional checks and recommendations have been added to this page, to help identify other adjustments that could benefit or prevent harm to your community.  Issues are color coded and classified as informational, recommended, or critical and a summary is provided at the top of the page with an easy "check again" button which will do so without taking you away from the screen.
If we become aware of an issue, we can quickly notify communities through a bulletin which will be displayed in the "Known Issues" block on this page. These bulletins can also trigger AdminCP notifications, however they will continue to show on the Health Dashboard so long as they are relevant, even when the AdminCP notification is dismissed.
A graph showing system, error and email error log activity has been added to the page to help you identify spikes in logged issues. Commonly, if an issue begins to surface on your community there will be an increase in these types of error logs, so the graph here is intended to allow you to identify an increase in these logs, allowing you to investigate and react quicker.
The right-hand sidebar surfaces common tools you may need to access.

The first block allows you to see our most recently featured guides, as well as search our documentation. While this functionality was available in the existing support tool, we found that it was rarely used because people more often visited the tool to allow the software to check for common issues, and the ability to search the documentation required a separate work flow through the support wizard. With the block always available (and searches performed "live" via AJAX), we expect users will find the ability to search our documentation from the AdminCP much more useful now.
Next up, the Tools and Diagnostics block gives you access to common tools you may need to use. You can quickly clear your system caches, as well as access phpinfo, the SQL toolbox (for self-hosted clients only), and disable all third party customizations. The process and behavior for disabling customizations is very similar to the existing process within the support tool, with the list of customizations disabled opening in a modal window and the ability to re-enable all customizations, or selectively re-enable individual customizations, still available.

Disabling customizations is still simple
Finally, the ability to submit a support ticket is still available right from this screen. Upon clicking the button to submit a support ticket, you will be presented with a form inside a modal dialog that behaves very similarly to the existing form with one minor but useful addition: if there are any patches not yet installed on the community, you will be alerted to this right on the form before submitting your ticket. Think of this as one last reminder that your issue may already be solved by installing any available patches before reaching out to us for official technical support.

Submitting a support ticket is still just a few clicks away
We believe the improved workflow and user experience will help administrators and support technicians alike more quickly identify any issues that need addressing on the community.

Wouldn't it be great to know if a staff member had replied to a topic before you clicked to open it?
When you're scanning a list of topics, knowing which have had a reply by a member of the community team can help decide which to read. Currently, you need to open the topic and scan the posts to see if there's a reply from the team.
Happily, in our next release, we've made it clear which have had a reply by a member of a specific group.
You can specify which groups to show as having replied via the Groups form in the Admin CP.

The per-group setting in the Admin CP
You can select to detect the group based on the member's primary group, secondary group or both.
When viewing a list of topics, you will see a badge showing that a member of that group has replied.

This simple feature will make it easier to highlight when important replies have been made to topics, which is a great addition for forums using the new 'solved' feature.

Let me know below if you'll use this new feature and what you'd like to see in the future.

Moats have been used for centuries as a way to defend a building from potential attack.
A flooded ditch around a castle is a great way to make it harder to be taken. You can't push battering rams against walls, and neither can you dig under the castle. Quite frankly, a moat is a pretty decent deterrent when there are plenty of other castles to pillage.
What does this mean for your business?
A community can be an economic moat, or in more simple terms, your competitive advantage.
When your product or service is surrounded by an engaged community that feels invested in your brand, you'll be able to resist challenges from competitors looking to tempt your customers away.
Humans are social creatures, and we love seeking out and joining a tribe that aligns with our values. The intangible value of belonging creates a sense of momentum for your brand and helps champion it to others.
The statistics back this strategy; 88% of community professionals said in a recent survey that community is critical to their company's mission and 85% said that their community has had a positive impact to their business.[1]
Your competitive advantage
One of the cheapest ways to create momentum for your product is to build a community around your startup. A community is much more than a one-time marketing campaign and can help you throughout your company's life cycle if you take the time to grow it right. [2]
Creating a buzz around a product can take a lot of time, effort and money. 
Traditionally, this buzz would be created with a mixture of videos, websites, influencer reviews, and heavy advertisement spends across multiple channels, including social media.
 Your community can create a shortcut and reach an audience without those costs and increase the chance of your product being shared virally. 
Your community creates a bond over a shared interest that continually re-enforces loyalty to your brand. This creates a personal investment which makes it less likely your customers will try a competitor.
Put simply, if a company can move from just shipping a product to building a community, it can benefit from several competitive advantages such as:
Engaged members help acquire new members, lowering the cost for customer acquisition. Increased customer retention through community loyalty. Members won't want to abandon the community they enjoy. Reduced support costs as members support each other. This benefit forms a loop that generates more value as the community grows.

Brand building 
Another area of opportunity for social marketing is "brand building" - connecting enthusiastic online brand advocates with the company's product development cycle. Here, research becomes marketing; product developers are now using social forums to spot reactions after they modify an offer, a price, or a feature in a product or service. Such brand-managed communities can have real success. One well-documented example is IdeaStorm, Dell's community discussion and "brainstorming" website, which saw a measurable increase in sales following its launch, by providing a forum for meaningful dialogue and "to gauge which ideas are most important and most relevant to" the public. [3]
By creating a community around your product or service, not only do you create brand advocates, but you also gain powerful insights into what your customers want through research which drives marketing. 
Consumers today crave a stronger bond with brands. It's no longer enough to give them a customer support email address and a monthly newsletter. They want a much more in-depth interaction with the company and other users of the product or service.
One tactic for success is for brands to move away from the hard-sell to instead embrace the notion of "co-creation". This means moving beyond "old-school" approaches to website advertising to embrace the principles of relationship marketing - building virtual environments in which customers can connect with each other to share insights and relevant information.
To capitalise on currently available opportunities, marketers need to find or establish real brand communities, listen to them, and then create special programs and tools that will empower potential and existing community members, rewarding existing consumers and eliciting behavioural change from potential consumers. [3]
Evernote, the note-taking app, is a great example. Their lively community encourages customers to interact directly with staff, post their wish-lists for future versions and learn more about what happens behind the scenes.
The community creates evangelists for Evernote and makes it harder for competitors to gain a foothold with a potent mix of dialogue, access to other customers, transparency from the brand and many opportunities for co-creation of content.
Co-creation fundamentally challenges the traditional roles of the firm and the consumer. The tension manifests itself at points of interaction between the consumer and the company where the co-creation experience occurs, where individuals exercise choice, and where value is co-created. Points of interaction provide opportunities for collaboration and negotiation, explicit or implicit, between the consumer and the company.
In the emergent economy, competition will center on personalized co-creation experiences, resulting in value that is truly unique to each individual. [4]
In simple terms, a community allows your customers to feel closer to your brand and the products you sell.

 
What are you waiting for?
Nearly 80% of founders reported building a community of users as important to their business, with 28% describing their moat as critical to their success.[1]
Our team at Invision Community has over two decades of community building experience and are trusted by brands of all sizes.
Whether you have an existing community, or you're taking your first steps to create your own, our experience and expertise will guide your success.

[1] https://cmxhub.com/community-industry-trends-report-2020
[2] https://viral-loops.com/blog/your-company-needs-a-pre-launch-campaign/
[3] https://www.researchgate.net/publication/268200746_Social_media_and_its_implications_for_viral_marketing#read
[4] https://www.cs.cmu.edu/~jhm/Readings/Co-creating unique value with customers.pdf

Since the feature was announced at last year’s World Wide Developer Conference (WWDC) we have received lots of requests to implement Sign in with Apple in Invision Community. We’re pleased to announce that as of 4.5 this is now available.
You will need a paid Apple developer account to use it but once enabled users will be able to sign in using their Apple ID and all the convenience that brings. Touch ID and Face ID is supported natively where available and works across all your devices.

Choose to share or hide your email address
Isn’t it just another login button?
Sign in with Apple is built on similar technologies as other login buttons such as those already available in Invision Community from Facebook, Google and Microsoft. The difference is Apple’s unique focus on privacy. On certain community types users can be reluctant to sign up when they fear they need to disclose lots of personal details. Every community is different so allowing your users to share as little or as much info as they like could be important to your success. Apple have stated that no user tracking will take place in contrast to other services where this forms a part of their business model.
When signing in with their Apple ID the user can choose whether or not to share their real email address with your community. If the user chooses to hide their email address then your community will receive a relay email address that will forward to their real address. The email address used is unique to your community so the user can retain control.
Can users link their existing Invision Community accounts?
Yes! If a user signs in using the Apple button and shares their real email address, then providing they already have an account on your community they will be prompted to link their account in the same way as other social login buttons. They can also link an existing account from their account settings. If linking from account settings then the email addresses used do not need to match.
Sign in with Apple is already enabled here on our community and is available in the 4.5 beta available to download now.

We've been on a little journey together since we announced the first Invision Community 4.5 feature way back in November 2019.
The first feature we announced was a revamped Admin Control Panel interface which created more visual space and brightened it up. Actually, we made it so bright that the first feature request was to add a dark mode (which we did).
In the space of three short months, we had spoken about Club improvements, invites and referrals, RSS feed improvements, blog categories, the simple stock photo picker, search insights, security enhancements, user interface updates, new statistic views, and notification improvements.
Most will agree that March and April seemed to last months, thanks to a global pandemic. We used these extra days to talk about marking posts as a solution, topic view summary, Zapier integration, forum view updates, post-installation onboarding, private staff notes, page builder widgets, theme designer improvements, a new default theme, language system updates and everything else we missed.
We have also revamped the front end user interface to modernise the look and feel but also to introduce new CSS frameworks, variables and other time-saving features our design team have been eager to implement.

On the subject of modernisation, we've deprecated some legacy functionality. We've given up trying to make anything look good with IE11 which last saw an update in 2013. We've also deprecated older caching engines like Memcache, APC and Wincache and recommend using Redis instead. The web hosting and domain management features of Commerce are also deprecated as is BBCode. BBCode has its roots in the earliest bulletin-board systems long before rich text editors were common use. It's 2020; we should no longer be asked to type in special codes in square brackets to format text. BBCode is still functional in Invision Community 4.5, but it is likely to be removed in a future version.
Now that primary development has finished, we move onto the beta testing stage. This is where you get to try it out and evaluate the new features before scheduling your own upgrades.
As always, we do recommend that you only test early betas on staging sites or simple test sites. Many a weekend has been ruined by over-enthusiastic upgrading of live sites; so we don't recommend that.
You'll also notice that we're running Invision Community 4.5 on our own site. If you do spot an issue, please let us know in the bug tracker.
I've been creating and releasing products for close to twenty years now, and I still get a real buzz out of hitting the release button. It's always a pleasure to see the result of hundreds of hours of coding, dozens of meetings and numerous passionate exchanges among the team.

You can access the beta in your client area.
We hope you enjoy Invision Community 4.5!

Almost ten years ago we launched the Marketplace; a place to connect Invision Community owners with talented developers creating new functionality.
Over the decade, the Marketplace has grown to hold thousands of applications, large and small. For many Invision Community owners, the Marketplace has become an essential resource.
Our aim was always to have the Marketplace available inside your Admin Control Panel to make it even easier to purchase and install extra functionality.

I'm pleased to say that as of Invision Community 4.5, this is now a reality. You can browse the Marketplace and install new add-ons without leaving the Admin Control Panel.

Obtaining Resources
Paid resources can be purchased directly from the Marketplace and are available to install immediately after the payment is complete. You no longer need to download and install the files yourself.
You may also notice some additional information with the resource listing, we'll be introducing a new 'tab' to marketplace resources to allow the authors to provide more useful information such as answers to frequently asked questions, or configuration instructions etc.

The video below takes you through the purchase and installation of a Marketplace application.
marketplace-install.mp4
Installing an Application
Updates
Some of the eagle-eyed among you may have noticed in the first screenshot that there are more 'bubbles' showing in the menu on the left. These are supported for Applications, Plugins, Themes and Languages.
In Invision Community 4.5 every resource available via the AdminCP is automatically versioned, you will see update notifications for everything you have installed (previously, you would only see update notices if the resource author supports them).
Installing an update is as simple as clicking on the update notice, then clicking 'update' on the Marketplace listing.

Installing Updates
Downloads Changes
Our Marketplace is built on our Downloads application, during development of this feature we needed to add new functionality. We have included as many of these improvements as possible in our software for the benefit of our customers, some of these are:
Custom Fields can now be set to only show to members that have purchased a file. Files can now be set to accept a single file upload instead of multiple. New file versions can now be moderated without hiding the current version from view. Downloads REST API Performance Improvements New /download endpoint that counts the download Added more data to the /downloads/file/{id} response Ability to sort file results by last updated date We hope you're as excited about this feature as we are.

As the deadline slowly comes down, two last feature additions race towards the descending door and slide in underneath with seconds to spare. 
If you've never seen "Raiders of the Lost Ark", then you probably think this is a weird way to start a blog.
As we wrap up development for Invision Community 4.5, we squeezed in two extra features that I want to talk about today.
Per Topic Post Approval
The first is a way to cool down a heated topic without locking it. Right now you can put an entire forum on post-approval. This means that moderators must review and approve all new posts before they are allowed to be publicly displayed.
As of Invision Community 4.5, you can now choose to set a single topic to post-approval regardless of the forum setting.

This is a great way to let a topic cool off but still receive new replies to review before adding to the topic.
Club Terms and Conditions
The ways that clubs are used throughout the many communities that run Invision Community are becoming increasingly varied.
A popular request is to allow members to agree to a set of club-specific terms and conditions before they can contribute to the club.

Invision Community 4.5 now allows the club owner to set up its own terms and conditions. You can optionally enforce that members agree to them before continuing.
That's it for feature announcements. We're excited to be closing development on Invision Community 4.5 and move towards a beta in the coming weeks.

If your brand sells a product or service, the first thing that comes to mind as a benefit to building your community is support deflection.
And it's easy to see why. It's something you can quickly calculate an ROI for. Let's say every 20 hits to a public question with a solved answer from a client or team member equates to one less ticket. If a ticket costs $10 to solve on average, it's straightforward to see the value by calculating deflected tickets. Let's say your busy public support community had 20,000 hits a month; you've just saved $200,000 a month in support costs.
Great! But before you finish there, I want you to consider the rewards a brand community can offer.
A public support desk isn't a community. It's likely most of your customers join because of an issue with your product. They tap in some keywords on Google and come across your site. They see a bunch of solved questions like theirs, and they either get the fix and bounce out, or post and wait for a reply. With nothing to get them to come back, once they have the answer they'll likely bounce out then and only come back when they hit a new problem.
That's not a community. A community is a place where people return multiple times to collaborate, learn and grow together.
"[A brand community is] a group of people who share an identity and a mutual concern for one another's welfare - who participate in shared experiences that are shaped by a brand." - Carrie Melissa Jones
For that, you need to look beyond the support desk and expand into more use cases, and there are compelling reasons to do this.
Shared experiences
Allowing your customers to share their experiences with your products can lead to unique brand stories that reinforce bonds between members and creates social solidarity in the community.
A few years ago, I remember reading a post on a travel community. A family were flying with Delta and their son who has autism was becoming more and more distressed with the change in routine for that day. A Delta employee saw this and came and spoke with the family, helped settle the boy and ensured they boarded early to avoid the crush of passengers.
It's a small moment of kindness that wouldn't make headlines, but it was very memorable for this family; enough so that they posted about it. This post had numerous replies in praise for the airline and no doubt made many of them think of Delta when booking their next flight.
"[Social solidarity is] not just passive tolerance but felt concern for what is individual and particular about the other person." - Alex Honneth "The Struggle for Recognition"
All those stories, connections and moments build social capital and loyalty for your brand.
Feedback
Your customers are already talking about your product. Some of it will be good, and some of it won't be good. They are already talking about it on social media, and in numerous communities, they belong to.
If you do not have space within your community for your customers to leave feedback, then you're missing out on a massive benefit. You get a chance to address negative feedback before it spills out further into the public domain. Likewise, positive feedback makes for compelling customer success stories.
Feedback is a great way to crowdsource innovation and to guide sales and marketing on how your customers are using your products and where the gaps are.
Owning your niche
Allowing space for conversations relating to your product makes good sense. If you sold a fitness tracker, then it makes good sense to have areas for discussions revolving around wellness areas such as sleep, diet and exercise. 
Likewise, a mobile phone network will do well having areas related to the various brands of mobile phones.
"There is status that comes from community. It is the status of respect in return for contribution for caring for seeing and being in sync with others. Especially others with no ability to repay you." - Seth Godin 
Creating these spaces encourages return visits beyond direct support for the product.
Those return visits are what makes your community a community.

One of the most popular requests we get for Commerce is for a free trial period for subscriptions. We've heard from many clients that wish to allow their members a free, or reduced cost trial period before auto-renewing the full price.
I'm pleased to say that we've now added this functionality into Invision Community 4.5. Let us take a look at how it works.
Initial Terms
In 4.5 you can now specify an initial term that is different to the normal renewal term for any subscription plan or product. For example, you could make the initial term $0 for 1 week and the normal renewal term $10 per month which will allow you to create 1 week free trial. The initial term doesn't have to be $0, you can use any special price for the initial term you like.

Subscription Plans showing Free Trials
For developers creating their own applications with Commerce integration, this functionality is also available to you simply by passing a DateInterval object representing the initial term when creating the invoice.
Collecting Payment Details for Free Trials
Previously, if you were buying something that is free, the entire of the last step of the checkout would just be skipped and the invoice marked as paid.
In 4.5, if:
The user is purchasing something which has a free initial period, but also has a renewal term (i.e. is a free trial), and You have a payment method which can collect card details (Stripe, Braintree, etc) The user will be prompted to provide payment details that will not be charged until after the free trial. If the user already has a card on file they will not be prompted to provide the details again but will see a confirmation screen rather than the order just being marked paid immediately.

Checkout Process for a Free Trial
As you can see, allowing a free or reduced cost trial period has never been easier. We hope that you enjoy using this new feature of Invision Community 4.5.
 

We have announced a lot of new things coming soon with Invision Community 4.5. Most of these are pretty big new features worth a blog on their own.
However, we've made a lot of smaller changes that may not deserve their own blog but still have a significant impact.
Let's run through some of those.
Performance Improvements
For every major release, we take some time to run through the code and look at ways to make Invision Community run more efficiently.
For Invision Community 4.5, we've made node forms, sitemaps and commonly run SQL queries more efficient, which is excellent news for you and your users who get reduced server load and a snappier community.
TikTok Embed
Although it confuses me greatly, TikTok has taken the internet by storm. We have added it to the embed list so pasting a TikTok share link automatically shows the video ready to play in the comment.

A TikTok
Upload Chunking
Uploading large files can be tricky. Typically trying to push a large file to a server results in timeouts, memory issues and eventually frustration. We have added chunked uploading when using S3. Put simply; this uploads part of the file at a time to prevent memory issues and the server timing out waiting for the upload to finish.
View Members by Rank
Very recently, we were asked how you can view all members in the ACP of a specific rank. It turned out you couldn't. This quick change was added into Invision Community 4.5.

Showing members with a specific rank in the AdminCP
Download Statistics
While Invision Community 4.5 has new and improved statistic displays, a common request was to be able to download the raw data. This is now possible.

Export stats as a CSV
Downloads
In Invision Community 4.5, when you require approval of new versions of files submitted to Downloads, the original version will no longer be hidden from view. We've added a new flow for moderators to approve these new versions.
Live Meta Tag Editor
Invision Community 4.5 seemed like a great time to run through this feature and tweak the functionality to make it more useful. Now it's possible to remove default meta tags, and it's easier to remove custom tags.
Closed Tag Autocomplete
When using the closed tag system where a user can select from one of your preset tags, we have added a search box to make it easier to find a single tag from a list of potentially hundreds.
EU Tax Support in Commerce
Tax doesn't have to be taxing! But it generally is. Countries within the EU often have complex tax rates. Commerce now supports multiple tax rates for consumers, businesses and EU VAT-registered businesses.
That concludes our mini round-up of all the things we've not talked about yet. Let me know which one you're looking forward to most!

Ever since Invision Community 4.0, there has been a huge focus on making communities multi-lingual by providing translation features inside the AdminCP.
We have received a lot of feedback on our multi-lingual and translation tools over the past year, and we're happy to announce these new features coming to Invision Community 4.5.

Pages Phrase Tools
If you have the Pages application, you can also use these phrases in HTML pages and HTML Blocks without needing to visit the translation tools area. Simply use the tag editor in the sidebar when editing a page or block's contents.



The new phrases sidebar options
You can quickly create new multi-lingual phrases by clicking the + icon.

The new add phrase dialog
Additionally, WYSIWYG Blocks have now been made translatable, so you can now create WYSIWYG blocks that will display their content in specific languages.
Translation Tools
Language pack creators can now set a version update URL which is checked to notify admins within the AdminCP that an update available, just like the theme system. This is a great way to notify customers when fixes are available.

Finally, you can now quickly add a new phrase from the Translation Tools page without the need to use the developer tools.

The new "Add Phrase" option

These little changes should make a huge difference in your workflow, and make it easier than ever to create fully multi-lingual pages throughout your site.

If you've been around Invision Community for a while, you'll know our frontend default theme hasn't significantly evolved since the early days of 4.0. Indeed, the last significant refresh came with 4.2.
With the upcoming release of 4.5, we wanted to revisit the default theme and give it a facelift for 2020, as well as make incremental improvements to the underlying codebase as a stepping stone to a bigger re-engineering in a future version.
In this entry, I want to talk a little about some of the design decisions that went into building the new theme.
Goals
Redesigning for the sake of it is never a good idea, so we first laid out what we wanted to achieve:
A brighter UI with more saturation & contrast and simpler overall color scheme Improved typography Better, more consistent, spacing around and between elements, especially on mobile Better logical grouping of sections of each page Reducing underutilized links/buttons on the page and finding alternative ways of making them available Improving how post states are displayed Modernizing and enhancing the underlying code that powers the default theme Let's talk a little about each of these.
 
Brighter UI
The most obvious change will be that our default colors are brighter and more saturated than before. Before making any changes, we first created a color scale for both neutrals and the brand color (blue, of course). This gave us a flexible but consistent palette of colors to choose from, with appropriate contrast built in. Neutrals have a touch of blue too to avoid seeming washed out.
We've simplified the style, in particular reducing reliance on background colors to differentiate sections within cards (a card essentially being an ipsBox, for those who are familiar with our framework). Instead, we use spacing, borders and appropriate typography to achieve visual separation.

Brighter default colors
 

Simplifying the UI by removing block backgrounds
 
Improving typography
We've felt our typography has been somewhat muddled for some time - with a mixture of sizes, weights and colors used depending on the particular context.
The first step to improving it was to create a typography scale that we could refer to and implement, to ensure we remained consistent throughout the product.

Our typography scale
(The keen-eyed amongst you may also notice we've switched our default font to Inter. Inter is a fantastic open source font that is ideal for text on the web, and was recently added to the Google Web Fonts project making it super simple for us to incorporate it into our default theme.)
We've been much more deliberate about applying type styles, especially for titles, ensuring that they are always visually distinct from surrounding text. We've done this through both color and weight. As a result, pages should instinctively feel more organized and logical than before.

An example of improved typography, from the Downloads app
 
Improved spacing (especially on mobile)
We identified that spacing (padding and margins) needed some improvement. A lot of spacing values were arbitrary and inconsistent, leading to poor visual harmony across any given page.
Most troubling of all, on mobile sizes we simply halved desktop padding values. While this was a reasonable approach in the days of phones with small screens, it has felt decidedly dated for some time. Phone screens are now typically larger and able to accommodate roomier UIs without appearing comical.
In 4.5, we have done away with that approach, and the impact was immediate. Mobile sizes now get a much more pleasant interface, with elements having room to breathe. In addition, we've also made most cards full-width to provide additional breathing space for content.

Posts can finally breathe on mobile
 
There are numerous other tweaks across the product too: default spacing has been increased a little, data tables (e.g. topic listing) get extra vertical spacing, and spacing between elements has become more consistent.
 
Improved grouping of related elements
Prior to 4.5, most content areas existed inside cards. However, one notable exception to this was page headers and as a result, they could feel particularly disorganized, especially for users who had many controls in this part of the page (such as staff).
To solve this problem, we've developed a new, standardized design for content item page headers, giving them their own cards and consistent button placement.

Topic view header
 
Some areas don't necessarily fit into the same design pattern above. In those areas, we've tweaked styling to suit the context, while still adhering to our overall aesthetic.

Calendar header

Messenger conversation header
 
Reducing underutilized links/buttons
Finally, another area we identified as needing improvement is the abundance of tools, made up of links and buttons, across pages. Many of these are only used occasionally and so would be better moved out of the main view to simplify the page.
Two particular areas we focused on were share links and postbits (both forum posts and comments in other apps).
Research shows social share links are used by a vanishingly small percentage of users, so even though they were at the bottom of the page, it was unnecessary to make them so prominent (given their eye-catching colors). To solve this, we've added a share link to the page header, with the social network links themselves in a popup menu. The result is ideal: sharing functionality is unobtrusive but obvious.

Share links in content items
Comment areas have also suffered from 'button creep' over the years. A typical comment will contain a report link, a share link, a quote link and multiquote button, reactions, plus IP address, checkbox, edit and options links for certain users. That is a lot of visual noise around the important part: the content.
We've therefore simplified comment boxes as much as is reasonable. Reporting and sharing comments/posts is now available in the post options menu, as are any tools for the author/staff. Quoting and reacting are two primary interactions for users, so they of course retain their position in the control bar.

Simpler postbits, even for staff
 
Improving post states
Posts/comments in Invision Community can have many states - sometimes more than one. Posts can be hidden/unapproved, popular, recommended, solved (new in 4.5!) or highlighted because of the author's group. It's always been a challenge to indicate these statuses well.
In previous versions, we added a border but the most prominent indicator was a flag in the top-right corner of the post. This had three problems:
Due to the lack of space (thanks to report/share links), showing more than one flag was difficult. Showing any flags on mobile was messy because of the space constraints. The meaning of the flags was not obvious, especially to new users. Group-highlighted posts had no flag, just a border, which made them even more difficult to understand. With the top-right corner of posts now tidied up and free from fluff, we were able to much more effectively use this space to indicate post statuses.
In 4.5, posts and comments will show badges when they have a particular status, as well as a more attractive semi-transparent border. For group-highlighted posts, we show the group name instead (the colors of this highlight are still controllable via theme settings).

A post with two states: group highlighted and popular
This works much better on mobile too, where the status badges get the prominence they deserve:

Mobile post statuses
 
Modernizing the underlying code
I wrote about the technical improvements behind the theme in a previous entry. If you're a theme designer or edit the theme for your own community, go and check it out now!
 
Wrapping up
As well as these large-scale concepts, you'll notice many other smaller enhancements as you start using the new theme.
I've shown some snippets of pages in the screenshots above, but I've included some full-page views below so you can see the overall aesthetic and how these pieces fit together.
Modernizing and refreshing our default theme has been needed for some time, but we view this as just a stepping stone to future work that will be reserved for a major version bump, and we're excited to figure out where we go next.
 
Screenshots
  
Desktop forum views (click to expand)
 
    
Mobile forum views (click to expand)
 
 
Activity streams & messenger (click to expand)
 

If you've been around Invision Community for a while, you'll know our frontend default theme hasn't significantly evolved since the early days of 4.0. Indeed, the last significant refresh came with 4.2.
With the upcoming release of 4.5, we wanted to revisit the default theme and give it a facelift for 2020, as well as make incremental improvements to the underlying codebase as a stepping stone to a bigger re-engineering in a future version. Keep an eye out for our next blog for more on the facelift.
In this entry, I want to go over some of the design and code-level changes we've implemented that will be of particular interest to third-party theme designers, or those building a custom theme for their community.
IE11 Support
Until now, we've supported IE11 as a 'B' browser - meaning we didn't aim for perfect support (especially visually), but did aim to make all functionality work, and we fixed IE11-specific issues if possible.
As of 4.5, we no longer support IE11 in any way and Invision Community will not work well in that browser. By removing support for IE11, we are able to make use of newer CSS technologies which significantly eases development for us and third-party designers. I'll discuss some of those below.
Combined theme settings
We've combined a number of existing theme settings into one new setting. We've found that settings like poll_bar, step_background, rating_hover and so on are nearly always set to the same color - typically the site's main brand color. These settings have therefore been replaced with one new brand_color setting, which is used throughout the CSS in places where this primary color would be needed. This will simplify the early stages of theme development and make it easier to match branding in Invision Community.

Front end colors
Removing hardcoded colors
While our theme settings have allowed community owners to change most colors, there were still many hardcoded in our CSS framework. These were typically neutral colors used for things like 'close' links, semi-transparent backgrounds and so on, but it was enough to make creating a dark theme an unrealistic prospect without an awful lot of effort (and kudos to those designers who have offered dark themes up until now!).
In 4.5, we've removed hardcoded colors from our framework, and instead rely on colors already defined by theme settings. You can now, finally, create a dark theme just by editing the built-in theme settings.
Type scale & {fontsize} tag
While we've had fixed type-size classes (e.g. ipsType_normal) for a long time, in practice many elements had their own font sizes set. This leads to inconsistency and poor visual rhythm too. Another side effect is it was also tough to globally change the font size (such as for branding purposes, or to create a theme for visually-impaired users).
To solve these problems, we first created a type scale; that is, a fixed number of sizes to choose from. A product the size of Invision Community does have need for a flexibility, so we settled on the following scale:
x_small: 12; small: 13; medium: 14; base: 16; large: 18; x_large: 20; 2x_large: 24; 3x_large: 30; 4x_large: 36.
All of these values are editable as theme settings, so each theme can adjust the type scale used. Our default CSS in 4.5 has been fully updated to put all type on this scale.
To actually make use of these settings, we have added a new {fontsize} tag which accepts either a scale key, or a specific pixel size (for those occasional situations where a specific size is absolutely needed, e.g. icons).
Why couldn't we just use {theme="x_small"}, or even CSS variables? To solve the problem of globally scaling text, we have also added a percentage-based scale setting that will save you from having to create your own type scale. The {fontsize} tag automatically applies the global scale to any values passed into it. Want text in your theme to be twice as big as default? Simply set the global type scale to 200% and the entire theme will reflect the change immediately. 

The new font size options
Spacing scale
The lack of a consistent spacing scale has led to some arbitrary values being used in any given situation, which again has had a negative impact on the visual harmony of our design. We've therefore implemented a 4px spacing scale (using CSS variables rather than theme settings this time) and applied across almost all padding/margin values. In time, we anticipate fully switching all measurement values to the scale.
New CSS class families
We have added a range of new spacing classes for padding and margins, allowing far more control over how these are applied, especially on different device sizes. Previously, ipsPad (15px) was simply halved on small screens - with no 'opt-out' short of adding specific CSS. We've felt this has been imprecise for some time, especially since mobile devices typically have larger screens in 2020 and don't need to be so tightly-spaced.
ipsPad_all now replaces the existing ipsPad, and does not halve itself on small screens. Instead, there's a new responsive naming convention that allows you to apply specific padding on specific device sizes:
ipsPad_all:double md:ipsPad_all sm:ipsPad_all:half
In this arbitrary example, desktop size (the default) get double padding, medium (tablets) get regular padding and small (phones) get half padding.
We've added similar classes for top, bottom, left and right padding, as well as horizontal, vertical and none (to removing all padding) shortcuts.
For margins, the old ipsSpacer_* classes have been replaced with a new ipsMargin family that work exactly the same as the padding classes above, with the same range of flexibility.
The old ipsPad/ipsSpacer classes will continue working as they did before for backwards compatibility, but should be considered deprecated from 4.5 onwards.
We've also added a whole range of new ipsFlex classes, also with responsive controls (making it easy to have horizontal layouts on desktop and vertical layouts on mobile, for example), as well as a new ipsGap utility that automatically adds spacing between elements, without requiring manual :first-child/:last-child exclusions.
CSS variables & calc()
In 4.5, thanks to IE11 support ending, we're finally making use of CSS variables and calc() to make CSS more maintainable and easier to customize. A lot of repeating or often-customized styles - such as form field styles, message colors, card styles, border radii etc. - are now created as CSS variables, allowing theme designers to easily change styling in one place. Instead of magic numbers, we either stick to our spacing scale, or use calc() to avoid hardcoded numbers.
The future
The work we've done so far is just a 'first-pass'. We'll be pressing forward with modernization throughout the 4.5.* series and beyond with a view to reducing our footprint, improving our ability to maintain our CSS and, of course, making theming easier for our customers.

Installing Invision Community for the first time is a fun and exciting process. After all, you're about to launch a new community that is going to thrive and attract members from all over, and you want to make sure you set it up just right to facilitate a painless experience for your visitors.
If you're new to Invision Community, however, it can be a little daunting when you think about "ok what now?" immediately after installing the software.
Though experience, and researching the analytical data Invision Community installations voluntarily share with us, we identified many common settings that most communities change, and it is easy to see why. In an effort to make Invision Community more approachable to new administrators, we have devised an intuitive "new installation" onboarding process that will help you configure the community just right, and quickly.
Upon first logging in to Invision Community after installing the software, administrators are presented with a welcome screen.

Welcome to your new Invision Community!
You can obviously skip this step by clicking away to another page if you wish, and you won't be bothered again. If you click the "Skip this step" link on the page, you will be sent an email with a link to return to the page in the future should you wish to do so.
Continuing into the helpful wizard, you will be presented with a screen like so

A helpful guided wizard
You'll note that there's an explanation as to why you may wish to configure these settings, as well as guidance for where to find the same options later should you wish.
Upon clicking next, you'll see the previous step marked as completed. You can even skip around steps by clicking and expanding on them should you wish to do so.

Each step is explained in detail
If you reached this page but decide that you have to do something else first, there is a "Remind me later" option at the bottom of the page. Clicking it will allow you to resume whatever else you need to do first, but will helpfully bring you back to this onboarding step at a later time to finish your quick setup.
Finally, once you submit the form you will be presented with a confirmation page containing links to several other areas that you may wish to visit to get started. Things like setting up forums and setting up groups are common tasks, so we've consolidated links to those areas on one helpful screen as part of the new quick setup.

Confirmation that you're doing great so far!
This change is but one small way that we strive to ensure our software is easy to understand and easy to use. The next time you set up a new community, we hope these adjustments make the process smoother for you, allowing you to get the backend work done quickly so you can focus on the real goal - growing your new community.

Invision Community has had different view modes for a good number of years.
Forum grid view was added to create some visual interest when listing forums, and we've had expanded and condensed view modes in streams since they were introduced.
We've taken both of these views a step further in Invision Community 4.5
Forum Grid View
To create even more visual interest, the grid view now allows you to upload, or choose a stock image for the header. This instantly makes for a more dynamic and inviting forum list.

The new grid view image headers
You can choose an image from the Admin CP when creating or editing a forum.

Choose a stock photo, or upload your own
Topic List View
For the topic list view, we have taken inspiration from our stream view options to introduce a new 'expanded' view mode, which displays a snippet of the first post.

The new expanded topic list mode
This immediately entices you to engage with the topic because you can read part of the post without having to click inside to see if it interests you.
This is controlled via the Admin CP, where you can choose the default view, or turn off the new view completely.
Other Changes
You may notice a few other subtle changes in these screenshots. The first is that we now included the follower count as a metric on both the forum grid view and the topic expanded view modes. The number of followers is usually a good indicator of how others perceive the value of the content. A higher follower count generally means a more engaging topic or forum.
You can also see that we've switched to a short number format to keep the displays clean. Instead of say, "2,483 posts", it will merely say "2.5k posts". Reducing visual clutter is always crucial to maintaining a clean user interface.
We hope that you find these new view modes useful and that they make your community even more vibrant!

Zapier is a service that allows you to connect over 2,000 web apps. In Invision Community 4.5 we are launching a beta service of Zapier integration for Invision Community in the Cloud.
What does Zapier do?
Zapier acts as a bridge between Invision Community and other apps, such as Google Docs, Twitter, Facebook, Slack, Trello, Facebook Ads, ActiveCampaign, Zendesk, Asana, Salesforce, Hubspot, Discord, Stripe and more. Zapier has over 2000 apps registered currently, and that number grows every single day.
Let us look at a real life example.
Right now, if you wanted to add a member to a Google Sheets document each time a new registration was completed, you'd need some fairly complex code to be written that was "triggered" by this registration event. This would take days to write at some cost.
Zapier simplifies this by allowing you to connect Invision Community with Google Sheets without needing a single line of code. Zapier allows you to streamline your workflows in minutes.
Zapier has two types of events, triggers and actions.
Triggers
When a certain thing happens on Invision Community, like a member registering or a topic being posted, a trigger can be sent to Zapier to then run actions in other apps. For example, you might create a zaps to...
When a member registers, add their email to a Mailchimp list. When a moderator posts a topic in a news forum, share it on Facebook, Twitter and other social platforms. When a member posts something that requires moderator approval, send a message to a Slack channel for your moderators.
Invision Community Integration with Mailchimp through Zapier
Actions
You can also set up Zaps so that when something happens in an external application, it triggers an action in your Invision Community. For example, you might create a zaps to...
When you add an event in a Google Calendar, create a Calendar Event on your community. When you receive an email to a feedback email address, create a topic on your community in a forum for moderators. When you create a task in Trello, add a record to a Pages Database on your community.
Invision Community Integration with Google Calendar through Zapier
Self-Integration
In addition to using Zapier to integrate with third party services, you can also connect an Invision Community trigger to an Invision Community action. For example: when a member registers, create a topic in a welcome forum.

Self-Integration through Zapier
Frequently Asked Questions
What integrations are available?
In the beta launching with Invision Community 4.5, Zapier will be able receive a trigger when a member account or content (forum post, gallery image, etc.) is created and send actions to create the same. More triggers and actions will be added over time. When will this integration be out of beta?
Later this year. Will third party applications and plugins be able to create Zapier triggers and actions?
Because the integration requires an app hosted with Zapier (which is written in Node.js) and this has to be submitted directly by the vendor, it will be difficult for third party applications and plugins to integrate with Zapier through Invision Community's integration. In the future we may be able to provide basic abstracted integrations for third party applications and plugins through an extension API. In the meantime, third party authors can of course write their own Zapier Apps if desired.

A topic is more than a collection of posts; it's a living entity that ebbs and flows over time.
Evergreen topics can see month-long gaps between posts and longer topics spanning numerous pages can end up hard to navigate through to find useful content.
With this in mind, we've added numerous improvements to the topic view to bring context and summaries key areas within the topic.

Topic view updates
Topic Activity
The first thing you likely spotted in the above screenshot is the new sidebar. This acts much like a summary of activity within the topic. It very quickly lets you know how old the topic is and how long it has been since the last reply. This context is essential if you are unwittingly replying to an older topic.
Most topics are driven by a handful of key members. The topic activity section shows you who have been most active, which may influence which posters you give greater authority to.
Likewise, popular days lets you dig into the 'meat' of the topic which may have evolved quickly over several days.
More often than not, a single post attracts more reactions if it is particularly helpful or insightful, and this is shown too.
Finally, a mini gallery of all upload images allows you to review media that has been attached to posts.

The topic activity summary under the first post
This activity bar can be shown either as a sidebar or underneath the first post in a topic. If you enable it for mobile devices, then it will show under the first post automatically.

The topic activity summary on mobile
As with many new features in Invision Community, you have several controls in the Admin CP to fine-tune this to your communities needs.

AdminCP settings
Other improvements
The eagle-eyed among you will have spotted a few other changes to the topic view.
The first is the badge underneath the user's photo. The shield icon notes that this poster is part of the moderation team. Of course, this badge can be hidden for communities that do not like to draw attention to all their moderators.

You will also notice that when the topic starter makes a reply to a topic, they get an "author" badge as their reply may carry more authority.
When you scroll down a topic, it's not often apparent that there has been a significant time gap between replies. For some topical topics (see what I did there) this may alter the context of the conversation.
We have added a little identifier between posts when a period of time has passed between posts.

These changes add a little context to the topic to give you more insight into how the replies direct the conversation.
The new topic activity summary gives you an at-a-glance overview of key moments and posters to help you navigate longer topics.
We hope that you and your members enjoy these new features coming to Invision Community 4.5!

Invision Community has certainly changed a lot over the years as we've moved through major updates and large user interface changes. 
While large scale changes offer a dramatic difference, it is sometimes the smaller changes that bring the most satisfaction when using your community daily.
This blog entry rounds up some of the UI improvements Invision Community 4.5 brings.
Content View Behavior
What do you want to happen when you click a topic link? Are you taken to the first comment, the last comment or the first comment you've not read? If you speak to 100 people, I'm pretty sure you'll get a good spread of votes for each.
Invision Community has always offered subtle ways to get right to the first unread comment. Our infamous dot or star allows you to do this, but it is so subtle almost no one knows this.
Invision Community 4.5 now allows each member to choose (with the AdminCP offering a default).

Now everyone wins!
Who Reacted?
Invision Community has had reactions for a long while now. Although finding out who exactly reacted without clicking the counts has proved irksome.
We've fixed that in Invision Community so simply mousing over the reaction icon reveals who reacted.

Sign In Anonymously
For as long as I can remember, Invision Community has offered an option to sign in anonymously via a checkbox on the login form.
However, as we've added faster ways to log in via Facebook, Twitter, Google and more it's become less straight forward to ensure your anonymity.
Invision Community 4.5 removes this login preference and moves it to your members' settings.

Now your members can resume hiding as they move around your community across multiple logins.
Resize Before Uploading
One of the most popular requests we've had in recent times is to resize large images before uploading. It's quite likely that your giant full resolution image will be denied when attempting to upload, and it's a bit of a faff to resize it in a photo editor.
Invision Community leverages the uploader's ability to resize before uploading, which makes it a much happier experience.
Switch Off Automatic Language Detection
Invision Community attempts to map your browser's user-agent to a specific language pack.
When you visit a site, your browser lets the site know which language our browser is set to (often dictated by your operating system) and we use that to show you the correct language if the community you're visiting has multiple languages installed.
However, it might be that you don't want this to happen because although your computer's OS is set to a specific language, it doesn't always follow that is the one you wish to use on a website.
Invision Community 4.5 allows this automatic detection to be switched off.

Quote Collapse
We will finish with another popular feature request; the ability for long quotes to be collapsed, reducing the amount of scrolling one has to do.
Quite simply, Invision Community collapses long quotes with an option to expand them to read the entire quote.

Thank you to all our customers who have taken the time to leave feedback. As you can see, we do listen and action your feedback.
Which change are you looking forward to the most? Let us know below!

Although we continuously review security within Invision Community, a major release such as 4.5 allows us to be especially proactive when it comes to keeping your community safe.
This blog entry outlines several enhancements to improve security in Invision Community 4.5.
Password Handling
Keeping your member's passwords secure is the simplest way to keep accounts safe and out of the wrong hands, so it makes sense to look at ways to ensure this doesn't happen.
Invision Community already uses strong one-way hashing when storing passwords, which means that once the password is stored in the database, there is no way to know the plain text version.
However, when creating a new member account via the AdminCP, a random password was created, and this was sent in the welcome email to the new member's email address.
As of Invision Community 4.5, this no longer happens, and the new member is invited to create a new password when visiting the community for the first time.

Part of your internal security procedures might be to force a reset of all passwords periodically. Invision Community 4.5 allows this on a per-member basis, or via a selection of filters to enforce a reset for many members at once.

This clears out any stored password hashes and emails the affected members to remind them to set up a new password.

AdminCP Security
The Admin Control Panel contains the most powerful tools available to Invision Community. This is already a very secure area with a separate login with an option to add two-factor authentication to the login flow.
Part of the session authentication has been a special key in the URL. While we have protection in place to prevent this special key being discoverable by a malicious user, there remains an incredibly remote theoretical chance that this could happen with a series of complicated steps. There was an additional annoyance that you are unable to share links within the AdminCP to members of your team due to the increased protection to keep URLs safe.
As of Invision Community 4.5, we have removed the special key from the URL and moved it elsewhere in the session authentication flow. This means that it's impossible to fetch the special key via the URL and links can now be shared and will survive a login action.
Text Encryption
There are a few areas within Invision Community that we use text encryption to allow us to save data in the database in a format that is encrypted when saved and decrypted when read. This protects you in the incredibly remote event of your own hosting being compromised and your database downloaded (of course, our Community in the Cloud customers do not need to worry about this!)
Invision Community 4.5 improves on this encryption by using PHP's built-in methods which give "bank-level" security to our encryption.
Security is critical to the success of your community, and we are always proactive in improving security throughout Invision Community.
Do you have any comments on this entry? Let us know below!

Every single day, your members are searching your community for answers or interesting conversations to join.
Wouldn't it be great if you could learn what is being searched for to identify hot issues, commonly asked questions and discover trends?
We thought so too, which is why Invision Community 4.5 comes with search statistics.
For the first time, Invision Community gathers anonymized information on what your members are searching for so you can use this to highlight more relevant content and shape strategic decisions with your community's structure.

Search statistics help you track searches performed on your community
When a member searches, their identity is converted into a unique key that cannot be reversed to identify the member. This allows us to track a single member's search usage over many search sessions without being able to link it to a specific member account.
The AdminCP now features a dashboard to review the most popular search terms as well as a raw log of recent searches along with the results they returned.
We have a lot of ideas in mind for additional changes down the road with the tracking of popular search terms, but for now, we hope you like the new statistics page and find the information presented useful for your future site plans.

Ever since Invision Community 4.x was launched you have been asking for the ability to categorize blogs in your community.
We heard you loud and clear, but sometimes when a feature sounds straightforward, it requires some re-engineering of the framework. Because users in your community can create both blog entries and their own blogs to hold these entries, this was one of those areas.
Starting with Invision Community 4.5 I’m pleased to announce that it is now possible for blog authors to categorize their blog entries and it's now possible for administrators to categorize blogs.

Blog Entry Categories
When creating a new blog entry, your members will now be able to create a new category for the entry or choose an existing one that had been created previously.

Choosing your category when creating a new blog entry
When a reader then visits the blog they can choose to display only those categories that interest them.

Filtering by category
Blog Categories
Running a community where users can create their own blogs, you don’t only need to make sure individual pieces of content are categorized correctly, you also need to make sure the blogs themselves have a logical place. Well guess what? Now you can!
As an admin you can now set up predefined categories in the control panel and Blog authors can then choose which one to create their new blog in.

Managing blog categories
We realize some of you have been waiting a long time to see these changes so we hope you enjoy this and everything else to come in Invision Community 4.5!

When the clocks strike midnight on New Year's Eve, we will enter the third decade of producing Invision Community.
A lot has changed since we set up in 2002. Our team has grown and our product matured. In a world where online startups explode and die within a few years, we're something of an anomaly.
We still have the same love and passion for creating the very best tools to build a community, and we have always ensured that Invision Community is in touch with modern demands.
This decade has seen Invision Community go from strength to strength. In 2010 we were one of many forum systems catering to smaller niche audiences. In 2019 we're powering discussion for many international and well-known brands.
Online habits may have changed in this time, and social media may have swallowed up smaller informal communities, but the need for independent community platforms remains strong.
2020 will see us release 4.5 which will bring another round of essential updates to existing features and a fresh batch of new features.
But first, let us climb inside our Delorean, rewind the clock to 2010 and start from the beginning.
As the sun rose on 2010, Bruno Mars was singing about parts of the human face in "Just the way you are", Katy Perry irritated Microsoft Word's spellchecker with "California Gurls", and CeeLo Green was trying to "Forget you" (at least in the radio edit).
Christopher Nolan's boggled all our minds with Inception, James Franco lost the ability to clap in 127 Hours, and Colin Firth stammered his way through The Kings Speech.
Steve Jobs unveiled the iPad to a collective snort, moderate derision and questions over just how useful a giant iPhone will be.
President Obama, just a year into office warns of "Snowmageddon" that eventually dumps up to 40 inches of snow on the east coast of the United States.
We lost comedy legend Leslie Nielsen (we'd never dream of calling him Shirley), and we gained a small child named Ryan who in just nine years would be earning $29,000,000 by opening boxes of toys on YouTube.
62% of us were using Internet Explorer to the chagrin of most web developers who wished that Chrome's 5% market share was more significant.
Facebook celebrated its sixth year by reaching 400 million users (a far cry from the 2.5 billion it currently has). Twitter, just four years old hits 30 million monthly active users (and none of them talked about fake news).
And how about Invision Community?
2010
We hit 2010 running by releasing numerous updates on IP.Board v3.1, including finally using long-established web standards, and share features now that "social networking is all the craze these days" noting that "friends and colleagues often share similar interests, after all."
How innocent we all were in 2010.

IP.Board 3.0
Back then, each product had its own name and release cycle. IP.Gallery's new features included being able to rotate images by 90 degrees. Honestly, people used to go crazy for this stuff.
In May, we released a brand new application called "IP.Commerce". A few months later we renamed it "IP.Nexus" and years later, it was changed back to "Commerce". Naming things is hard.
The announcement contained exquisite details such as "It's hard to say when it'll be available" and "we don't know how much it will cost". We were so sure that it would be accepted positively, we removed the ability to post comments to the blog entry.
As summer turned to autumn and the end of the year loomed large, we released news about a significant update to Gallery called "IP.Gallery 4.0" which pre-dates Invision Community 4 and confused customers for years (so IP.Board 3 works with IP.Gallery 4, but IP.Board 4 works with Gallery 4?). Numbering things is hard too.
The last blog entry was about an app called 'IP.SEO' that I had utterly forgotten existed. It was written by Dan who once locked Lindy out of his own datacenter, but we don't talk about that.

I don't even remember this website
2011
Charles opens the year by managing expectations for IP.Board 3.2 by outlining our three key goals (promotion, usability and modernization). The last one was us removing the "back to top" button and then spending the next eight years explaining why we removed it.
Our spam monitoring service processed 300,000 requests in the first two weeks of 2011. 30% of these requests were deemed to be spam and blocked (0.1% was probably an administrator registering 50 fake accounts before being banned from their own site).
I posted about "exciting new technology" in our new "WYSIWYG" editor (although what you see is sometimes close to what you get) would be more appropriate but slightly less catchy. We spent the next eight years explaining why no one uses BBCode anymore to almost everybody.
Brandon closed out the year with a blog promising "new toys" for IP.Content 2.3 (now called Pages, keep up!) which promises a "who's online" widget and a "shared media field" that was not only complicated to explain, but also use.

IP.Board 3.2 in all its glory
2012
We start the year with news on IP.Board 3.3. This release was to feature essential updates such as the "Remember me?" checkbox on the login form and emoticons in signatures.
Despite being constantly told that we don't take SEO seriously, we round up the latest serious SEO changes including tags, soft 404s and micro schema.
We also celebrated our tenth year in business.
Something terrible must have happened to one of our competitors because we asked if you'd like to switch to IPS.
The year ends with IP.Board 3.4 being released for beta testing. This being a rare year where we release two major versions in less than 12 months.
2013
Brandon has eight coffees and tries to explain what it's like to be a developer: "us developers are a strange bunch. We have a lot of crazy thoughts that just don't make sense to anyone else. Our brains are wired differently. We get from point A to point B by going around point Z and bouncing off point M first.", he closes the blog entry by urging you to ignore us.
The big news is that work on 4.0 is officially underway! Don't get too excited, releasing two major versions in 2012 clearly fatigued us as "IPS Community Suite 4.0" is not released until June 2015, over two years later.
4.0 was our first complete rewrite in years. We threw out all our stable and tested code and started over with an empty editor. It was a vast undertaking that consumed us completely. The result was worth it as we had a new modern framework that still serves us today. But we're getting ahead of ourselves a little.
Back in 2013, Mark talks about trees. Not the kind you find laying around in forests, but rather the programmatic type. It's just a way for Mark to show off how beautiful his code is.
IP.Board 3.4 still gets many updates (along with IP.Gallery, IP.Blog, IP.Content, IP.Downloads and IP.Address (ok that last one was made up)).
We spend the year talking about various new things in 4.0, including a new-new editor and various special features (and no one noticed we started calling it "IPS Social Suite 4.0" - it just rolls off the tongue!)
I introduce the new theme engine for 4.0, and this time, my code is not deleted by Mark (true story).
2014
We didn't know it at the time, but 2014 was not the year that IPS Social Community Suite 4.0 (naming things is hard) will be released. Still, Rikki talks enthusiastically about "extending JS controllers and mixins"  a way of coding so complex, to this day you can count the number of people who truly understand it on one of Rikki's fingers because it's only Rikki that understands it.
Determined not to be outdone in the confusing customers' stakes, I go on about how important it is to convert your database to UTF-8 when upgrading from 3.0.
As 2014 neared its inevitable end, we did manage to put up a pre-release testing site and release Beta 1 a release so unstable; it makes the current political climate look absolutely peachy.

 IPS Community Suite 4.0 (Preview)
2015
Finally, the year that 4.0 is to be released! We released six betas and a few release candidates before nervously hovering over the 'release' button (actually it's a collection of git commands and 'to the letter' instructions I ignore).
After a  year of training customers to call our forthcoming release "IPS Social Suite 4.0," we release it as "IPS Community Suite 4.0". Lindy writes a lengthy blog article that sounds like a cross between a technical discussion of the Brother 8987-A printer and an award acceptance speech.
Quite frankly, after nearly two years of development, we're just relieved to have finally released it.
The year is spent refining and fixing 4.0 and culminates in the news of 4.1, where we add activity streams and a menu manager. We also talk about the new-new-new editor.
December 16th marks the time that IP.Board 3.4 officially dies as we declare it "end of life" and no longer support it. That shiny new release we were excited to talk about in 2012 is finally put out to pasture. The last we heard, IP.Board 3.4 moved to a farm and is doing well.
2016
Now that IP.Board 3.4 is end of life; we do the sensible thing and make a few minor IP.Board 3.4 releases to improve security.
IPS Social.. sorry, Community Suite hits version 4.1.17 (confusing Lindy) before the year is done with many new improvements, including embeds, warning notes and the new leaderboard.
We're still mostly undecided what to call the product, so we avoid trying in all our blog entries.
In fact, looking back, it's quite remarkable how often we changed the name of our product. You'd be forgiven for thinking that it was a robust and well-considered attempt to prevent Google from serving up relevant search results and to confuse potential customers.
We find time to update our own website and introduce a new developer's area.
2017
Barely 16 days into the new year, and we release news of the two-factor authentication feature added to IPS Community Social Invision IP.Board Suite 4.1.18.
When spring has sprung, Charles drops the news that we're working on 4.2, the main feature being a screenshot of the Admin CP log in. We promise that you will love it and that it will be released mid-2017.
Updates come thick and fast. Calendar event reminders, content messages, recommended replies, letter profile photos device management and delayed deletes all make the blog.
Still not convinced that people take us seriously when we say we're committed to SEO, we post about more SEO improvements.
This time, we talk about implementing JSON-LD, rich snippets, pagination tags and more.
We also squeeze another one in about the new-new-new-new editor.
We overhaul our own blog (using Pages because that's how we roll) and I start a hilarious series of blog entries where I troll our own team. Everyone including me loses interest early on in 2019.
During April, we do the sensible thing and change the name of our product once more. IPS Community/Social Suite 4.1 is out, and Invision Community 4.2 is in.
Just to recap: IBForums > IPB > IP.Board > IPS Social Suite > IPS Community Suite > Invision Community.
You're welcome search engines!
As promised, we release Invision Community 4.2 around the middle of the year. Well done, everyone! We finally hit a release date!
As is now tradition, we end the year with news of our next big release Invision Community 4.3 (and tease the new emoji feature). We also calm nerves about Europe's endless fascination with regulation (it's this kind of joke that caused Brexit you know) and wrote up a guide on GDPR.
2018
Phew. We're almost there, dear reader. If you skimmed through most of the blog to this point and expected me to finish with a bang, you'll be disappointed.
We start 2018 at full speed releasing feature news on Invision Community 4.3 including emoji, OAuth, community moderation, REST API, subscription manager, announcements and more.
Oh and we hit our sweet sixteenth birthday in February!
We release Invision Community 4.3 in April to rapturous applause after a short beta testing period. We all agree that 4.3 was a great stable release which instantly makes the developers nervous.
Towards the end of the year, we announce that work has begun on Invision Community 4.4. We talk about new features such as GIPHY integration, AdminCP notifications, Post Before Registering, Commerce Updates and more.
Still not sure if we care about SEO? Well, how about another blog entry on SEO?
The only thing missing this year is a new update on our editor.
2019
And we arrive back home in 2019. A week into January and I pull the massive twist that we're using Invision Community 4.4 on our own community. It's not quite up there with "Bruce Willis is a ghost" though.
In March we write up a case study on The Trevor Space, an LGBTQ charity set up to prevent suicide and to provide crisis intervention. TrevorSpace commends Invision Community for allowing anonymity online which isn't possible with social media.
Rikki drops a bombshell in September when he announces that we're actively working on native iOS and Android apps for Invision Community. Apparently mobile is a thing now.
November starts a series of blog entries talking about our new upcoming release, Invision Community 4.5. We talk about the Admin CP overhaul, Club Pages, RSS Feed Improvements and Club improvements.
And here we are. Right up to date. This decade may have only taken us from IP.Board 3.1 to Invision Community 4.5, but it really has seen a massive change in the company we are, and the industry we are in.
We have seen the inception, rise and stumble of social media. While it's true that forums are no longer the preserve of Star Trek fans obsessing over continuity errors and informal communities have been absorbed by Facebook and friends, spaces that you completely own to host discussions are still very much in demand.

Invision "Chameleon" Community in 2019
Over the past year or so we've seen a sustained rise in the demand for independent communities. Brands especially like that you own your data and can use it to gain insights into customer habits. Just this year, we've launched communities for LEGO, HTC, Sage, Mattel, Gibson Guitars, Squarespace, and many more.
We are constantly evolving Invision Community (assuming we stick with that name) to be at the very centre of your online presence. We have tools to add discussion comments to any page of your site, to embed widgets with a few lines of code. We want to showcase your community throughout your site by adding multiple touchpoints to take your customers on a journey with you. Our native apps will offer new and exciting ways to interact with a community via new interfaces.
As we move into our third decade, I can only see a resurgence for independent communities as we tire of the crushing intrusion of social media. We give away so much of our attention, time and information for very little reward.
We have never been more divisive and fiercely tribal.
It's time to come back together to discuss a topic with care and thoughtfulness. It's time to allow our personalities to take a back seat and let considered discussion live again.
And we'll be here doing what we have always done; creating the very best community platform possible.

I'd love to know when you joined us on this crazy ride. Was it before or after 2010?

You'd be forgiven for thinking that RSS feeds belong in some bygone era of the web where Netscape was king and getting online meant listening to your modem scream at your phone line.
There's certainly a lot of newer web technologies to share data, but the venerable RSS feed still has a place.
Invision Community has supported RSS feed importing and exporting for a very long time now; however, it has been restricted to just Forums and Blogs.
Importing an RSS feed is a simple way to populate content on your community. It's even a great way to share content to and from your site without creating blocks or writing custom code.
Invision Community 4.5 now centralizes RSS feed importing, so it is available for Forums, Blogs and Pages.

You can now choose to import an RSS feed to any Pages database. Better yet, there is now full support for image enclosures.
RSS feeds have a special tag to note that the feed entry has an attached image. Lots of RSS feeds use this, such as the NASA Image Of The Day feed. Until now, this image has just been silently discarded.

Now, it is imported as an attachment (so it can be moved around in the post or Pages entry). If the Pages database you are importing to has record images enabled, you can optionally import the enclosure as a record image which some template sets can use as a header image, just as our blog here does.

But what about exporting enclosures?
Happily, Invision Community 4.5 can now export the main content image of an item as an enclosure. This certainly makes the Gallery RSS feed export a lot more useful!

While these updates are not revolutionary, they certainly make RSS feed importing and exporting much more useful. We've been asked to support RSS feed importing into Pages for quite a while now.
What do you think of these changes? What will you import into your Pages databases?