This is related to an issue resolved earlier.
We found that if a topic's posts contained images pointing to a relative path (e.g. ![test](1.jpg), NodeBB would attempt to load them, causing them to load the entire topic again (since the url is site.com/topic/123/1.jpg).
To combat this, @baris restricted the URL so that the slug must be correct, otherwise the user is sent to 404.
For lack of a better solution, this was the approach we took, so this seems to be the reason why you're running into this issue now.
Shouldn't this request be directed to Taptalk Inc? They seem to charge both the app user and the forum maintainer for "pro" features.
As this is an open source project, they're free to provide a NodeBB taptalk plugin and earn more money
Place a link to a moo.do outline in the original post. Presto, integration without really integrating the code. Even this half baked setup is superior to all dedicated pm solutions that I have tried. For me, efficiency is the primary factor when evaluating software. How quickly we can download the data we need and upload our input. Number of clicks is a useful metric.
Having every resource available on the home page is a highly efficient design for a workflow tool. I view nodebb as the best version of this concept.
Its easy to recommend the popular product. Actually testing all of them to isolate value is challenging. Try not to anchor yourself until you've done the research.
change api to QraphQl
gives clients the power to ask for exactly what they need and nothing more
Get many resources in a single request
maintainable server code
Apps using GraphQL can be quick even on slow mobile network connections.