Skip to content
  • Home
  • Categories
  • Recent
  • Popular
  • World
  • Top
  • Tags
  • Users
  • Groups
  • Documentation
    • Home
    • Read API
    • Write API
    • Plugin Development
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor
  • Default (No Skin)
  • No Skin
Collapse
Brand Logo
v3.12.0 Latest
Buy Hosting
  1. Home
  2. Technical Support
  3. 1.19.3 Support Thread

1.19.3 Support Thread

Scheduled Pinned Locked Moved Technical Support
1.19.3support
32 Posts 12 Posters 5.1k Views
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • kurulumu.NetK Offline
    kurulumu.NetK Offline
    kurulumu.Net
    replied to PitaJ on last edited by
    #6

    @PitaJ but it didn't work. otherwise this is not the first update for me.

    1 Reply Last reply
    0
    • DownPWD Offline
      DownPWD Offline
      DownPW Translator
      wrote on last edited by DownPW
      #7

      @kurulumu-Net

      Very odd, for me, this is perfecty functionnal :

      git fetch
git reset --hard origin/v1.19.x
./nodebb upgrade
      phenomlabP 1 Reply Last reply
      0
      • phenomlabP Offline
        phenomlabP Offline
        phenomlab Community Rep GNU/Linux
        replied to DownPW on last edited by
        #8

        @DownPW I used exactly the same mechanism (which I've always used) and this also worked without issue.

        kurulumu.NetK 1 Reply Last reply
        0
        • kurulumu.NetK Offline
          kurulumu.NetK Offline
          kurulumu.Net
          replied to phenomlab on last edited by
          #9

          @phenomlab After Hetzner made the switch, interesting things started to happen. For example, port 465 is closed for security by default 🙂 Standard update commands didn't work for me. It's really weird.

          phenomlabP 1 Reply Last reply
          0
          • phenomlabP Offline
            phenomlabP Offline
            phenomlab Community Rep GNU/Linux
            replied to kurulumu.Net on last edited by
            #10

            @kurulumu-Net Very odd indeed. As you know, I'm a Hetzner customer myself, and am not experiencing these issues. Admittedly, I do not use port 465, but 587

            1 Reply Last reply
            0
            • AlekseiA Offline
              AlekseiA Offline
              Aleksei
              wrote on last edited by
              #11

              I have a similar problem with upgrade. Performing it as usual:

              git reset --hard origin/v1.19.3
              fatal: ambiguous argument 'origin/v1.19.3': unknown revision or path not in the working tree.
              Use '--' to separate paths from revisions, like this:
              'git <command> [<revision>...] -- [<file>...]'

              PitaJP 1 Reply Last reply
              0
              • PitaJP Offline
                PitaJP Offline
                PitaJ Global Moderator Plugin & Theme Dev
                replied to Aleksei on last edited by
                #12

                @Aleksei you're supposed to do literally

                git reset --hard origin/v1.19.x
                AlekseiA 1 Reply Last reply
                0
                • AlekseiA Offline
                  AlekseiA Offline
                  Aleksei
                  replied to PitaJ on last edited by
                  #13

                  @PitaJ I was following the offical guide:

                  9d53c0c6-337b-4b65-a8ac-86910640ac71-image.png

                  So in this case the brach name is origin/v1.19.3 or origin/v1.19.x ?

                  volanarV julianJ 2 Replies Last reply
                  0
                  • volanarV Offline
                    volanarV Offline
                    volanar Translator
                    replied to Aleksei on last edited by volanar
                    #14

                    @Aleksei git reset --hard origin/v1.19.x

                    1 Reply Last reply
                    0
                    • julianJ Offline
                      julianJ Offline
                      julian NodeBB GNU/Linux
                      replied to Aleksei on last edited by
                      #15

                      @Aleksei The branch name is v1.19.x, the remote is origin (that's the default, unless you've changed it)

                      So git reset origin/v1.19.x says "git, please change my working directory to match the latest commits on the v1.19.x branch"

                      If you want to reset to a specific VERSION, then you don't need the remote. git reset --hard v1.19.3 should work fine.

                      1 Reply Last reply
                      3
                      • AlekseiA Offline
                        AlekseiA Offline
                        Aleksei
                        wrote on last edited by Aleksei
                        #16

                        Thank you for the detailed reply! I was confused by the examples in the documentation.

                        1 Reply Last reply
                        2
                        • AndreyA Offline
                          AndreyA Offline
                          Andrey
                          wrote on last edited by
                          #17

                          Hello! Broken links and hints (1.19.3)

                          I have replaced one icon in the menu. After that, unformatted template text appeared in the title, tooltips, and links. The category names also have a strange display of some characters.

                          Updating the markdown plugin to version 9.0.8 didn't help. Rebuilding the frontend didn't help either.

                          Please tell me how to fix

                          9be433b7-7a88-4871-aeb8-d2c6d687d8bb-image.png

                          104c387f-04b9-408d-b8a5-f92338987542-image.png

                          AndreyA 1 Reply Last reply
                          0
                          • AndreyA Offline
                            AndreyA Offline
                            Andrey
                            replied to Andrey on last edited by
                            #18

                            @Andrey

                            The problem is global

                            62661609-3bed-4b6d-b30b-efd3dc812afe-image.png

                            julianJ 1 Reply Last reply
                            0
                            • julianJ Offline
                              julianJ Offline
                              julian NodeBB GNU/Linux
                              replied to Andrey on last edited by
                              #19

                              @Andrey Try replacing all of the &lsqb; to [ and &rsqb; to ]

                              Those are language keys, they shouldn't be escaped into html entities.

                              AndreyA 2 Replies Last reply
                              1
                              • AndreyA Offline
                                AndreyA Offline
                                Andrey
                                replied to julian on last edited by
                                #20

                                @julian I changed "popular" to [[global:header.popular]] and it works! Thanks!

                                But when I re-enter this section of the settings, all the fields again take the form:

                                &lsqb;&lsqb;global:header.popular&rsqb;&rsqb;

                                I'm also not sure that this can't affect service addresses, including

                                1 Reply Last reply
                                0
                                • AndreyA Offline
                                  AndreyA Offline
                                  Andrey
                                  replied to julian on last edited by
                                  #21

                                  @julian Also I see the problem from this thread 😢

                                  1 Reply Last reply
                                  0
                                  • crazycellsC Offline
                                    crazycellsC Offline
                                    crazycells
                                    wrote on last edited by crazycells
                                    #22

                                    our update to 1.19.3 from 1.18.6 failed...

                                    forum has language problems... and this is the log:

                                    
Clustering enabled: Spinning up 3 process(es).

2022-02-27T03:30:48.522Z [4567/2929] - info: Initializing NodeBB v1.19.3 https://yesilkartforum.com/forum
2022-02-27T03:30:52.524Z [4568/2935] - info: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:52.740Z [4569/2936] - info: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:53.071Z [4567/2929] - info: [socket.io] Restricting access to origin: https://yesilkartforum.com:*
2022-02-27T03:30:53.585Z [4568/2935] - info: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:53.633Z [4568/2935] - info: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:53.737Z [4568/2935] - info: [router] Routes added
2022-02-27T03:30:53.741Z [4569/2936] - info: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:53.800Z [4568/2935] - info: NodeBB Ready
2022-02-27T03:30:53.817Z [4568/2935] - info: Enabling 'trust proxy'
2022-02-27T03:30:53.828Z [4568/2935] - info: NodeBB is now listening on: 0.0.0.0:4568
2022-02-27T03:30:53.916Z [4569/2936] - info: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:53.957Z [4569/2936] - info: [router] Routes added
2022-02-27T03:30:53.965Z [4569/2936] - info: NodeBB Ready
2022-02-27T03:30:53.967Z [4569/2936] - info: Enabling 'trust proxy'
2022-02-27T03:30:53.970Z [4569/2936] - info: NodeBB is now listening on: 0.0.0.0:4569

2022-02-27T03:30:54.072Z [4567/2929] - warn: [plugins/load] The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. In the event of an unresponsive NodeBB caused by this plugin, run `./nodebb reset -p PLUGINNAME` to disable it.
  * nodebb-plugin-calendar
  * nodebb-plugin-twitter

2022-02-27T03:30:54.203Z [4567/2929] - info: [plugins/spam-be-gone] Settings loaded
2022-02-27T03:30:54.283Z [4567/2929] - info: [api] Adding 0 route(s) to `api/v3/plugins`
2022-02-27T03:30:54.296Z [4567/2929] - info: [router] Routes added
2022-02-27T03:30:54.307Z [4567/2929] - info: NodeBB Ready
2022-02-27T03:30:54.310Z [4567/2929] - info: Enabling 'trust proxy'
2022-02-27T03:30:54.312Z [4567/2929] - info: NodeBB is now listening on: 0.0.0.0:4567
  started
2022-02-27T03:31:26.286Z [4568/2935] - info: [build] Building in series mode
2022-02-27T03:31:26.287Z [4568/2935] - info: [build]         plugin static dirs  build started
2022-02-27T03:31:26.304Z [4568/2935] - info: [build]         plugin static dirs  build completed in 0.017sec
2022-02-27T03:31:26.304Z [4568/2935] - info: [build]          requirejs modules  build started
2022-02-27T03:31:33.553Z [4568/2935] - info: [build]          requirejs modules  build completed in 7.248sec
2022-02-27T03:31:33.553Z [4568/2935] - info: [build]           client js bundle  build started
2022-02-27T03:31:36.274Z [4568/2935] - info: [build]           client js bundle  build completed in 2.721sec
2022-02-27T03:31:36.282Z [4568/2935] - info: [build]            admin js bundle  build started
2022-02-27T03:31:39.209Z [4568/2935] - info: [build]            admin js bundle  build completed in 2.927sec
2022-02-27T03:31:39.209Z [4568/2935] - info: [build]         client side styles  build started
2022-02-27T03:31:44.383Z [4568/2935] - info: [build]         client side styles  build completed in 5.174sec
2022-02-27T03:31:44.383Z [4568/2935] - info: [build] admin control panel styles  build started
2022-02-27T03:31:47.562Z [4568/2935] - info: [build] admin control panel styles  build completed in 3.179sec
2022-02-27T03:31:47.562Z [4568/2935] - info: [build]                  templates  build started
[benchpress] warning: output bloat due to ambiguous inner BEGIN
     --> admin/plugins/canned-responses.tpl:44:17
      |
   44 | 						<!-- BEGIN responses -->
      | 						           ^^^^^^^^^ `responses` could refer to the top-level value `responses` or the `.responses` property of the current element, so compiler must emit code for both cases
      | note: Migrate to modern syntax to avoid the ambiguity. This will become an error in the future.

2022-02-27T03:31:48.434Z [4568/2935] - info: [build]                  templates  build completed in 0.872sec
2022-02-27T03:31:48.434Z [4568/2935] - info: [build]                  languages  build started
2022-02-27T03:31:49.055Z [4568/2935] - error: [build]                  languages  build failed
2022-02-27T03:31:49.055Z [4568/2935] - error: [build] Encountered error during build step
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
2022-02-27T03:31:49.055Z [4568/2935] - error: admin.reload
Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
Missing translation "pages:maintenance.text" for language "en-GB"
Missing translation "pages:maintenance.messageIntro" for language "en-GB"
Missing translation "global:500.title" for language "en-GB"
Missing translation "global:500.message" for language "en-GB"
Missing translation "error:goback" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:guest" for language "en-GB"
Missing translation "global:header.search" for language "en-GB"
Missing translation "global:search" for language "en-GB"
Missing translation "global:login" for language "en-GB"
Missing translation "language:dir" for language "en-GB"
                                    barisB 1 Reply Last reply
                                    0
                                    • crazycellsC Offline
                                      crazycellsC Offline
                                      crazycells
                                      wrote on last edited by
                                      #23

                                      additionally, we are having this problem while trying to install extended-markdown plugin...

                                      2022-02-27T05:50:26.207Z [4568/1274] - error: admin.plugins.toggleInstall
Error: Command failed: npm install [email protected] --save
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/nodebb-plugin-markdown
npm ERR!   nodebb-plugin-markdown@"9.0.8" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer nodebb-plugin-markdown@"8.x" from [email protected]
npm ERR! node_modules/nodebb-plugin-extended-markdown
npm ERR!   nodebb-plugin-extended-markdown@"1.5.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /home/fsuzer/.npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/fsuzer/.npm/_logs/2022-02-27T05_50_23_241Z-debug-0.log

    at ChildProcess.exithandler (node:child_process:399:12)
    at ChildProcess.emit (node:events:520:28)
    at maybeClose (node:internal/child_process:1092:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
    at Process.callbackTrampoline (node:internal/async_hooks:130:17)

Logs Control Panel
                                      1 Reply Last reply
                                      0
                                      • barisB Offline
                                        barisB Offline
                                        <baris> NodeBB
                                        replied to crazycells on last edited by
                                        #24

                                        @crazycells said in 1.19.3 Support Thread:

                                        2022-02-27T03:31:49.055Z [4568/2935] - error: [build] Encountered error during build step
                                        Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'
                                        2022-02-27T03:31:49.055Z [4568/2935] - error: admin.reload
                                        Error: EMFILE: too many open files, open '/home/fsuzer/nodebb/public/language/sc/admin/manage/tags.json'

                                        This error happens because of limits in the OS, check the open file limit with ulimit -Hn & ulimit -Sn and increase it if its too low. https://linuxhint.com/increase-open-file-limit-ubuntu/

                                        crazycellsC 1 Reply Last reply
                                        1
                                        • crazycellsC Offline
                                          crazycellsC Offline
                                          crazycells
                                          replied to <baris> on last edited by
                                          #25

                                          @baris thanks.

                                          any idea how to install the extended-markdown plugin without error? we had to remove all of them to prevent errors, all but this one was OK to re-install...

                                          1 Reply Last reply
                                          0

                                          Copyright © 2024 NodeBB | Contributors
                                          • Login
                                          • Don't have an account? Register
                                          • Login or register to search.
                                          Powered by NodeBB Contributors
                                          • First post
                                            Last post
                                          0
                                          • Home
                                          • Categories
                                          • Recent
                                          • Popular
                                          • World
                                          • Top
                                          • Tags
                                          • Users
                                          • Groups
                                          • Documentation
                                            • Home
                                            • Read API
                                            • Write API
                                            • Plugin Development