Buy Hosting

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Localisation incomplete - groups [0.7.0 dev]

5 Posts 3 Posters 1.7k Views

H Offline

H Offline
Hägar
wrote on last edited by

#1

The popup is not localised and the search field contains a non-localised placeholder.
1 Reply Last reply
1
N Offline

N Offline
nhl.pl
wrote on last edited by

#2

Please use Bug Tracker.
https://github.com/NodeBB/NodeBB/issues

Look here for an example how to report i18n related issues.
https://github.com/NodeBB/NodeBB/issues/3009
1 Reply Last reply
0
H Offline

H Offline
Hägar
wrote on last edited by

#3

Done. _____
1 Reply Last reply
0
J Offline

J Offline
julian GNU/Linux
wrote on last edited by

#4

Resolved
1 Reply Last reply
0
H Offline

H Offline
Hägar
wrote on last edited by

#5

Great.
1 Reply Last reply
0

Suggested Topics

J

Groups - Category IDs to display posts from
Scheduled Pinned Locked Moved Bug Reports bug

0 Votes

3 Posts

372 Views

J

Ahh, ok! Will check that out!
E

Notification sound does not work on 1.5.0
Scheduled Pinned Locked Moved Bug Reports

0 Votes

1 Posts

944 Views

E

Only option available is "no sound" on both user and ACP.

Sound does not work on 1.5.0 · Issue #5678 · NodeBB/NodeBB
Links are created but the only option (both on user and ACP) is "no sound". Mongo Linux
favicon
GitHub (github.com)
A

JavaScript Error for NodeBB V1.0.0 on Chrome browser latest version 55.
Scheduled Pinned Locked Moved Bug Reports

0 Votes

6 Posts

3k Views

A

Thanks for the support!!
@julian @Bri @PitaJ

I have upgraded Nodejs version to v4.7.0 and It solved the problem.
P

O.8.0 Bug Images with German ÄÜÖ in the file name
Scheduled Pinned Locked Moved Bug Reports

0 Votes

4 Posts

3k Views

B

Pretty sure its the regex in composer-default plugin that's exploding on those chars.
G

Merge conflicts in 0.6.1
Scheduled Pinned Locked Moved Bug Reports

0 Votes

7 Posts

3k Views

S

@Shaun said:

Have tried git reset --hard

So the resolution for me was:

git reset --hard 4686ae992318eeaaff1945868ee4cc094dcda17d
git pull

Wasn't sure where to find the hash, but git put it in the package.json file. I did not alter this file or any other after installing 0.6.0, so I'm very confused about how this conflict arose. The conflicting line was the version number, which in my local file was, apparently, 0.7.0-dev (I believe). Again, no clue how that got in there.

Copyright © 2023 NodeBB | Contributors