@noob111 the main benefit of React is not really performance. The benefit of React and other frameworks is that it separates your UI into individual composable components and allowed you to easily define them in a declarative fashion. Those features of that kind of framework allow for much easier development.
No sorry, that didn't solve. But following worked:
After importing mybb, upgrade it to v1.16.0 which produces "Error: ENOENT: no such file or directory, open '/nodebb/node_modules/nodebb-plugin-require/plugin.json' " as mentioned above.
Back up both database and any image files imported from mybb under public/uploads/files
Delete whole nodebb files and database
Install original v1.16.0 (git clone -b v1.16.x https://github.com/NodeBB/NodeBB.git)
Remove only the database, then restore database and image files using backups
Works well, it doesn't produce any error even after installing quickstart plugin.
Additionally, https://github.com/NodeBB/nodebb-plugin-quickstart doesn't work on v1.16.0.
It shows following error on Chrome and the page got frozen while loading:
colorpicker.js:11 Uncaught TypeError: n.ColorPicker is not a function
at HTMLInputElement.<anonymous> (colorpicker.js:11)
at Function.each (jquery.js:381)
at C.fn.init.each (jquery.js:203)
at Object.n.enable (colorpicker.js:8)
at o (admin.js:31)
at Object.i.init (admin.js:9)
at Object.execCb (require.js:1696)
at n.check (require.js:883)
at n.<anonymous> (require.js:1139)
Anyways, it's not to be discussed here I guess.
Thank you very much!
there was a problem with old plugins.
For the future I wold suggest to list all active used plugins.
Then disabling all of them and the update the forum.
If eveything is ok, update the plugins step by step to see if something goes wrong.
Thanks for yopur help. 👍
In the future I have to read the error messages more carefully.
The "bad" plugins were mentioned there 😉
Ok, the problem was solved. But I'm not sure how exactly.
After I wrote this post I noticed that the latest version of NodeBB is 1.16.x. But while upgrading the forum i switched to 1.15.x branch (I thought that was the latest).
After that, I used ./nodebb upgrade command. Maybe this was the issue? Maybe, I switched to the previous version branch, but installed the latest version of files with the "upgrade" command? — I don't really know. But when I switched to 1.16.x and upgraded the forum again, then it worked as expected. The forum now works fine.
@rob any way you can use a heroku instance with an older version of Node / npm?
Wanted to post earlier but had to wait for the post to be accepted, but you are correct. In case anyone else has the issue, this was it:
In package.json the 'engine' line for node was =>10 so Heroku was choosing Node 15. Manually changed that value to the same as what works for me locally 12.14.1 - all works well. Now having fun setting up nodebb-plugin-session-sharing - cheers!!
@patrick-anderson It should be on the network tab of your browsers console. Try uploading something while the network tab is open and it should show you the failing request. Then you can check what the server has returned in the same window.