jcdesign reacted to Mark for an entry, 4.3: Take payments with Apple Pay and more with Stripe and Commerce
Stripe is the most popular payment method in Commerce, allowing communities to take payments by card securely with easy setup.
While there's no doubt that credit cards are still the most popular methods of making a payment, digital innovations such as Apple Pay are increasing in popularity.
For 4.3 we've deepened our integration to support some of their latest features.
Apple Pay & Google Pay
Apple Pay allows users to pay quickly with their iPhone, iPad or Mac (with Safari and either a paired iPhone or using the MacBook Pro with Touch ID) using the card details stored on the device, authenticated with Touch ID or Face ID.
Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
Paying with card details stored in Google Chrome
Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
Commerce will automatically hide the option if the user's device does not support either method.
Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
Amex Express Checkout
American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information. This is also now supported through Stripe in 4.3.
Amex Express Checkout
Alipay, Bancontact, Giropay, iDEAL, SOFORT
These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
All of these are also now supported through Stripe in 4.3.
A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).
All transactions with currently open disputes can be accessed quickly from the transaction list. The transaction page will show you the status and reason for the dispute, and links to your Stripe dashboard where you can respond.
When the dispute is resolved, the transaction screen will be updated, with either the transaction being marked as refunded if the dispute is lost, or going back to paid if the dispute is won and the funds returned to you.
A dispute that was lost
A dispute that was won
Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
jcdesign reacted to Mark for an entry, 4.3: Scaleable search and interface improvements
Search. Let's be honest, it's not the most exciting feature in the world. You ask to find things, and it shows you what it found.
It's a lot more complex than that. After numerous tests, a few surveys and many discussions with customers, we've decided that there is no "right" or "wrong" way to search. Invision Community is used on many diverse communities and each has its own needs.
The bigger the community, the more of a headache search can be when you start hitting frustrating technical limitations of the database.
Happily, we've addressed all of these issues with Invision Community 4.3 and added a few extra treats.
Searchable Products and Pages
Products in the Store and custom Pages will now show in search results.
Store product in search results
More Customisable Search Experience
One of the most difficult challenges with search is anticipating the scope of the search. If, for example, you're looking for something you know you've seen before, you want the search to be narrow - matching only the exact terms you provide, probably only matching against the title, in the specific area you know where the content is located. If however, you're just doing a general search about a particular subject, you want the search to be wide - matching any of the terms you enter, anywhere in the community, in both titles and content.
For a while, Invision Community has had the option to choose which areas to search, defaulting to the area of the community you're in (for example, if you're in a forum, only that forum will be searched by default). We also provide a number of suggestions on the search result form (in the form of "Didn't find what you were looking for? Try searching for..." followed by a number of options) which adjust the scope of the search.
In Invision Community 4.3, we have a new interface for the quick search feature which makes some of these options more visible so you're more likely to find what you're looking for on the first search.
New Search UI
Along these lines we have also:
Changed the default "Search In" selection to "Everywhere", regardless of where the user is. Added a new setting which controls whether the "Any words" or "All words" option is checked by default. Added a new setting which allows you to adjust how much of a boost results receive for a match in the title, versus the content body, when searching both content titles and body. You can set default and/or operator.
New Search Settings
In Invision Community 4.3 we are adding native support for Elasticsearch, a third party search engine which offers a number of benefits over searching your MySQL database:
Elasticsearch, being designed and indexing data in a way optimised for search rather than data storage, is generally able to match and sort by relevancy with better accuracy than MySQL. Elasticsearch is generally faster. One user performing a search doesn't slow down other users trying to read and make posts at the same time (when searching MySQL, the data has to be "locked" from changes when the search is being performed). It scales very well with very large datasets, and runs very easily on multiple servers. Elasticsearch understands language. If for example, you search for "community", it will also return results which contain the word "communities", understanding that these are the same. Supported languages are Arabic, Armenian, Basque, Brazilian, Bulgarian, Catalan, Chinese, Czech, Danish, Dutch, English, Dinnish, Drench, Galician, German, Greek, Hindi, Hungarian, Indonesian, Irish, Italian, Japanese, Korean, Latvian, Lithuanian, Norwegian, Persian, Portuguese, Romanian, Russian, Sorani, Spanish, Swedish, Turkish, Thai. Elasticsearch supports custom functions on the scoring algorithm. In our initial implementation this has allowed us to add settings to allow you to control the time decay (allowing newer results to show higher) and author boost (allowing content posted by the user to optionally show higher in results). Unlike with MySQL, there is no minimum query length and a very small list of stop words.
When enabled, both searches and activity streams will be retrieved from Elasticsearch. The core_search_index database table in MySQL will no longer be populated, so you will not have to store the data twice.
To use Elasticsearch, you can either install it yourself on your own server, or use any of the many excellent hosted Elasticsearch options. The minimum required Elasticsearch version is 5.5.
Developers and those looking to integrate Invision Community features into their own sites will be pleased to learn that we've extended the REST API to accommodate searching.
jcdesign reacted to Matt for an entry, New: Fluid Forum View
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.
The database stores the members' view choice. This remembers the selection across devices. Guests are not permitted to change between views.
jcdesign reacted to Daniel F for an entry, New: Downloads Index Page
This entry is about our IPS Community Suite 4.2 release
In IPS Community Suite 4.2 we have added a bunch of new settings for the Downloads Index Page.
Downloads Index Page - Settings
With 4.2 you'll be able to hide any of the boxes.
Hidden Most Downloads Box
Another often requested feature was that people want to be able to choose the categories from where the files should be fetched
This way you'll be able to hide files from some very old categories.
jcdesign reacted to Matt for an entry, IPS Community Suite 4.1.19 Available
Version 4.1.19 is now available in the client area!
This release focuses on bug fixes and performance along with some new key features.
Ability for members to lock and unlock their own content
We've added a new group level option to allow members to lock and unlock their own content. This is disabled by default.
Messenger Quota Display
To help diagnose issues your members may find, we now display their personal message quota in the ACP.
Default view for Activity Stream
When creating a new activity stream, you can specify either expanded or condensed as the default view. This is especially handy for streams you wish to share with other members.
Other key changes include:
Performance and speed improvements. A new moderator setting to restrict users from ignoring moderators. A new group setting to hide a group from filters in search. When moving content moderators are now prompted for where you want to be redirected after the action. An email is now sent when an account is locked for too many bad login attempts. Check out the Release Notes for a full list of changes.