Jump to content

Sly_Ripper

Clients
  • Posts

    177
  • Joined

  • Last visited

Recent Profile Visitors

4,653 profile views

Sly_Ripper's Achievements

  1. Using OAuth while you’re already authenticated with the forum. If 2FA is enabled, after inputting user/pass you’re just redirected to the forum index instead of triggering 2FA/redirecting to the redirect URL set in the oauth app. Disabling 2FA or logging out of the forum first both work fine.
  2. Steps to reproduce Enable/set up 2FA Log into forum Attempt to log into external app with the forum's OAuth (/oauth/authorize/?client_id=client_id_here&response_type=code&scope=scopes&prompt=login) Upon logging in you will be redirected to the forum homepage, not the correct redirect url Disabling 2FA fixes this, as does logging out of the forum first
  3. When "show on member's profile" is set to "Do not show", it will also not show on content submissions when that's set to show. The content submission setting should either apply or be disabled Edit: actually, when content submissions was set to "show to all" it was being treated as "show to staff and profile owner"
  4. Yeah this needs fixing, or at least display a message to clear the cache
  5. Allow IN_DEV with designer's mode, huge pain in the ass
  6. From what I can tell, this seems to be by design? Even deleting a forum in the admin panel has the same effect. Topics aren't considered children of a Forum, but a content item. Although there's a confirmation on deleting in the admin panel, there's no indication that all the topics will be left in limbo.
  7. It didn't appear to even create a background task
  8. Topics are orphaned despite passing 'deleteChildrenOrMove' when deleting a forum via the API, they should be moved. Not moved:
  9. [2023-07-04T16:42:25,544][INFO ][o.o.c.m.MetadataDeleteIndexService] [e14911be311d] [content/YyPDIyO8TqCQgJPetdn7UA] deleting index [2023-07-04T16:42:25,582][INFO ][o.o.a.u.d.DestinationMigrationCoordinator] [e14911be311d] Detected cluster change event for destination migration [2023-07-04T16:42:25,583][ERROR][o.o.i.i.ManagedIndexCoordinator] [e14911be311d] get managed-index failed: [.opendistro-ism-config] IndexNotFoundException[no such index [.opendistro-ism-config]] Definitely broken, tried opensearch 2.0.1 and 2.1.0. When rebuilding, the index is deleted and not re-created. Tried elasticsearch 7.17.10 and it works fine.
  10. It's a localhost dev install, the URLs are being generated like this:
  11. I considered attaching the sub-forums to clubs but forums that are part of a club are still loaded on index/forum views. An Invision install with clubs enabled are possibly prone to this slowdown, I don't know if the club rows are evaluated or not.
  12. Basically, we create a sub-forum for every PlayStation game so topics stay organised. Similar to how every game on Steam has it's own sub-forum: https://steamcommunity.com/discussions/#games
  13. Continuing from this topic: The board index (and I assume any forum listing) grabs every row from forums_forums, this could be 20k sub-forums. The board index should only grab nodes/categories with a parent ID of -1 and then any forums with those results as a parent, and sub-forums of that parent. The only reason I can think of that it's not done this way is to provide the correct "last post" info for the user's permissions. It would be nice to have an option to just limit the "last post" depth to 1 sub-forum deep and have a more performant forum.
×
×
  • Create New...