I just did an install of NodeBB 0.8.2 and it installed nodebb-plugin-emailer-mandrill 0.3.1 with it which is only compatible with NodeBB 0.9.^. In addition to the declared version problem I was also getting a socket.io/helpers related error on NodeBB startup until I removed the mandrill plugin.
I worked around this problem by removing mandrill and then installing it like this:
I'm newbie to the Nodebb and currently I'm trying to play around with creating a new theme.
I've downloaded the repo from Quickstart theme.
I've added the nodebb-them-quickstart folder to the node_modules folder.
When I go to the admin page and load all the available themes, my new theme is listed under the installed themes.
After selecting it, it says that I should restart NodeBB to fully activate the selected theme.
After I do that and after I refresh admin page, I'm in situation where previously active them is still the active one.
In other words new custom theme is not activated.
This is the case with every theme I made.
But when I switch to the nodebb-theme-lavander, everything goes fine.
I'm really struggling to make this happen with my own custom theme.
I would be very thankful if some would tell me what is going on.
git rev-parse HEAD returns aa116e6b4d2f42731729db01f28875494988a684
I've looked through the Chrome dev console in the network section and it seems that ajaxify is receiving 304: Not modified responses, and gets stuck on opacity:0. A very weird functionality. All of the elements are loaded in, but they are all invisible. Very odd.
There is an Uncaught Error: Mismatched anonymous define() module error that occurs on page load in ajaxify.
Okay, I guess never mind. One of the external sources I was including was causing the problem. I removed the define call and now it's working.