Bug Reports

@darkpollo hi there, thanks for bringing this up. I think this only happened with two language files, user.json and admin-settings-general.json Can you check if that is the case?

It seemed to work on mine: [image: 1733994812099-8416c85f-a14c-467e-8a83-746a76cae4c4-image.png] Did you make sure you enabled Custom CSS switch? [image: 1733994866043-7e13e08d-78ba-4761-9927-4ed3df4fbde6-image.png]

i'm using NodeBB v3.10.3. Popular work well when i start to use. In the one day, i don't know why Popular don't work although i try to click to topics for update topics views. Site don't show any data when i chose: day, week, month [image: 1733200643197-5161646d-203a-441a-b031-788314c75d08-image.png] When i chose: All time, site response data but it's not true by views. this is my congfig: { "url": "https://mywebsite", "secret": "{mykey}", "database": "mongo", "mongo": { "host": "{ip}", "port": "27017", "username": "nodebbv3", "password": "mypass", "database": "nodebbv3", "uri": "" }, "port": ["4567","4568","4569"], "bind_address": "0.0.0.0", "isCluster": "true", "redis": { "host": "127.0.0.1", "port": "6379", "password": "mypass", "database": "2" }, "upload_path":"/public/uploads", "session_store": { "name": "redis", "host":"127.0.0.1", "port":"6379", "password": "mypass", "database": "1", "tls": {} } }

@nono-lqdn The error message is showing you which key is causing the violation, in this case it is analytics:pageviews:byCid:32 you need to delete that and try the createIndex command again until you no longer get errors and the index is created successfully. Do this when the forum is not running so you don't get more invalid keys. > db.objects.createIndex({ _key: 1, value: -1 }, { background: true, unique: true, sparse: true }); { "ok" : 0, "errmsg" : "E11000 duplicate key error collection: fotepo.objects index: _key_1_value_-1 dup key: { _key: \"analytics:pageviews:byCid:32\", value: \"1726783200000\" }", "code" : 11000, "codeName" : "DuplicateKey", "keyPattern" : { "_key" : 1, "value" : -1 }, "keyValue" : { "_key" : "analytics:pageviews:byCid:32", "value" : "1726783200000" } }

@elkd Running ./nodebb build is an interactive command that outputs the build state in real-time. Can you paste the log output from running that command?

@baris Works! Also just noticed you'd pushed the fix as soon this was notified. Appreciate it!

@faizanzahid Hello, I also encountered a similar problem, may I ask if the problem has been solved

@julian Then there is some big issue in my server. ekk.app is neither getting public posts nor DMs from this server. Please guide on how I can find the cause of the problem. Earlier had an issue with file uploads and thanks to guidance from @baris , I was able to solve the issue. Now, looking forward to you for help on this issue.

Then change the 999 to -1 on this line https://github.com/julianlam/nodebb-plugin-mentions/blob/master/library.js#L252

@julian https://***.org/confirm/98f65230-0d29-4175-a596-fe9d17d I've also tested the status of this feature in my community, and it's also not working.

https://github.com/NodeBB/NodeBB/commit/c4a60dbbcc75499492eb793d31e6364d60f150ee With this change, doing a search on the Find Plugins tab will show all matches, looks like all the plugins were already available in ajaxify.data.incompatible so it will search in that array too.

I think sso-facebook plugin has an option to auto confirm emails.

hi, ı do not have 2,2K users in my forum. [image: 1723609924473-9e8b5080-aa3e-45cc-a6c6-9dde72fea349-image.png] also user has 1.4K entries, it is not correct. [image: 1723610030366-aae7bc39-c796-4b14-bf04-b5c468b1ee98-image.png] those are bug or something done false my side?

@xxx and do what exactly, automatically verify accounts? That would not be ideal I think.

Hi @baris Thanks for getting back to me. Running v3.6.3. Noted. Will update soon. Thanks!

Same thing here. After initial installation with docker compose, I had to remove it, annd than just reinstall using same method. Now it works as well showing correctly in cli

@julian said in forum is not behaving normal on firefox: You likely have some cached client-side files on Firefox. Please clear the browser cache and try again. yeap, apparently this was the problem. Thanks

Yes, this is a bug in the v4 code. Will fix soon.