3.0.0 Bug Report Thread

inspiring

@baris
could you open a chat with me?

NikolaiPatrushev

Ok on 3.1.2 everything works!

brazzerstop

Hey guys!

Today forum was updated to version 3.1.4 and I noticed this error in the event journal after rebooting, I hope this is not critical?

2023-05-20T10:46:05.069Z [4567/3445] - [32minfo[39m: [app] Shutdown complete.
2023-05-20T10:46:06.027Z [4567/3601] - [32minfo[39m: Initializing NodeBB v3.1.4 https://example.com
node:events:491
      throw er; // Unhandled 'error' event
      ^

Error: write EPIPE
    at process.target._send (node:internal/child_process:874:20)
    at process.target.send (node:internal/child_process:747:19)
    at process.<anonymous> (/var/www/nodebb/src/meta/minifier.js:118:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
Emitted 'error' event on process instance at:
    at node:internal/child_process:878:39
    at processTicksAndRejections (node:internal/process/task_queues:78:11) {
  errno: -32,
  code: 'EPIPE',
  syscall: 'write'
}
2023-05-20T10:46:09.048Z [4567/3601] - [32minfo[39m: [socket.io] Restricting access to origin: https://example.com:*

After restart mongo I don't view this error

+ Bootstrap

2023-05-20T11:01:29.875Z [4567/4265] - [32minfo[39m: 🔗 Canonical URL: https://example.com
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;
    │                                                               ^^^^^^^^
    ╵

+ FontAwesome

Add icons from FontAwesome to Icons list on Nodebb

thx for the support. we'll run the update soon ....

NodeBB Community (community.nodebb.org)

+ Topics Thumbnail

Please add setting in privileges page to allow upload topic thumbnails only for users from some group.

On the /settings/uploads settings admin can only enable/disable thumbnails upload for the all users, so if disable it, admins can't upload thumbnails too.

And add sort label on users page...

ScreenShot 2023-05-20 в 19.29.25.png

<baris>

The bootswatch warnings are fixed in the dependency https://github.com/thomaspark/bootswatch/pull/1246

NikolaiPatrushev

Let me confirm that the latest version of 3.1.4 works in tor too.

brazzerstop

Quote button not work for me on iPad, Safari.
When I click on the button nothing happens.

inspiring

@baris

overflow issue in phone when we use below code

.post-container .content p{
        direction: rtl;
}

In order for the entire content of the post to be RTL, even when the sentence starts with English words, but the rest comes from the RTL language

How to solve this problem?

<baris>

Not sure I understand, can you post a screenshot? Mixing rtl and ltr inside the same post content is probably problematic.

inspiring

@baris said in 3.0.0 Bug Report Thread:

Not sure I understand, can you post a screenshot? Mixing rtl and ltr inside the same post content is probably problematic.

like this

inspiring

@baris
When I want to mention a user, because the user name is English, the order of the sentence gets messed up

brazzerstop

UPD

I can open this topic after disable adblock extension in my browser, it's normal?

For the test I posted this url on my forum and now can't open the topic:

AdSense Bug: Please fix '0 clicks' issue - Started since March 2023 for many Publishers - Google AdSense Community

(support.google.com)

It seems strange that a simple ad blocker can harm the forum and prevent opening the topics if that have "advertised" links.

phenomlab

@brazzerstop said in 3.0.0 Bug Report Thread:

It seems strange that a simple ad blocker can harm the forum and prevent opening the topics if that have "advertised" links.

It's not the ad blocker from what I see. I too have an ad blocker and it's the same with or without it. Interestingly, the post URL works fine in an incognito tab.

julian

@phenomlab @brazzerstop it's because the plugin you're using is doing a naive check for the word "adsense" or similar in the URL.

You'll see the same thing happening here on topics with adsense in the title slug.

Incognito it works possibly because your ad blocker plugin isn't running in incognito?

brazzerstop

@phenomlab I use AdGuard, maybe the problem depends on which extension is used.

I wasn't able to open the topic in incognito (safari) mode until I disabled my ad blocker.

https://imgur.com/a/3tHH2wq

eeeee

I've got some bugs happening, in Admin panel, they may be related:

They are different on Laptop / Mobile.

On laptop, the Admin left side panel shows blank, if the browser window is less that 100% open to full size of screen.
So for example if I have a few tiled windows and they are 90% full size, then Admin side bar opens blank
On Android browser in portrait mode cant scroll down, I noticed that problem on the Widgets admin page which I have a separate posts about

eeeee

Also buggy menus on mobile or tablet, in Desktop view.
None of the headings come next to the sidebar icons.
Screenshot_20230526_143940_Chrome~2.jpg

In Admin mode its worse, you dont even get the icons!

Screenshot_20230526_145831_Chrome~2.jpg

EDIT. Changed Theme to Harmony and its fixed!

phenomlab

@eeeee I think this is cache related. Do you still experience the same issues in an incognito session? I had similar issues when upgrading from 2.x to 3.x and it was due to caching.

eeeee

Yes happens incognito too

phenomlab

@eeeee Can you remove any custom css or js you may have and see if the issue improves ?

eeeee

@phenomlab
All working now, after you explained on Sudonix (thanks) about changing to the new Theme Harmony!
I had upgraded to v3 but not changed Theme to the newer one!