Jump to content

Stuart Silvester

Invision Community Team
  • Posts

    3,621
  • Joined

  • Last visited

  • Days Won

    26

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Stuart Silvester

  1. I've had a look at the ticket, we do have some further Elastic search changes in 4.4.7. I would recommend upgrading when it's available and then rebuilding your search index. If the problem persists, let us know via a new ticket.
  2. I don't see the ticket you're talking about, can you give me a ticket ID?
  3. It is coming in a future release, most likely 4.5.0. You will need to continue using ES6 until then.
  4. We don't have native support for this time, but that's also something we could implement easy enough (since OpenID Connect uses OAuth). There is some basic pricing information on here: https://invisioncommunity.com/services/sso/ but I would recommend emailing our sales team for a quote (click the contact us button on the right)
  5. SAML is a bit more complex than things like OAuth, it is not something that is natively supported at this time. Based on experience, most authentication providers that support SAML also have OAuth 2 support which is natively supported in Invision Community (It's also much easier to set up). We can provide a bespoke SAML-based solution if required, please see here for more information: https://invisioncommunity.com/services/sso/ Personally, I would look at using OAuth if it's a solution that's available to you.
  6. Elastic Search 7 isn't supported at this time, you will need to use version 5 or 6. We will be adding support for v7, but I cannot confirm exactly when that will be yet.
  7. You would need to write a plugin to overload \IPS\Text\Parser::_htmlPurifierModifyHtmlDefinition() to whitelist your custom attribute on the chosen tag. I would recommend taking a look at that method to see how we're whitelisting certain attributes. Allowed JavaScript controllers is purely for controllers (data-controller attributes that we use to load JS)
  8. No it's a front-end thing only, core.front.core.lightboxedImages is a front end controller only. In the AdminCP, you could just add data-ipsLazyLoad to your container tag
  9. We use whatever PHP defines as the 'default' algorithm in your PHP version. At the current time, that is blowfish for all PHP versions. Argon2ID was added in PHP 7.3 and would be eligible to be the default algorithm in PHP 7.4/vNext, although there's no guarantee they'll do that. http://php.net/password_hash
  10. You are assuming that if member validation is enabled, that everyone will validate. This isn't true for anyone that signs in with an SSO (be it Custom, OAuth, Facebook etc) or anyone that registers (when purchasing an item) in Commerce. You would be better to just use onCreateAccount() and make sure you have onDelete() supported for accounts that get removed (currently there are only methods for onCreateAccount() and onValidate())
  11. We have a very important announcement to make! There are times where you need to get the attention of your visitors. You might be closed on certain days of the year, performing server maintenance (if you are consider our Cloud Plans, they're excellent) or running a competition. Invision Community has always had an announcements feature baked in, but we felt it could be improved. Okay, maybe this feature isn't as flashy as some of the others we're introducing in 4.3, but these useful features should make managing your community easier. The new look announcement feature replaces the old widgets enabling you to display customisable announcements in any of the following locations; Top of the page Above the page content In the sidebar The three new announcement locations Each location has some slightly different features; the page top banner is dismissible by the member if they no longer want to see it, whereas the banner above the content and the sidebar announcements cannot be dismissed. Most of the original customisable features are still available, including the ability to select which applications and pages show certain announcements and which member groups can see them. Combining this with the three new locations gives you much more flexibility for different types of announcements and we've also included the option to customise the color of the announcement. New customisable options The announcements have also been improved to contain more information. Rather than showing an unformatted snippet along side the title, announcements can now be tapped to open a modal showing any further details. Modal showing announcement content We hope you'll enjoy these useful improvements in Invision Community 4.3. Stay tuned for further announcements (pun intended)!
  12. /applications is a folder on the file system where the applications are stored.
  13. JsonLD data was restored in 4.2.4 beta 2, I'm also seeing it working in communities that have been upgraded to Beta 2.
  14. No problem! You can also find a list of third party developers here: https://invisioncommunity.com/third-party/providers/
  15. We've done custom SSO projects for InfusionSoft in the past, please see https://invisioncommunity.com/services/sso for further information.
  16. This is actually a bug that's fixed in 4.2.3, they should be displaying a letter photo instead. p.s. support issues and bug reports should be submitted via a ticket in the client area.
  17. This is an entry about our IPS Community Suite 4.2 release In previous versions of IPS Community Suite we have had an account history feature in our Commerce application. This feature showed many important actions that may be relevant to the customer such as when an invoice was generated or when a customer changed their account details. In IPS Community Suite 4.2 we have expanded this functionality and moved it into the core functionality of the suite. Member History Member Overview Member actions that will be logged include (but are not limited to) Email address change Display name change Password change Account merge Primary group change (The reason will be shown when triggered by an automatic group promotion) Secondary group change Flagged/Unflagged as spammer Multi-Factor Authentication (Enable / Disable / Opt-out) Social media (Twitter, Linked In, Facebook, Google, Twitter, IPS Connect) for enabling, disabling and which (if any) were used to register an account. The Commerce customer account page will now show actions that may be related with a transaction or account. Member History on the Commerce customer view Discoverability Each action is also discoverable via the IP Address tools built into IPS Community Suite 4 Member History in IP Search We’ve also made the data table filterable Member History Search Notes for developers: The new Member History system has been designed with interoperability in mind. In IPS Community Suite 4.2 you will be able to integrate your own applications into this system. Member History replaces the display name changes system.
  18. No, this tool is only for users that have upgraded from 2.3 (and should only be ran once). We removed it in 3.4.7.
  19. That really isn't required, anyone following this instruction will permanently delete any data stored by those 3rd party applications and be unable to upgrade to their IPS4 version. The upgrade process will remove any 3.x themes and plugins.
×
×
  • Create New...