Community

Seeing the same issue on my new 0.5.3 install as well.

@julian Gotcha. If I may offer some criticism, it would be ideal to have even a basic on/off toggle for email blasting features when they ship. Many users don't want to receive daily-ish emails.

Yup, we run our NodeBB forum out of EC2. The trickiest setup was Redis, but here are a couple links which helped:

I'm interested in investigating Redis on ElastiCache, but haven't had the time yet.

Other than that, you'll need to install Node.js, of course. It's pretty straight forward (git clone the repo and build/install), but I think you may need to add some directories to PATH or other small setup tweaks. There are a probably a bunch of guides if you Google around.

Is there a way to completely disable email digests in the meantime?

Just updated to the latest 0.4.x and the loading is much faster, thanks for the heads up!

I updated to the latest v0.4.x code today (which includes the fixes mentioned by @psychobunny) and all seems to be well! Thanks for the help

Post install I had to nuke the public/templates directory to fix other issues. The JavaScript seems to be up-to-date:

I'll try your patched version of themes.js and check the versions of vanilla and lavender.

Thanks!

EDIT: Here are the versions of Vanilla and Lavender that I've got installed:

[email protected] /home/ec2-user/nodebb
├── nod[email protected] 
└── [email protected]

I've just upgraded from 0.3.2 to 0.4.x (which was a little rough, but posts on this forum helped!). However, I can't save any widget changes using the Lavender theme. When I hit "Save" nothing happens. No JavaScript errors, no errors server-side. Any ideas?

I skipped the category upgrade, the "user topic and post upgrade to sorted set" section, and now the v0.3.x upgrade completes without errors. The forum loads and so far I haven't seen any crashes while browsing around. Looks like we might be in good shape. I'm guessing that my original database botching left some of the 0.3.x upgrades intact even though I was running on 0.2.1.

As always, thanks for the help!

Thanks for the help here, @baris.

So, categories:cid is a list and the db.getListRange command seems to run correctly. The error occurs in the upgradeCategory function while attempting to run db.getSetMembers('cid:' + cid + ':active_users'.

Running TYPE cid:10:active_users returns "zset".

I've tried upgrading to v0.3.x and I get the following error while running the upgrade script:

info: Beginning database schema update
error: [upgrade] Errors were encountered while updating the NodeBB schema: Error: WRONGTYPE Operation against a key holding the wrong kind of value

I'm testing these upgrades on a copy of the database running locally.

Quick background: I had some issues upgrading my NodeBB install a month or so a ago.

I'm currently running 2.1 but trying to upgrade to the latest 2.x (and following the upgrade procedures this time!). However, I seem to be running into an issue where the types of certain keys within redis are incorrect. For example, the latest 2.x code expects the key "tid:22:posts" to be a list, but it's a zset in my database.

There aren't any errors during the database upgrade, but the server crashes trying to fetch the zset data using lrange. It's not limited just to the tid:* keys, it seems there are several keys that are zsets when they should be lists.

I'm looking for suggestions on how to fix these data types while retaining the current data. A quick google for converting zsets to lists didn't turn up much of anything. I'm pretty new to redis in general, but I'm able to inspect and modify the data via command line or redis-commander. Any help is appreciated!