Jump to content

Mark

Clients
  • Posts

    36,220
  • Joined

  • Last visited

  • Days Won

    114

Reputation Activity

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

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  2. Like
    Mark got a reaction from stefano_els for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  3. Like
    Mark got a reaction from rhyker2u for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

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

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  5. Thanks
    Mark got a reaction from zbahadir for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  12. Thanks
    Mark got a reaction from kysil for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  13. Like
    Mark got a reaction from vanderbroms for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  14. Like
    Mark got a reaction from JwilsonVW for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  15. Like
    Mark got a reaction from TAMAN for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  16. Like
    Mark got a reaction from TAMAN for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

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

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

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

    An uploaded video in a browser without playback support for that format
  18. Like
    Mark got a reaction from JwilsonVW for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  20. Like
    Mark got a reaction from Faqole for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  21. Like
    Mark got a reaction from Josiah Wallingford for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  24. Like
    Mark got a reaction from motomac for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  25. Like
    Mark got a reaction from OverPlay for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  26. Like
    Mark got a reaction from OverPlay for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  27. Like
    Mark got a reaction from SeNioR- for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  31. Like
    Mark got a reaction from Teascu Dorin for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  32. Like
    Mark got a reaction from Thomas. for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  37. Thanks
    Mark got a reaction from sobrenome for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  38. Thanks
    Mark got a reaction from grande_ecks for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  41. Like
    Mark got a reaction from Real Hal9000 for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

    An uploaded video in a browser without playback support for that format
  42. Like
    Mark got a reaction from sudo for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  62. Thanks
    Mark got a reaction from IceCore for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    An uploaded video in a browser without playback support for that format
  69. Like
    Mark got a reaction from Silnei L Andrade for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

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

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

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

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

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

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

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

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

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

    An uploaded video in a browser without playback support for that format
  73. Thanks
    Mark got a reaction from The Old Man for a blog entry, 4.3: Videos   
    Videos are everywhere. We shoot them on our smart phones, share them to social media, messengers and more.
    Up until now, the only way to share a video to Invision Community was to use a service like YouTube or Vimeo. If you uploaded a video file it would be treated like an attachment, and if the user clicked the link it would download it to their computer.
    In Invision Community 4.3 we've improved this. Now if you upload a video file (mp4/3gp/mov/ogg/ogv/mpg/mpeg/flv/webm/wmv/avi/m4v), it will embed similarly to an image.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    An uploaded video in a browser without playback support for that format
  91. Like
    Mark got a reaction from Stuart Silvester for a blog entry, 4.3: AdminCP Member Profiles   
    Viewing and editing a member is probably one of the most frequently used features of the AdminCP. With the design unchanged for many years, and the tabbed interface starting to grow unwieldy, it was due for some love. We have not only dramatically improved the design but added many new features.

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

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

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

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

    A member that has been locked



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

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

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

    Warnings & Restrictions Block for an account which has content moderation in effect
     
    Account Activity
    On the right is a pane which shows all of the latest account activity. While this was available in previous versions (called "Member History") we have made some significant improvements:
    The number of things that get logged has been significantly expanded. We now log photo changes, group changes, when a new device is used to login, if an account is locked (by failed logins or failed two factor authentication attempts) or unlocked, password/email/display name changes, when a user links or unlinks a social network login method, initial registration and validation, merges, being flagged/unflagged as a spammer, receiving/acknowledging/revoking a warning, restrictions being applied, two factor authentication being enabled/disabled/changed, an OAuth token being issued if Invision Community is being used as an OAuth Server, enabling/disabling receiving bulk mails, and accepting the privacy policy / terms and conditions, as well as all of the Commerce-related information that is already logged. Much more information is now shown such as who made the change (i.e. an admin, the user themselves, or if it was changed by the REST API or syncing with a social network) and how the change was made (for example, for a password change - if the user used the "Forgot Password" tool or changed it in their Account Settings) and what the data was before and after. This includes being aware of if the change was made by an admin after using the "Sign in as User" tool. You can now filter what information you are seeing to quickly find what you are looking for.
    Recent Account Activity
     
    Extensibility
    The new profile has been designed with extensibility in mind. Third party developers can easily add new blocks our even entire new tabs. Any apps/plugins which are currently adding a tab to the "Edit Member" form will retain backwards compatibility with their tab continuing to appear when clicking the "Edit Preferences" button in the basic account information pane.
  94. Thanks
    Mark got a reaction from Devrix for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  95. Sad
    Mark got a reaction from SeNioR- for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  96. Thanks
    Mark got a reaction from SeNioR- for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  97. Like
    Mark got a reaction from SeNioR- for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  98. Like
    Mark got a reaction from Cyboman for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  99. Like
    Mark got a reaction from Windwalker222 for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  100. Thanks
    Mark got a reaction from levsha for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  101. Like
    Mark got a reaction from ايمن for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  102. Thanks
    Mark got a reaction from Thomas. for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  103. Like
    Mark got a reaction from LiquidFractal for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  104. Like
    Mark got a reaction from RObiN-HoOD for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  105. Like
    Mark got a reaction from bfarber for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  106. Like
    Mark got a reaction from Tripp★ for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  107. Thanks
    Mark got a reaction from shahed for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  108. Thanks
    Mark got a reaction from The Old Man for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  109. Like
    Mark got a reaction from Ioannis D for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  110. Like
    Mark got a reaction from crmarks for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  111. Thanks
    Mark got a reaction from O9C4 for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  112. Thanks
    Mark got a reaction from Emanoel for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  113. Like
    Mark got a reaction from Qubabos for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  114. Like
    Mark got a reaction from DawPi for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

    Ability to remove features from clubs
     
    Other Minor Tweaks
    You can now set per-group the maximum number of clubs a member in that group can create. A member invited to join a club can now delete the invitation if they do not want to accept it (rather than just ignoring it).
  115. Like
    Mark got a reaction from Meddysong for a blog entry, 4.3: Paid club memberships, and other club improvements   
    We released news of Clubs just under a year ago for Invision Community 4.2 and it has been the best received feature to date.
    Clubs opens up new ways to run your community by allowing members to create sub-communities away from the central forum area.
    Since the feature was released, we've collated an immense amount of feedback on the feature. Here's what we're improving for Invision Community 4.3.
    Paid Club Memberships
    If you have Commerce installed on your community, 4.3 adds the ability for members to create paid clubs. Users wishing to join the club will be required to pay a membership fee (which can be one off or recurring) which will be paid to the club owner, minus any commission you want to keep for the site. You can choose which groups can create paid clubs.

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

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

    Paid club after request to join has been accepted

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

    Waiving fee when approving request to join

    Waiving fee when inviting members

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

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

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

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

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

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

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

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  117. Like
    Mark got a reaction from Marc Stridgen for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  118. Like
    Mark got a reaction from Rhett for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  119. Like
    Mark got a reaction from steve00 for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  120. Like
    Mark got a reaction from motomac for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  121. Like
    Mark got a reaction from Silnei L Andrade for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  122. Thanks
    Mark got a reaction from Cyboman for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  123. Like
    Mark got a reaction from OverPlay for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  124. Like
    Mark got a reaction from Ioannis D for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  125. Like
    Mark got a reaction from sobrenome for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  126. Like
    Mark got a reaction from The Old Man for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  127. Thanks
    Mark got a reaction from Aaron M for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  128. Like
    Mark got a reaction from opentype for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  129. Like
    Mark got a reaction from Brian A. for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  130. Like
    Mark got a reaction from Myr for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  131. Like
    Mark got a reaction from Emanoel for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  132. Like
    Mark got a reaction from Real Hal9000 for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  133. Like
    Mark got a reaction from Meddysong for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  134. Like
    Mark got a reaction from David.. for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  135. Like
    Mark got a reaction from jcdesign for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  136. Thanks
    Mark got a reaction from grande_ecks for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  137. Like
    Mark got a reaction from DawPi for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  138. Like
    Mark got a reaction from Tom S. for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  139. Like
    Mark got a reaction from Andy Millne for a blog 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.
    Apple Pay
    Google Chrome (on desktop or Android devices) supports a similar feature allowing users to pay with card details stored in their Google account with Google Pay, or stored in Chrome itself.
    Paying with card details stored in Google Chrome
     
    Both of these features are now supported through Stripe in Invision Community 4.3. Setup is simple - for Apple Pay you simply need to verify that you own your domain by uploading a file you obtain from the Stripe dashboard, and nothing special is needed for Google Pay - and then create the payment method in the AdminCP. Stripe does not charge any additional fees for either option.
    Commerce will automatically hide the option if the user's device does not support either method.
    3D Secure
    Also known as Verified by Visa, Mastercard SecureCode, and other brand names, 3D Secure is a system that is used to verify a customer's identity before purchase is completed and transfers the fraud loss liability from the merchant to the cardholder bank in case of fraudulent disputes.
    After the user has entered their card details, they are redirected to their bank's website and asked to provide additional verification.
    Our integration with Stripe in 4.3 now supports this process. A new setting allows you to choose if you want to use 3D Secure just for cards which require it (i.e. cards which would decline the payment if 3D Secure is not completed) or for all cards which optionally support it as well.
     
    Amex Express Checkout
    American Express cardholders can use Amex Express checkout to pay by using their American Express login rather than providing their card information.  This is also now supported through Stripe in 4.3.
    Amex Express Checkout
     
    Alipay, Bancontact, Giropay, iDEAL, SOFORT
    These are popular payment processors internationally (Alipay is popular in China, Bancontact in Belgium, Giropay in Germany, iDEAL in the Netherlands, and SOFORT in several European countries).
    The checkout experience is similar to PayPal with the user being redirected to the appropriate site, authenticating the payment, and then being redirected back.
    All of these are also now supported through Stripe in 4.3.
     
    Dispute/Chargeback Handling
    A dispute (also known as a chargeback) occurs when one a cardholder questions your payment with their card issuer, which causes the funds, plus a fee, to immediately be taken from your account until evidence is provided that the transaction was legitimate.
    Anyone operating an online store knows how frustrating this experience can be. In 4.3, we've made dealing with this situation a little easier. When a dispute is created, Commerce will now mark the transaction as disputed, which will immediately revoke any benefits from the purchase (for example, if it's for a subscription that moves them into a different group, they will be placed back into their original group; if it's a Downloads file, they won't be able to download it any more; if it's for a physical item that hasn't been shipped yet, the shipping order will be placed on hold).

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

    A dispute that was lost

    A dispute that was won
     
     
    Radar
    Radar is Stripe's suite of fraud detection tools using machine learning and customisable rules to help detect fraudulent transactions.
    Stripe will automatically blocks transactions is considers highest risk already. However, for "elevated" risk transactions, while Stripe would alert you of them so you could review them, Commerce would process the transaction normally.
    In 4.3, Commerce will place any transactions which Radar reports as having an "elevated" risk level on hold for manual review, so you can decide whether to approve or not before the funds have been captured.
    In addition, the transaction details screen for Stripe transactions now provides some additional information about Stripe's checks on the transaction, including the Radar risk level, if the CVC check passed, and if the billing address provided matches the card's billing address.
    If a fraudulent transaction does make it through, you will now have the option to indicate this when refunding the transaction to help Stripe's anti-fraud systems learn.
  140. Thanks
    Mark got a reaction from Firdavs Khaydarov for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  141. Like
    Mark got a reaction from A.Man.Br for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  142. Like
    Mark got a reaction from bfarber for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  143. Like
    Mark got a reaction from Lindy for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  144. Like
    Mark got a reaction from Xiaodidi8 for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  145. Like
    Mark got a reaction from LukasGr. for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  146. Like
    Mark got a reaction from Emanoel for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  147. Like
    Mark got a reaction from OverPlay for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  148. Thanks
    Mark got a reaction from The Old Man for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  149. Like
    Mark got a reaction from Yamamura for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  150. Thanks
    Mark got a reaction from shahed for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  151. Like
    Mark got a reaction from Silnei L Andrade for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  152. Like
    Mark got a reaction from BomAle for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

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

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


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

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

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


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

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

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

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

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  153. Like
    Mark got a reaction from sadel for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

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

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  154. Thanks
    Mark got a reaction from Cyboman for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  155. Like
    Mark got a reaction from Ramsesx for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  156. Like
    Mark got a reaction from Ehsan1111 for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  157. Thanks
    Mark got a reaction from 13. for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  158. Like
    Mark got a reaction from Meddysong for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  159. Thanks
    Mark got a reaction from ipbhero for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  160. Like
    Mark got a reaction from SoloInter for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  161. Like
    Mark got a reaction from Ioannis D for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
  162. Thanks
    Mark got a reaction from DawPi for a blog entry, 4.3: Sign in from other sites using OAuth   
    The best way to convert guests into members is to make the onboarding process as simple as possible.
    Over the years, we've added special log in methods for Facebook, Google, LinkedIn and Microsoft. We've carefully hand coded these integrations to allow guests to sign up with just a few clicks using services they're already a member of.
    These services used to use proprietary methods to link with other websites, but a new standard has emerged.
    OAuth
    You may not know it, but you're probably familiar with OAuth already. If you have enabled the ability for users of your community to sign in with their Facebook, Twitter, Google, LinkedIn or Microsoft account, you may have noticed that the process for setting up each of these is quite similar. This is because they all use the OAuth protocol.
    In Invision Community 4.3, we are introducing several exciting new features:
    In addition to all of the existing social networks above, which retain their "easy setup" status, we have also added Wordpress. Users on your community can now sign in with any Wordpress site you control (you will need to install a Wordpress plugin to enable OAuth capabilities). As well as those "easy setup" options, we have also added the ability for you to allow users on your site to sign in with any OAuth 2.0 based provider. This means, for example, if your community is based in a location where other social networks are popular, if they use OAuth, you can set those up too. While the setup is a little bit more complicated, this doesn't require any custom programming - you'll just need to find out a few more pieces of information from the provider (an example is provided below). Invision Community itself can now also serve as an OAuth 2.0 server so you can set up other sites to be able to facilitate logins using credentials from your community. This works in conjunction with our REST API, allowing you to make API calls as an authenticated member, which will return just the information that user has access to. With the ability for Invision Community to serve as both an OAuth server and client, this now provides standard integration for multiple Invision Communities together, which will now replace the old IPS Connect feature. We have also taken this opportunity to make a few other minor tweaks to login, registration and account management features, especially for communities which rely heavily on non-standard login methods (more details below).  
    Setting Up a Custom OAuth Provider
    For this example, I'm going to use vk.com, which is a popular social network in Europe. While Invision Community doesn't provide this as one of the "easy setup" options, it is based on OAuth 2.0 so we can use the new functionality in Invision Community 4.3 to set it up.
    In older versions, the list of login handlers in the AdminCP had all of the providers listed with enable/disable toggles - because now you can add as many custom handlers as you like in 4.3, it's now a list where you can add/delete options:

    Login Handlers List
    When clicking the "Create New" button, you'll see all of the different handlers Invision Community supports. Since vk.com isn't in the list, but is still OAuth 2.0-based, I'll choose the "Other OAuth 2.0" option:
     
    Choosing a Login Handler
    You'll now need to use the documentation provided by the site you want to integrate with to fill out this form. While no custom programming is required, the documentation is usually quite technical in nature - but you only need a few key pieces of information. We anticipate that for some of the more popular options, guides will be provided to help you find the information you need.
    I have created an application in vk.com's developer center and so I will copy and paste my credentials into the form:

    Inputting vk.com credentials
    I then need to find the endpoints from vk.com's documentation and input those too.

    Inputting vk.com endpoints
    Next I need to find the endpoint where I can access the user's information within their API and the parameters they are returned by. The only required piece of information is an ID, but you can also provide the parameters for accessing the display name, email address and profile photo. If display name/email address isn't available/provided, the user will be asked for this the first time they sign in. vk.com's API doesn't provide access to the email, but I can use the screen name as the display name, and they do provide access to the photo:


    Inputting vk.com User Information Endpoint and response parameters
    Finally, provide a logo and a color for the sign in button and some final settings:

    Inputting vk.com Logo and Button Color
    And now vk.com login is set up. A button will now show up on the front end which I can use to sign in. I didn't provide a way to access the email address, so on the first sign in, the user will be prompted to provide that, but the screen name and profile photo from vk.com will be used:

    Signing in with vk.com
     
    Using Invision Community as an OAuth Server
    You can also set up Invision Community itself to be an OAuth Server. This may be useful for two main reasons:
    If you want to integrate two communities together, or integrate with something else which supports adding custom OAuth clients. If you are a developer and want to use the REST API using OAuth for authentication rather than an API Key. You can either make requests as an authenticated user (by obtaining an access token) or using Client Credentials. The screenshots below show the full capabilities which are quite technical and mostly aimed at developers. If you will just use this feature to link two communities, don't be concerned if it looks too complicated, an easy-to-follow guide will be available to achieve that.
    You will set up the clients from the AdminCP:


    Setting up an OAuth Client
    When creating the OAuth Client, you can control which scopes are available, and which endpoints of the REST API they provide access to:

    Defining OAuth Client Scopes
    The login process is then the standard OAuth flow, and users have the ability to view authorisations in the account settings:

    Authenticating an OAuth Client
    The REST API has new and updated endpoints to be aware of the authenticated user:

    A new REST API endpoint which returns details of the currently authenticated user

    An updated REST API endpoint which, when called using OAuth authentication, will only return data the authenticated user has access to
     
    Other Login System Tweaks
    Users can now choose if they want to change their local display name or email address if it is changed by an external login method (or the administrator can choose this behaviour). If there is an issue with this (for example, it wants to change the email to one that is already taken), or profile photo syncing, this is now better communicated to the user. You can now control per-login-handler if new registrations are allowed using it. This addresses some confusion from previous versions as to if the "Allow New Registrations" setting applies to accounts being created by social network logins. The Standard login handler can be disabled if you rely totally on an alternate login method. To allow this to happen:  All areas where a user is prompted to re-enter their password (some areas of the account settings) now allow reauthentication using any login handler. You can disable local registration but still allow accounts to be created by other login handlers, or redirect users to an external URL to register an account. You can also disable or redirect to an external URL for changing email address / password or the Forgot Password tool. You can now create multiple instances of the external MySQL database and LDAP login methods which have also had some other minor tweaks: The external MySQL database handler now has PHP's password_hash() function as an available option for password encryption type, and defining a custom encryption method is now much easier, done entirely in the AdminCP without needing to modify PHP files. You can now choose if changes to the local display name / email address / password is synced back to the external database / LDAP database. You can optionally show these handlers in the Account Settings pages like other login handlers to allow users with an existing account to link their accounts. You can define a Forgot Password URL for the external database which the user will be redirected to if they try to use the Forgot Password tool and that is how their account is authenticated. 
×
×
  • Create New...