Jump to content
View in the app

A better way to browse. Learn more.

Learn more

Stuart

Invision Community Team
  • Joined

  1.    Stuart reacted to a post in a topic: 4.7.26 is now available!
  2.    thompsone reacted to a post in a topic: 4.7.26 is now available!
  3.    Bionic Rooster reacted to a post in a topic: 5.1.0 Beta 3 is now available!
  4.    Adriano Faria reacted to a post in a topic: 5.1.0 Beta 3 is now available!
  5.    The Old Man reacted to a post in a topic: 5.0.21 is now available!
  6. If you need to apply any more updates, you'll have a large red banner appear on your community letting you know.
  7.    Marc reacted to a post in a topic: 5.1.0 Beta 3 is now available!
  8. We've released 5.1.0 Beta 4 with the security fixes from the previous patch. We've also included a few bug fixes: #7939 Fix an issue where annual recurring events showed in every month of the overview #8200 Restore theme rows when building a third-party app.
  9.    My Sharona reacted to a post in a topic: 5.0.21 is now available!
  10. Yes, we know it's an issue. Currently it appears that it's a visual bug in the theme editor and doesn't affect any functionality. We're still looking at potential solutions for a future update.
  11.    Matt reacted to a post in a topic: 4.7.26 is now available!
  12.    Bonaparte reacted to a post in a topic: 4.7.26 is now available!
  13. Right now we have two choices to make, either use our patch system and send out a notification to self-hosted customers or release an update with a new version number. Using a new version number creates extra friction because it'll prompt every customer to run an upgrade when they visit their AdminCP. Quite often this isn't needed with version 5 because we precompile templates and JS. Those not using the latest patch will see a large red banner asking them to update. Will we stop doing that in future? yes, that's part of the development plan but we have to work within the confines of what's possible today. I think you may have made my point. To be clear though, we have no plans to extend version 4. It's not fully compatible with newer PHP versions and that large change was implemented in version 5.
  14.    The Old Man reacted to a post in a topic: 5.0.21 is now available!
  15.    My Sharona reacted to a post in a topic: 5.0.21 is now available!
  16. Thanks, we're looking into it.
  17. If that's the case, why will it take you so long to update to version 5?
  18. Important Update We have released a patch for 5.1.0 Beta 3 with some important security updates. Please go to AdminCP > Support to apply the patch. Cloud customers have already been updated, no further action is required. Downloads of 5.1.0 Beta 3 have been updated with these fixes, if you do not see a patch available on the support page you already have these updates.
  19. Important Update We have released a patch for 5.0.21 with some important security updates. Please go to AdminCP > Support to apply the patch. Cloud customers have already been updated, no further action is required. Downloads of 5.0.21 have been updated with these fixes, if you do not see a patch available on the support page you already have these updates.
  20. Important Update We have released a patch for 4.7.26 with some important security updates. Please go to AdminCP > Support to apply the patch. Cloud customers have already been updated, no further action is required. Downloads of 4.7.26 have been updated with these fixes, if you do not see a patch available on the support page you already have these updates.
  21.    Stuart reacted to a post in a topic: 4.7.26 is now available!
  22. @RextonXVT From that log, I'd guess that you're using PHP 8.3 (unsupported). Switch to PHP 8.2 and then it should work.
  23. Also, if you look at /uploads/logs/ you might have some logs with the date and 'extractfailure' in the filename. These may provide more information about why the automatic upgrade failed.
  24. Not at this time, but it seems that something odd is going on. Your error message is from trying to access a front-end module that you don't have permission for. The MFA process does not redirect from the AdminCP to the front-end, you may have something else going on there (maybe a custom Loader extension redirecting the browser?). We did harden the answer verification for the security answers MFA handler.
  25. We're working on this issue, it's related to whether your member account has read data stored for the record. That's why sometimes you see the broken links and sometimes you do not.
  26. Yes, you can use the DISABLE_MFA constant to temporarily disable 2FA.
  27.    Stuart reacted to a post in a topic: 5.0.21 is now available!
  28.    Stuart reacted to a post in a topic: 5.1.0 Beta 3 is now available!
  29. It's #10238 which is the title from the Pull Request. I have updated it to make it clearer though. Unfortunately, Redis SORTs in v4 continued to cause issues so we had backport this change to ensure platform stability.

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.