Adriano Faria Posted January 18, 2022 Share Posted January 18, 2022 This was tested on localhost, fresh install with no 3rd-party resources. Although I select the option to anonymize the content, it keeps attributing it to the deleted member. Link to comment Share on other sites More sharing options...
SeNioR- Posted January 18, 2022 Share Posted January 18, 2022 (edited) I confirm the same bug for me. Edited January 18, 2022 by SeNioR- Adriano Faria 1 Link to comment Share on other sites More sharing options...
Stuart Silvester Posted January 18, 2022 Share Posted January 18, 2022 Have you allowed the background tasks to complete? Link to comment Share on other sites More sharing options...
Adriano Faria Posted January 18, 2022 Author Share Posted January 18, 2022 6 minutes ago, Stuart Silvester said: Have you allowed the background tasks to complete? It's a test install with 50 topics and 50 members. Quick thing. Link to comment Share on other sites More sharing options...
Marc Posted January 19, 2022 Share Posted January 19, 2022 Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release. SeNioR-, Real Hal9000 and Adriano Faria 2 1 Link to comment Share on other sites More sharing options...
Solution Marc Posted January 25, 2022 Solution Share Posted January 25, 2022 This issue has been resolved in 4.6.10 beta 1. Feel free to give this a try, or await the full release if you prefer SeNioR- and Adriano Faria 1 1 Link to comment Share on other sites More sharing options...
Recommended Posts