Sly_Ripper Posted July 7, 2023 Share Posted July 7, 2023 Topics are orphaned despite passing 'deleteChildrenOrMove' when deleting a forum via the API, they should be moved. Not moved: Link to comment Share on other sites More sharing options...
Jim M Posted July 7, 2023 Share Posted July 7, 2023 Have the background tasks completely finished for the process here? Can check this in ACP -> System -> Dashboard -> Background Processes. Link to comment Share on other sites More sharing options...
Sly_Ripper Posted July 7, 2023 Author Share Posted July 7, 2023 1 hour ago, Jim M said: Have the background tasks completely finished for the process here? Can check this in ACP -> System -> Dashboard -> Background Processes. It didn't appear to even create a background task Link to comment Share on other sites More sharing options...
Jim M Posted July 7, 2023 Share Posted July 7, 2023 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- 1 Link to comment Share on other sites More sharing options...
Sly_Ripper Posted July 8, 2023 Author Share Posted July 8, 2023 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. Link to comment Share on other sites More sharing options...
Solution Jim M Posted July 8, 2023 Solution Share Posted July 8, 2023 As mentioned, this is a bug. If you delete a forum and specify to move children, it should move topics. If you outright delete a forum and specify to delete its children, it should delete them too. It should not just orphan the topics. SeNioR- 1 Link to comment Share on other sites More sharing options...
Marc Stridgen Posted September 6, 2023 Share Posted September 6, 2023 This issue was resolved in the recently released 4.7.13 release. Please update in order to fix this issue, and if you see any problem after that point, please let us know. Link to comment Share on other sites More sharing options...
Recommended Posts