3.0.0 Bug Report Thread
-
-
Guys, what do you think about change color for the read/unread topics?
I think accent primary color should be associated with actions, not labels.Default dark color for the unread topics:
.skin-noskin ul.topics-list li.unread .title { color: #282c30; }
and grey for the read topics, like this
color: #989b9e;
vs
-
There are some small but annoying bugs, Im trying to counter each with CSS fixes, and work arounds.
I dont know if small things Nodebb devs want to hear about?
An example is in Admin, a floating title is printed in White text. Its unnecessary, (because there are other headers on page) and its mostly invisible anyway. The issue is you start to see outline of it when you may be typing something!
For example on widgets page, this text looks corrupted, but its just 'widgets' is a floating white text header. It starts to show when there is text behind it.
-
Please change z-index for mobile navigator when Composer is open
-
Create Token
button on pageadmin/settings/api
not work when click. NodeBB (develop) -
@brazzerstop fixed in https://github.com/NodeBB/NodeBB/issues/11773, thanks for reporting.
-
Categories pagination toolbar is very tiny for my fingers on mobile. I keep pressing wrong box.
-
Upgrade from 3.1.4 > 3.2.0 is stalling on this, initially it was a custom theme, which I removed, but now this, this is outside my pay grade
Dependencies outdated or not yet installed. Installing them now... npm WARN ERESOLVE overriding peer dependency npm WARN While resolving: [email protected] npm WARN Found: [email protected] npm WARN node_modules/nodebb-plugin-emoji npm WARN nodebb-plugin-emoji@"4.0.6" from the root project npm WARN 2 more (nodebb-plugin-emoji-android, nodebb-plugin-emoji-apple) npm WARN npm WARN Could not resolve dependency: npm WARN peer nodebb-plugin-emoji@"^5.0.0" from [email protected] npm WARN node_modules/nodebb-plugin-emoji-apple npm WARN nodebb-plugin-emoji-apple@"^4.0.0" from the root project npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /home/dir/nodebb/node_modules/nodebb-plugin-spam-be-gone npm ERR! dest /home/dir/nodebb/node_modules/.nodebb-plugin-spam-be-gone-9pOCzryn npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/home/dir/nodebb/node_modules/nodebb-plugin-spam-be-gone' -> '/home/dir/nodebb/node_modules/.nodebb-plugin-spam-be-gone-9pOCzryn' npm ERR! A complete log of this run can be found in: /home/dir/.npm/_logs/2023-07-000000.log Error installing dependencies! message: Command failed: npm install --omit=dev stdout: null stderr: null /home/dir/nodebb/src/cli/package-install.js:138 throw e; ^ Error: Command failed: npm install --omit=dev at checkExecSyncError (node:child_process:885:11) at Object.execSync (node:child_process:957:15) at pkgInstall.installAll (/home/dir/nodebb/src/cli/package-install.js:129:9) at Object.<anonymous> (/home/dir/nodebb/src/cli/index.js:52:18) at Module._compile (node:internal/modules/cjs/loader:1254:14) at Module._extensions..js (node:internal/modules/cjs/loader:1308:10) at Module.load (node:internal/modules/cjs/loader:1117:32) at Module._load (node:internal/modules/cjs/loader:958:12) at Module.require (node:internal/modules/cjs/loader:1141:19) { status: 217, signal: null, output: [ null, null, null ], pid: 1921, stdout: null, stderr: null } Node.js v18.16.0
-
@crazycells I guess I am the only sausage fingers around here... But I still think it would be better and more practical if 5 boxes of the pagination bar align with the 5 boxes below (social media signs)...
-
For my part, since I upgraded to 3.2.0, the page takes longer to load than before and I see this socket error :
-
@julian said in 3.0.0 Bug Report Thread:
rm -rf node_modules/nodebb-plugin-spam-be-gone
thanks for that, but of course it stopped on another error, trying again to see what it was but in the meantime, what is the most effective cmd line to remove a custom theme, it's not just the same as above, rm -rf node_modules/theme-name, becasue I tried that and it still got stopped on a
npm err:404 .... theme is not in this registry
-
yep @phenomlab I see this bug too