Can't move posts to new topics

Product Support

AI-generated summary

The discussion revolves around an issue where users cannot move posts to new topics. Helga_Razinkova reports the problem, showing an error in the ‘Move to’ modal. NateDhaliwal asks for console or log errors, which Helga_Razinkova provides, including a screenshot of a deprecated code path error. dax explains that the issue was a transient error resolved during a site redeployment and confirms the functionality works now. Helga_Razinkova thanks dax for the resolution.

1

Hi everyone,

Is anyone experiencing the same issue? It seems I cannot create a new topic from a post:

A "Move to" modal is open in Droplr, showing an error message and options to move a post to a new topic or existing topic, with a new topic instructions, category selection, and tag options listed. (Captioned by AI)
A "Move to" modal is open in Droplr, showing an error message and options to move a post to a new topic or existing topic, with a new topic instructions, category selection, and tag options listed. (Captioned by AI)669×620 26.3 KB

2

Any errors in the console or /logs?

3

Well, yes:

The image shows a computer screen with an open Discord chat window displaying an error message related to a move operation, overlaid with a mention of deprecated code paths in the developer console. (Captioned by AI)
The image shows a computer screen with an open Discord chat window displaying an error message related to a move operation, overlaid with a mention of deprecated code paths in the developer console. (Captioned by AI)1729×724 105 KB

5

It appears to have been a transient error that was resolved when the site was re-deployed. Today it is no longer applicable or replicable. As a test I restored the deleted post and moved it by creating a new topic and the creation was successful. Note that however I deleted both the new topic and the small action on the original topic since you had already taken care to create a new one

image
image1428×335 18.8 KB

6

Thank you for looking into this, @dax!