1.19.3 Support Thread

[baris]

We had quite a bit of new topics about 1.19.2 so I am creating this thread for 1.19.3. Maybe we will create a new one of these for each release going forward.

1.19.3 Closed Issues

[kurulumu.Net]

@baris This command in the official documentation didn't work when upgrading between branches. It is necessary to leave a character space in between.
What's in the document:

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

Working for me:

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

Thank you for the update. The team is working hard

[PitaJ]

@kurulumu-Net that's absolutely incorrect, it should only work without the space you added.

[fffddd dfeeedd]

@baris When scrolling down the page, it skips a line by itself. Is the problem with me or is it a software problem?

[fffddd dfeeedd]

@fffddd-dfeeedd on mobile

[kurulumu.Net]

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

[DownPW]

@kurulumu-Net

Very odd, for me, this is perfecty functionnal :

git fetch
git reset --hard origin/v1.19.x
./nodebb upgrade

[phenomlab]

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

[kurulumu.Net]

@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.

[phenomlab]

@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

[Aleksei]

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>...]'

[PitaJ]

@Aleksei you're supposed to do literally

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

[Aleksei]

@PitaJ I was following the offical guide:

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

[volanar]

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

[julian]

@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.

[Aleksei]

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

[Andrey]

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

[Andrey]

@Andrey

The problem is global

[julian]

@Andrey Try replacing all of the [ to [ and ] to ]

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

[Andrey]

@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:

[[global:header.popular]]

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