3.0.0 Bug Report Thread
-
@DownPW This should fix that
@media (min-width: 1200px) { .page-topic .topic .posts { max-width: 1200px; width: 1200px; } }
And
@media (min-width: 1400px) { .container, .container-lg, .container-md, .container-sm, .container-xl, .container-xxl { max-width: 1320px; } }
-
@DownPW most of those are normal design changes to harmony, not sure about the fontawesome pro icons, but you can probably fix the position of the arrows via css.
@FrankM you screenshot looks to me. What's wrong?
In fact, very little space (screen width) is used for reading.
Actually reading text is easier when it is narrow, think about books/newspapers. If you want you can change it with css @phenomlab provided.
-
Yep ok I'm sure for font awesome pro, if I don't use it, Recent card is ok
-
@baris said in 3.0.0 Bug Report Thread:
To bring back icons for sub categories you need to add
{buildCategoryIcon(@value, "24px", "rounded-circle")}
at https://github.com/NodeBB/nodebb-theme-harmony/blob/main/templates/partials/categories/item.tpl#L23I think i got the icons back in this view!?
-
-
@julian said in 3.0.0 Bug Report Thread:
@FrankM If you updated the theme, then that change you made manually will have to be re-done.
After upgrade my forum to rc2 i got this.
I thought the forum icons were supposed to be displayed there? Or am I understanding something wrong?
Sorry, english is not my main language
Thanks for rc2
-
Maybe explain cli commands to update rc1 (devellop) to RC2 (main) correctly ?
Oups talk to fast
https://community.nodebb.org/topic/17105/nodebb-v3-0-0-rc-2-the-second-release-candidate
-
-
-
Hello @baris
I see this in log with the last commits (upgrade today)
2023-04-15T11:48:47.857Z [4567/1334] - info: 📡 NodeBB is now listening on: 0.0.0.0:4567 2023-04-15T11:48:47.857Z [4567/1334] - info: 🔗 Canonical URL: http://192.168.1.54:4567 DEPRECATION WARNING on line 68, column 52 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 68 │ $nav-link-padding-y: .5rem !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 70, column 56 of ../../node_modules/bootswatch/dist/flatly/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 70 │ $nav-link-disabled-color: $gray-600 !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 79, column 60 of ../../node_modules/bootswatch/dist/litera/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 79 │ $input-group-addon-bg: $gray-200 !default !default; │ ^^^^^^^^ ╵ WARNING: The keyword 'none' must be used as a single argument. ../../node_modules/bootstrap/scss/mixins/_box-shadow.scss 10:9 box-shadow() ../../node_modules/bootstrap/scss/forms/_form-control.scss 40:7 @import bootstrap/scss/_forms.scss 3:9 @import - 18:9 root stylesheet WARNING: The keyword 'none' must be used as a single argument. ../../node_modules/bootstrap/scss/mixins/_box-shadow.scss 10:9 box-shadow() ../../node_modules/bootstrap/scss/forms/_form-select.scss 31:7 @import bootstrap/scss/_forms.scss 4:9 @import - 18:9 root stylesheet DEPRECATION WARNING on line 62, column 208 of ../../node_modules/bootswatch/dist/solar/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 62 │ $font-family-sans-serif: "Source Sans Pro", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol" !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 116, column 63 of ../../node_modules/bootswatch/dist/solar/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 116 │ $navbar-light-color: rgba($black, .4) !default !default; │ ^^^^^^^^ ╵ DEPRECATION WARNING on line 117, column 63 of ../../node_modules/bootswatch/dist/solar/_variables.scss: !default should only be written once for each variable. This will be an error in Dart Sass 2.0.0. ╷ 117 │ $navbar-light-active-color: rgba($black, .7) !default !default; │ ^^^^^^^^ ╵
-
After last upgrade (git pull) I see the blue page with 503 error ( excessive load warning) a very long time 2-3 mins when use
./nodebb restart
and logs in ACP show this:2023-04-16T15:28:14.633Z [4567/24243] - [32minfo[39m: 📡 NodeBB is now listening on: 0.0.0.0:4567 2023-04-16T15:28:14.634Z [4567/24243] - [32minfo[39m: 🔗 Canonical URL: https://site.com WARNING: The keyword 'none' must be used as a single argument. node_modules/bootstrap/scss/mixins/_box-shadow.scss 10:9 box-shadow() node_modules/bootstrap/scss/forms/_form-control.scss 40:7 @import bootstrap/scss/_forms.scss 3:9 @import - 18:9 root stylesheet WARNING: The keyword 'none' must be used as a single argument. node_modules/bootstrap/scss/mixins/_box-shadow.scss 10:9 box-shadow() node_modules/bootstrap/scss/forms/_form-select.scss 31:7 @import bootstrap/scss/_forms.scss 4:9 @import - 18:9 root stylesheet
-
I'm was remove last changes in library.js file and now don't have a Bootstrap warning and 503 error, 3-5 second after restart and forum is worked.
I mean this codes:
https://github.com/NodeBB/nodebb-theme-harmony/commit/6a8aa395d0a7e95726b3ced1ed48a0b1baa27650 -
@brazzerstop https://github.com/NodeBB/NodeBB/commit/05c96033ab61ec7e2dc8d115b1504d26ecbbfd4b I made a change so the minifier doesn't run on the nodebb process, that might help with the startup responsiveness.
-
I think I have a small bug in displaying images in categories. (unless you missed something, it's possiblle !)
I put an image (a .png file with a transparent background for a category but the image is not displayed in the categories and in the header. I tried to clear the browser cache and then the DNS cache, rebuild nodebb, in incognito mode but nothing works-- ACP Catgories settings :
-- Result with no image :