I just noticed that typing in a username only produces results if no filters are applied. As an example, if I filter on 'Online Users', there are no results returned for any of the users even if I type in one of the users displayed. Is this intentional? If so, the search input should probably be disabled when a filter is active.

Those are just warnings you can ignore those.

Can't change profile pictures when trying to update with "Upload new picture form URL". Some pictures works others don't.

You can reproduce in this same forum with this pic: "https://cf.geekdo-static.com/avatars/avatar_id169592.jpg"

No error is logged, just a blank form:

508e55c6-2cda-40ec-8f9b-a9fb54cc8214-image.png

If I use the option "Upload new picture" with the same picture than it works.

@PitaJ Yes, I am using http://localhost:4567 to access the forum. It seems I got it wrong how URL variable works. And as I am using the default port everything work it when I changed my config and mislead me to believe that was something wrong with the plugin.
Thank you!

@baris Thank you, its xaponeis1

Open it on main nodebb repo, it probably effects all soo plugins including twitter facebook etc

@Akira Could be a variety of root causes. Broadly speaking, these break down to web/reverse proxy server and app server issues, e.g. Nginx and NodeBB, respectively. If possible you should endeavor to examine the logs from each. 👍

Have fun sleuthing! 🔍 🐕

That will remove most of the user data but you should also remove 4076 from some sorted sets like users:joindate users:reputation users:postcount

Link Preview Image NodeBB/src/user/delete.js at master · NodeBB/NodeBB

Node.js based forum software built for the modern web - NodeBB/src/user/delete.js at master · NodeBB/NodeBB

favicon

GitHub (github.com)

@julian Yup, ninja style... silent and deadly!! 🤕

@lavanyadeepak thanks for letting me know. Do you mind opening an issue on our github tracker?

Link Preview Image Build software better, together

GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

favicon

GitHub (github.com)

@Andrea-0 https://community.nodebb.org/post/88482

@baris thanks a lot 🙏

@AshiVered https://github.com/NodeBB/NodeBB/issues/10283

@venkat123 You need to run ./nodebb upgrade to update the dependencies. If running that didn't change the mentions version, then something went wrong with the command, or perhaps the mentions plugin is a symlink (and thus does not get updated).

Not sure if anyone else has noticed this, but when using this site on mobile, the header often masks the top part of the screen making the first post unreadable.

Screenshot_20220206-123628.jpg

I've fixed this annoying bug (it's always been there but is now much worse with the NodeBB header that was added a while back) over at Sudonix.com by making the header fixed and allowing other sticky elements to float over the top using z-index so not an issue as such for me, but thought I'd report it here.

@ahoh said in TypeError: Cannot read properties of undefined (reading 'length'):

plugin nodebb-plugin-sso-beer-qq

remove plugin nodebb-plugin-sso-beer-qq

@baris Ugh, duh! And coincidentally all the other users I checked were in the same boat. Thanks for the clue bat.

Finally, to make a summary, I met a strange problem when building nodebb: when I write a post, the uploaded pictures can be displayed normally, but the picture links cannot be displayed.
The solution is to set "cross origin embed policy" to the state shown in the following figure:
屏幕截图 2022-01-26 153145.png
However, there is another strange problem. When you use "www.domain. Org" to access, you can display pictures normally, but when you use "domain. org", you still can't display pictures.
You can configure nginx to make "domain. org" jump to "www.domain. Org" through 301。

Welcome to my station, ahoh.club，Thank nodebb, thank Mr. cat(baris).

@crazycells thanks for reporting https://github.com/NodeBB/NodeBB/issues/10197

I suggest updating to 1.19.0 and applying this change as well https://github.com/NodeBB/NodeBB/commit/e9ee843b274b1e1f38b992650f3f74f940a20a49.

After that users might have to clear their cookies and refresh their browsers. Let us know if they still experience csrf errors after those changes.