You could just leave the older versions compatible with the older versions of NodeBB. Like currentlyat BitBangers, we have the old 0.0.6 version running as that was the only one i could get working correctly with the 0.3.2 version of NodeBB.
If you use an older version of nodebb then you will have to use an old version of the plugin.
@baris
That does appear to resolve the issue. One issue it brings up, though, is that I have customizations to the lavender theme and the version I've been using appears incompatible with Edge.
Is there any way to identify which versions of the lavender theme are compatible with which versions of NodeBB?
@baris
Are you guys going to address who can delete, move a topic. Giving every registered user the right or privilege of deleting/moving topics could be very bad for some very active forums, don't you think.
Reserving that privilege (of deleting/moving a topic) I think should be reserved for the admin or somebody in the admin group. Just my $0.02.
That looks good to me. Although I am not sure if it would have any side effects to other routes without testing can't tell for sure. I only see one db call in there for themes. I am not sure if there could be a case where webserver.js is required from app.js and then webserver.init is called before all the setup is done in webserver.js.
Hey @medwards -- Indeed, that's what we're hoping to do with search. Not everyone wants to use Reds, so I'm actually planning on divorcing Reds from core, and allowing third-party plugins to interface with the routes.
@eva2000 this exporter hits the VB databases, gets all the relevant data, then writes them all on the file system in some storage directory in a structure that this nodebb-plugin-import can understand then import to the NodeBB database. .. basically a two step import technique.
M
