Posts made by baris

I think /top is what you want. So /api/top?cid=5&term=daily

const topicId = 5;
const keys = db.objects.find({ _key: "tid:" + topicId + ":posts" }).map(i => 'post:' + i.value);
printjson(db.objects.find({ _key: { $in: keys } }).toArray());

You can save this in a file called query.js and then execute it with mongo localhost:27017/mydb query.js

It will output something like

[
        {
                "_id" : ObjectId("5547ae6a65190fe21225ec2b"),
                "_key" : "post:124",
                "pid" : 124,
                "uid" : 47,
                "tid" : 5,
                "content" : "I like it too :)",
                "timestamp" : 1376791225638,
                "bookmarks" : 2
        },
        {
                "_id" : ObjectId("5547aee765190fe212296f10"),
                "_key" : "post:18",
                "pid" : 18,
                "uid" : 2,
                "tid" : 5,
                "content" : "Thank you :)",
                "timestamp" : 1373686442781
        }
]

https://github.com/NodeBB/NodeBB/issues/8120

yossizahn created this issue in NodeBB/NodeBB

closed Throwing an error in a static hook doesn't propagate to caller #8120

Hmm, looks like static hooks are not sending the error back which seems to be the problem. Can you open an issue on our github tracker.

@vf144 thanks for looking into this. This commit should fix the issue.

Did you restart nodebb after changing the setting?

/admin/settings/uploads has a setting for stripping exif data, try turning it off.

Yes. As always make a backup of your database with mongodump before upgrading.

@Brophy said in Issue since upgrading to v1.13.1 from v1.12.1:

Secret Service Civilian Support

Try creating this group in the mongodb cli. To see what fields you need you can load one of the other groups with

db.objects.findOne({_key: "group:raceTECH"});

Couple things to try.

Stop nodebb and run ./nodebb build and try again.

Also run ./nodebb plugins to check active plugins and see if persona is active.

Not right now since it's part of the moderation privilege.

Are those all the groups you have? You can compare that list to the ones you see on the /groups page and find the missing one. Then it is a matter of recreating that groups object.

Take a look at logs/output.log for any error messages.

db.objects.find({_key: "groups:visible:createtime"}) This command should more than one group. Did you run it with findOne?

They are mongodb commands so you need to run them in the mongodb cli.

Seems like the groupName is empty string. Do you get any results when you run this db.objects.findOne({_key: "group:"});

Also what is the output of db.objects.find({_key: "groups:visible:createtime"});

It is safe to delete the ip:recent and analytics keys, you will just lose the historical data on the dashboard.

Your calculations probably doesn't include the index data size. You can check /admin/advanced/database to see those sizes.

@Brophy When you right click in the browser and inspect the empty row do you see a group name?

@Brophy said in Issue since upgrading to v1.13.1 from v1.12.1:

Someone tried to update their group yesterday and managed to break it,

This sounds like a serious issue, let us know if you can reproduce this.

Looks like there is a group with invalid/missing data. Maybe you can inspect the groups page to see the name of the missing group on the first row.

In the meantime this commit should prevent the crash you are getting on the widgets page.