2
1

Moderator => remove post doesn't seem to work

10d 9h ago by feddit.uk/u/i_am_not_a_robot in lemmyconnect@lemmy.ca

Bug Report

Describe the issue:

<!-- Please describe what happened and what you expected to happen -->

Tried removing a post using Moderator => Remove post and noting happened.

Expected a reason to be requested and then the post to be removed

Steps to reproduce:

  1. Find a post on a community that you moderate
  2. Select Moderator => Remove post
  3. Nothing happens

Device Information

  • App Version: 1.0.441 (441)

  • Platform: android

  • OS Version: W1UIS36H.39-17-4

  • Migration: n/a (attempts: 0)

Modified Settings

The following settings have been changed from defaults:

  • isSwipeEnabled: false (default: true)
  • isNotificationEnabled: 2 (default: 0)
  • isCommentBarAlwaysShowing: true (default: false)
  • shouldAlwaysOpenInDefaultBrowser: true (default: false)
  • alwaysShowInstance: true (default: false)
  • alwaysTrustDomains: true (default: false)
  • shouldUseHighRefresh: false (default: true)
  • shouldPreloadImages: wifi (default: always)
  • commentTextStyle: bodyMedium (default: bodyLarge)
  • postTitleTextStyle: titleLarge (default: titleMedium)
  • customColoursPreset: 3 (default: 0)
  • enableCommentNavigator: true (default: false)
  • isTopBarFixed: true (default: false)
  • isDraftsEnabled: false (default: true)
  • shouldAlwaysDisplayAvatars: true (default: false)
  • defaultRoute: /community?postCommonListingType=Subscribed&hint=Frontpage (default: null)
  • defaultPostSort: New (default: Active)
  • applyNsfwInCommunities: false (default: true)
  • postActions: [comment, save] (default: [comment, save, none, crosspost])
  • shouldPreloadVideos: wifi (default: always)
  • shouldCombineMarkdownImages: false (default: true)
  • shouldRemembercommentPosition: false (default: true)
  • shouldUseProfileBanner: true (default: false)
  • shouldLoadAllComments: true (default: false)
  • isOfflineSyncOwnContent: true (default: false)
  • imageDomainRewrites: {} (default: {})

Hi, thanks for the bug report. This should now be fixed in v443. Cheers!