Skip to content

Conversation

@ihorsokhanexoft
Copy link
Contributor

@ihorsokhanexoft ihorsokhanexoft commented Nov 19, 2025

Purpose

Admin encounters cases when spam data is not set for the objects that have SPAM status

Changes

When user is being checked for spam, it doesn't set spam data of the user to this related resources
Some objects become FLAGGED instead of SPAM when spam is found by akismet and oopspam
Also fixed losing FLAGGED status of user after account deactivation
It happens when:

  1. Spammy domains are found in user record and they aren't added to user's nodes and preprints
  2. Spam is found by akismet or oops. In this case spam data is not set for related objects at all

Ticket

https://openscience.atlassian.net/browse/ENG-9730?atlOrigin=eyJpIjoiYTI3ZWU1MDRhZjc1NDVhOGIyNjljNjYyY2Q3OGZjOGIiLCJwIjoiaiJ9

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant