@baris Indeed, I was logged with admin account. I tried with a regular user and it works correctly. The "Upload Image" button does not show and uploading with CTRL+V gives me the following error:
Thanks for clarifying and sorry for the misunderstanding.
Hey everyone,
Yes, it's a crazy upgrade, but I need it! 
I will try to be as brief as possible.
Collections in my MongoDB (2.4.8): objects, posts, search, searchpost, searchtopic, sessions
schemaDate value: 1412640000000.000000
Mongodump'ed and Mongorestore'd to another MongoDB database in MongoLab (2.6.9, therefore, textSearchEnabled=true by default).
Collections in my MongoDB (2.6.9): same as above
schemaDate value: 1392925500000.000000 - I think it's different because of some many failed attempts to ./nodebb upgrade
What I did after that:
C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\lib\utils.js:97
process.nextTick(function() { throw err; });
^
TypeError: Cannot read property 'length' of undefined
at Object.async.eachSeries (C:\Users\Rafael\Desktop\openshift\NodeBB\node_modules\async\lib\async.js:141:17)
at C:\Users\X\Desktop\openshift\NodeBB\src\upgrade.js:903:13
at C:\Users\X\Desktop\openshift\NodeBB\src\database\mongo\main.js:103:4
at handleCallback (C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\lib\utils.js:95:12)
at C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\lib\collection.js:763:5
at C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\node_modules\mongodb-core\lib\topologies\replset.js:371:5
at C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\node_modules\mongodb-core\lib\topologies\server.js:795:13
at Callbacks.emit (C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\node_modules\mongodb-core\lib\topologies\server.js:94:3)
at null.messageHandler (C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\node_modules\mongodb-core\lib\topologies\server.js:235:23)
at Socket.<anonymous> (C:\Users\X\Desktop\openshift\NodeBB\node_modules\mongodb\node_modules\mongodb-core\lib\connection\connection.js:259:22)
-- Ignored error. Checked schemaDate: 1424736000000.000000, therefore, it got updated.
-- Tried running NodeBB and I was told to ./nodebb upgrade. Did it, received message: Schema update complete!
-- Tried running again, node app.js - Success - Checked schemaDate: 1431302400000.000000
-- Opened the forum and noticed my HTML Widget at the top was missing. Logged with old admin account - had Admin rights normally. Opened ACP and changed theme to Persona - Worked just fine
-- Investigated Widget issue. ACP > Extend > Widgets and no widgets were found, however, I'm stuck with a light-blue empty div on the top of my NodeBB forum.
The funny thing is that I wrote this post while testing everything on my side and expected it to fail because yesterday I tried the same steps and the outcome was quite different: I didn't even manage to run 0.7.0-dev. So yeah, I guess I could just erase all my post and just leave the "light-blue div issue", but I think my use case might be useful for someone. If not, feel free to edit my post.
Anyways, that's basically the entire process that I went through. I will keep investigating the light-blue widget and post here if I managed to remove it. Other than that, all I can say is that you guys did an amazing job with NodeBB and... Persona theme is cute 
(one of the reasons why I updated everything lol)
Regards!
Hey everyone,
My question is very specific: is it possible to hide sensitive data when composing/editing a post? I have a NodeBB forum where people may post some private information, but the content of the post itself is relevant to other users, so I don't want to hide it completely: only certain information, which will be shown only for administrators.
Example: to integrate some SDK, a user requires an ID, but this user is having issues with the integration. Then he creates a post with his logs, asks for help and those logs contain his ID and other stuff. While the user can hide his own ID, I want that ID to not be shown at all for regular users/guests, but show normally for administrators, since we can track his bug easier with his ID. That's more or less the use case.
Do you guys know if there's a plugin or markdown command that does this?
Regards!
Awesome! It worked for me and indeed, there's no delay. Also, to hide the views in the post bar, I used this one:
.topic-main-buttons .stats:nth-child(3) * {
/* to maintain formatting */
visibility: hidden;
/* to hide completely instead */
/*display: none;*/
}
Thanks a lot!
Apparently it looks at the users:online key instead of the lastonline field of each uniqueuser.
It seems there is some discrepancy between the two which is causing these wrong results. Maybe my server was having issues...
I'm using NodeBB 1.11.1 on AWS. When I check for users that have been inactive for longer than 5 months, I get some results that do not fit my query, i.e., the user actually was online recently. Is this a bug?
I'm using NodeBB 1.11.1 and I would like to delete all users that have been inactive for longer than 1 year:
The feature above works fine, but it only shows 50 results per page. I've got about 10 pages so I need to click the top-left checkbox for each page and then click "Delete user(s) and content".
Is there a faster way to do this? Simply showing more results would be handy.
With the viewcount, I found the topic in my database:
{
"_id" : ObjectId("5b0e1c4390dcefcd0d0bd012"),
"_key" : "topic:107",
"viewcount" : 810
}
Then I deleted the document and it also disappeared from my category.
Yeah, no luck. The topic is still there.
One of my categories has the following topic:
When I try to delete it, I receive the following error:
In the HTML, the topic is shown with ID 0:
It feels like some user was about to post something and then the server restarted/crashed or whatever.
How do I delete this topic? I've searched for a _key: "topic:0", but there aren't any documents.
At least 10 seconds to restart NodeBB and more 10 seconds for my plugin to load some stuff from my database and do other startups. In the case below, I simply added a space in my subscribe2.tpl and saved it.
>> File "node_modules\nodebb-plugin-myplugin\templates\subscribe2.tpl" changed.
started
2018-11-04T07:57:31.402Z [19060] - info: [themes] Using theme nodebb-theme-persona
2018-11-04T07:57:32.324Z [19060] - info: [build] Building in parallel mode
2018-11-04T07:57:32.326Z [19060] - info: [build] templates build started
2018-11-04T07:57:33.295Z [19060] - info: [build] templates build completed in 0.969sec
2018-11-04T07:57:33.296Z [19060] - info: [build] Asset compilation successful. Completed in 0.97sec.
2018-11-04T07:57:34.021Z [6952] - info: Initializing NodeBB v1.10.1 http://127.0.0.1:8081
2018-11-04T07:57:37.405Z [6952] - warn: [upgrade/appendPluginScripts] Unable to read plugin.json for plugin `nodebb-plugin-emoji-extended`. Skipping.
2018-11-04T07:57:39.417Z [6952] - info: [themes] Using theme nodebb-theme-persona
2018-11-04T07:57:39.920Z [6952] - info: [plugins] Plugins OK
2018-11-04T07:57:41.873Z [6952] - info: Routes added
2018-11-04T07:57:42.053Z [6952] - info: NodeBB Ready
2018-11-04T07:57:42.058Z [6952] - info: Enabling 'trust proxy'
2018-11-04T07:57:42.061Z [6952] - info: NodeBB is now listening on: 127.0.0.1:8081
When I said "shutdown my server" and "starting it again" I meant locally, not production. So I'm not really worried about the impact to my users, but the development speed instead.
Sadly, this is still very slow. Thanks for the help though.