3.0.0 Bug Report Thread
-
@baris said in 3.0.0 Bug Report Thread:
maybe we can flip the scroller to the right so the text can grow to the left.
Or remove translate and use only
"23 of 120"
or"23/120"
or change position for text if long number, like on flarum or hide translation for md screens and add width in navigator on big screen, to make the reserve of place for any language... -
I think scrolled on left and date on right - this is a beautiful and usability, the classic
-
Feedback upgrade to version 3
The upgrade to version 3, afterwards feels kind of broken. The post editor doesn't respond on the buttons I running my Nodebb in Tor. The admin panel in rus...
NodeBB Community (community.nodebb.org)
-
There some critical bugs, and the request-promise-native npm module is already deprecated somebody need to switch to another lib, which is maintained.
-
@NikolaiPatrushev Eventually, yes, this will be replaced with
node-fetch
or some similar alternative.There is no immediate rush only because
request
(and its variants likerequest-promise
andrequest-promise-native
) are deprecated because it is feature complete, not due to some security concern, unless I am mistaken. -
@dave1904 you can do this with my search utility quite easily. It's on the below if you want to try it out.
Look for the font awesome swatch icon at the top of the page
-
What about problems with assets?
404 Not Found for a assets/templates/ , the build was success without any warnings.
Look the error output https://community.nodebb.org/topic/17156/feedback-upgrade-to-version-3/6 -
-
Here another blocker issue which i have with latest nodebb 3.X version
Whenever i click on the menus , i dont see page change and drop down menu is not loaded -
There is no
templates/alert.tpl
anymore in 3.x, it's been moved totemplates/partials/toast.tpl
make sure you don't have any outdated plugins. I suggest disabling 3rd party plugins and rebuilding to see if the error goes away. Then you can find the one that causes the issue.If you start nodebb in dev mode, then you can click the javascript error you see in the browser console and it should show you the location of the error.
-
Ok, fine, but still it's strange i prefer convention over verbosity.
Sure my problems appeared only after i installed 3.x, because early the plugins devs did not provided newer versions of theirs plugins for the newer nodebb version, i admit it's my fault , because i didn't knew about big changes in v3.x
Now i took the package.json from the github branch 3.x install directory and deleted all npm modules and the file package-lock.json in my current nodebb, so after all work i found that my default composer was disabled , now it is enabled and here the outcome :
It looks like, now it works finally!
Strange that my default composer was disabled, but now it is enabled.
I will report if i find any breaking issues with the plugins, i hope that i wont find any breaking issues.So far i like what i see, it really fast , the performance in Tor is fast as lightning thanks! Great job overall!!!