3.0.0 Bug Report Thread

[eeeee]

I am getting these error in console log, could this be related?

[deprecated] Accessing bootbox globally is deprecated.
Use require(["bootbox"], function (bootbox) { ... }) instead
error loading admin/settings/reputation
Error: Cannot find module './settings/reputation'

[baris]

@eeeee seems like a bug please open an issue on our github

[eeeee]

@baris ok, what is the settings/reputation module its looking for. Should there be one?

[baris]

@eeeee that error message is fine to ignore, when a page is loaded it automatically tries to load a javascript module based on the template name, not all pages need that so it shows a 404 message.

[julian]

@brazzerstop cannot reproduce, please submit client-side error logging in linked issue.

https://github.com/NodeBB/nodebb-plugin-2factor/issues/85

[brazzerstop]

UPD

@julian I tested it now and this is not bug. I was can't generate backup codes because I don't enabled 2FA. Now I enabled 2FA and can generate backup codes... Sorry for the stupid

UPD

I can't disable 2FA, I get this in console when click Confirm.

[omega]

Are we suppose to see ALL the unread notifications while having to scroll and find the couple of unread ones?

Perhaps a "filter" button to bump or only display "unread" notifications is required?

[baris]

@brazzerstop Fixed in [email protected]

[brazzerstop]

I get a strange result in filtration of categories on sticky tools.
To reproduce this we need enable page pagination.

We set NodeBB Plugins (for example) - everything is OK.
https://community.nodebb.org/recent?cid[]=7

Go to next page (page 9 for example)
https://community.nodebb.org/recent?cid[]=7&page=9

Now we want to change filter of categories and view topics from NodeBB Blog

and we get incorrect result, because category NodeBB Blog don't have 9 page: https://community.nodebb.org/recent?page=9&cid[]=13

When we change a category, the filter not reset a page number.

[baris]

@brazzerstop Thanks for reporting, fixed in https://github.com/NodeBB/NodeBB/commit/304f9b6eeff38c2b4ca9ebe1edf5bf38484334e3

[eeeee]

Ive mentioned this before, but Im sure there is some kind of email verification bug. It happened with my nodebb instance, but also with my pals instance which is nodebb hosted (so he doesnt control the outbox).
Registration has email set to optional (to get round the issue), but even still no veri email arrives even though email addresses were entered at signup.
Looking at users in admin panel it says (no email) for everyone except the admin

[baris]

@eeeee https://community.nodebb.org/post/93723 this is coming in 3.2.0 to show who didn't enter email and who has pending verifications.

[eeeee]

Ok, hopefully that will fix it. Currently its not storing emails when entered at signup

[BrotherGlaucon]

@BrotherGlaucon said in 3.0.0 Bug Report Thread:

Screen goes entirely black:

Reply -> Zen Mode -> Hide

(Type Esc to exit the black screen)

I reproduced this in Chrome, Firefox, and Brave. I am using v3.1.4, but it is also reproducible on this forum.

There is a another active bug in Zen Mode: only the bottom half of the Reply button is clickable.

[eeeee]

Just to mention again an Admin panel bug.
On mobile there are some things that dont work on Admin panel
For example drag the HTML element into a Widget Header box.
If you put a mobile into desktop view, then the Admin sidebar disapears.
People might argue that for these tasks should use a desktop device, but some tablets run as 'mobile devices' and sometimes you want to make updates on the move

[BrotherGlaucon]

Lavender home page doesn't work with "Treat this category as a section."

(v3.1.6)

[baris]

Sections work a bit differently on lavender, they don't render their children, so you need to put them right before the categories and they act like a header to those categories.

[BrotherGlaucon]

Gotcha, thank you, @baris.

[brazzerstop]

I get blank page with error Internal Server Error after sync my theme fork with Harmony and have this error in logs:

TypeError: meta.css.getSkinSwitcherOptions is not a function
    at Object.library.filterMiddlewareRenderHeader [as method] (/var/www/nodebb/node_modules/nodebb-theme-community/library.js:200:63)
    at fireMethod (/var/www/nodebb/src/plugins/hooks.js:164:25)
    at Object.fireFilterHook [as filter] (/var/www/nodebb/src/plugins/hooks.js:195:18)
    at Hooks.fire (/var/www/nodebb/src/plugins/hooks.js:132:49)
    at Object.wrapperCallback [as fire] (/var/www/nodebb/src/promisify.js:46:11)
    at renderHeader (/var/www/nodebb/src/middleware/render.js:311:42)
    at renderHeaderFooter (/var/www/nodebb/src/middleware/render.js:370:17)
    at renderMethod (/var/www/nodebb/src/middleware/render.js:89:14)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ServerResponse.renderOverride [as render] (/var/www/nodebb/src/middleware/render.js:111:5)

History - https://github.com/ferumdev/nodebb-theme-community/commit/365e7dfe4190a5365df0dfca4f20e61d486482eb

NodeBB 3.1.6

When I switch to default theme Harmony, I don't have this errors. How I can fix it?

[phenomlab]

@brazzerstop you may need to copy that function from Harmony and include that in your forked theme. I had a similar issue that despite the function already being declared, I couldn't call it without adding it in the custom theme.

Never got to the bottom of it as I abandoned the custom theme anyway.