General Discussion

Hmm I don't think we expose isAdmin and isModerator globally to the templates so that you can them everywhere. Maybe we should, everything in the config object is exposed so if you open your console and type config any variable you see under that object you can use in the templates. You can also take a look at the routes by prepending api to the url like https://community.nodebb.org/api/topic/1917/users-shouldn-t-be-able-to-purge-their-posts/10 you can use stuff from there in the template as well.

@julian oh tnx

First of all we already have topic thumbnails you can enable it from the ACP. [image: SjSQYR4.png] If that isn't enough you can take a look at the code that makes it work and duplicate that.

@avi Hard to say, they could be doing it through cookies, if you upvote a deal, the upvote of that deal is saved into your cookies, then if you try again in the same browser, it knows you've done it already, however this is also circumventable by changing browsers and deleting your browser cookies. You can make it hard for someone to fake votes, but you can't stop it. I think a mixture of email confirmation, cookie usage, limiting who can upvote and downvote (need to post a deal in order to vote for other deals, or something like that) and keeping an eye on activity would deter enough people not to bother trying to fake the votes. You'd have to post the deal, log out, clear your entire browser cache, cookies, history etc, create an email account, sign up, verify your account, upvote, then do the whole thing again, the time taken isn't worth it, it would be easier to hire a team of people in the east to do it for you (similar to likes on facebook or views on youtube), and you can't stop them unless you place blanket IP bans on subnet ranges. Which, if you're only concentrating on one place, then that would be fine.

@julian "windows 4 lyf" Waiting for my Pi b+ to arrive! then I'll load ubuntu on that and use it as my development board, keep the normal b model pi for XBMC. Not sure how easy it is to cluster the raspberry pi. However for something that's made in the UK, it takes long enough to post to me...

@a_5mith said: @psychobunny .username { font-size: 80%; } Well that works for me ... updated

@julian pfff vestacp support is soooo bad.. instead i will create a snapshot of my droplet and then try to install the wstunnel module, if anything breaks i can revert back i will message back if it works or not

@velderia said: So... As far as npm install I'm having issues pretty much the same here: https://community.nodebb.org/topic/540/-nodebb-theme-lavender-lavender-theme-for-nodebb/73 (at the bottom) but I'm not sure how to reinstall npm on the stack or if that would even help. I guess I should be developing Node.js on linux but so far I've been dual booting and I'm thinking about investing in like a Gigabyte Brix and having two monitors side by side (or even a KVM switch). I use Windows for graphics and I like Ubuntu for developing stuff and it's kind of my dream setup to begin with. Edit: After rolling around in bed and drinking some coffee, I manually inserted the lavender theme in the node_modules folder, removed it from the npm-shrinkwrap.json file (created a npm-shrinkwrap-backup don't worry), and tried npm install again. It seemed to work up until "[email protected]" saying "no repository field" as a warning. I had to ctrl-C because it was literally stuck there. Now I have a bunch of nice modules installed in the node_modules folder but I'm assuming not all of them to be able to get NodeBB up and running. Tl;Dr: npm is really not liking .tgz I think Edit 2: I screwed up the entire NodeBB installation by typing node app too early and rushing everything. I'm going to take a break and probably upgrade the Ubuntu partition I have and do everything on there. Hmm... What's the problem you're having exactly. I've been running nodebb on a windows bitnami mean stack for a long time without any issues whatsoever. Just make sure you pick the latest BITNAMI version (sometimes they hide them in favour of older more stable releases), install git and you're off to the races

@luke Pre v30 (or maybe v29) you could move the refresh button anywhere on the toolbar, it's now fixed at the right of the Location bar. Can't be moved without addons.

@julian I think English is the parent repo, then translations are considered children of that one, as docs.nodebb automatically routes to /en/. That's what the documentation of your doc software says anyway.

@julian said: Need more info. I can't work with "not working", sorry Look at the code above, this is what I get on the browser. I have run the ./nodebb dev but I don't get any information in the console, so kind of this is all I have.

@zenkamal I have no idea, the last 3 events were editing posts, I had app running in dev mode for an hour, no issues, I then started it normally and left terminal open on the logs while I went out, came back, no issues. I'll keep an eye on it, but since enabling swap, hopefully I won't have any more issues.

Cards should be fine.

part of the answer you can find here: https://community.nodebb.org/topic/2032/changing-e-mail-notification-content/4

I was interested by LevelDB because I searched on google and on the project page, the author said that LevelDB is fast and lightweight.

Actually it was an update pushed in the last couple of hours which have solved the issue. At least on one of the plugins which I have tested. I hope it will be the same way on all the plugins. Thanks for your help.

I have tried to browse the plugins in the hope that I would get some more information but I did not got one single line. There still have to be a way to put this in full debug mode.

@Peter-Zoltan-Keresztes That circle next to login / register means that connection to nodebb has been lost, sometimes because of a restart, sometimes because of a crash, either ./nodebb logs or running nodebb in developer mode.

@psychobunny yep.. i did the git pull / upgrade stuff before leaving the office... and before creating this thread : /

@a_5mith if you are quoting from a different topic it puts in a link to that topic but it was using the old format which is fixed now. https://github.com/NodeBB/NodeBB/issues/1840