3.0.0 Bug Report Thread

[inspiring]

This is for default skin? or you customize it

In our forum it's white

If you have personalized it, can you teach me?

[inspiring]

@baris
Your welcome

[baris]

The color of that progress bar comes from the bg-info class, so it is set to a different color based on the skin used.

[inspiring]

@baris
When I block a user, it shows the list of blocked people on the blocked page, but clicking on each one does not go to the profile page of that user, to unblock him.
I test it in this forum and it's work, but it doesn't work in our forum

[inspiring]

Forbidden error

It gives this error and I have to clear the cache and log out to allow login

This problem does not exist when you have just logged into the forum and want to enter the management panel, but when after a few minutes (I think you are 15 minutes) I want to enter the management page from the menu, this problem occurs.

[julian]

@inspiring you'll need to provide more details, like a screenshot.

[dave1904]

Is there a way to format the date more readable for expiring pinned topics?

[baris]

@dave1904 Thanks for reporting, will be fixed in 3.1.0

[brazzerstop]

On the reset password page...

[btc]

Not strictly a bug as I assume the paths have just changed, but I used to have a couple of custom routes for the side menu which don't work in 3.0:

/user/_self_/bookmarks
/user/_self_/watched

Is there an equivalent in this version?

[julian]

@btc have you tried the special prefix /me?

[baris]

@brazzerstop Fixed here https://github.com/NodeBB/NodeBB/commit/8a1ec4d6451656a8883f54e00ffed67424d21580

[btc]

@julian Thank you.

/me/bookmarks and /me/watched works

[baris]

@btc like @julian mentioned these routes got replaced with the /me prefix, so they would be.
/me/bookmarks and /me/watched

[btc]

When trying to visit the "API Access" menu, I get the following error:

This is a bit of a disaster as now, none of our membership automations etc will work because I can't configure the API settings!

Full error from console is:

2023-05-12T06:37:30.401Z [4567/91921] - error: GET /api/admin/settings/api?_=1683873301366
TypeError: Cannot read properties of undefined (reading 'map')
    at settingsController.api (/usr/bin/nodebb/src/controllers/admin/settings.js:115:52)
    at async /usr/bin/nodebb/src/routes/helpers.js:74:5

It's saying "tokens" is undefined within the following function:

settingsController.api = async (req, res) => {
        const { tokens } = await meta.settings.get('core.api');
        const scores = await api.utils.getLastSeen(tokens.map(t => t.token));

        const [lastSeen, lastSeenISO] = tokens.reduce((memo, cur, idx) => {
                memo[0][cur.token] = scores[idx];
                memo[1][cur.token] = new Date(scores[idx]).toISOString();
                return memo;
        }, [{}, {}]);

        res.render('admin/settings/api', { lastSeen, lastSeenISO });
};

I have worked around it by changing the line to:

const { tokens = [] } = await meta.settings.get('core.api');

I don't know yet whether there will be any knock-on effects!

[baris]

@btc please open an issue on our github. Add your nodebb version as well.

[baris]

@btc released 3.1.2 with the fix, try on that version. Thanks for reporting.

[NikolaiPatrushev]

I use latest tor browser and upgraded nodebb engine to 3.1.3 recently released version.
I am experience problems with CORS, can somebody help?

I am getting error socket.io/?EIO=4&transport=polling&t= 403 Forbidden
My node server somehow refuses to authorize it socket.io request .

[brazzerstop]

@NikolaiPatrushev are you have this socket error if use this onion mirror?
https://community.nodebb.org/topic/16981/nodebb-in-tor-works/3

I don't know, but maybe solution for this sockets problem in here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins

[NikolaiPatrushev]

look what now my server saying
info: [socket.io] Restricting access to origin: i have ommited full address .onion:*
And i still receive same failure message

403 means that my server recognise the request, but for some unknow to me reason it refuse to forward further.