No, NodeBB doesn't support it. Why not just use multiple databases?
[Solved] Pagination widget broken
whoops, 0.4.x yes
it used to work before 4.3
Hi @Ezra-Sharp, can you let me know what language you have set your NodeBB to?
Edit: I am seeing that in en_US, the pagination shows
pagination.out_of... this is due to the fallbacks not being implemented in that language. The others should be fine...
Edit 2: Latest v0.4.x branch should resolve this -- I've added that specific language string back in for en_US, vi, pt_BR, and de.
@julian the language is en_GB,
But this gets weirder, when I am logged in as myself this issue still exists. However, when I created a new account and logged in with that. the issue was gone. Same language settings on this account too (en_GB).
Then came back when I logged in with my old account again.
Hm, so the issue only occurs on your account?
@julian, Seems so. Unfortunate that its the main admin account
Okay. Any new accounts should have no languages set (so it would default to the system-wide language). Your admin account is set to en_GB in the user profiles section, right?
Try switching to en_US... is it resolved? What if you switch back to en_GB?
Well, system wide is set to en_GB.
My user language was set to en_US, when I changed it to en_GB the problem was fixed. And when I changed it back to en_US; the issue came back.
I also tried changing to board settings to en_US, but that did not seem to affect either case.
@julian hmm, however..
I logged in with the new non-admin account and changed its language settings to en_US, and the issue showed there also.
Seems to be an issue with the user language settings being en_US.
You might see the issue first-hand if you created an account.
https://community.ag-aus.org/category/2/general-discussion (All the SSO registrations are broken, but normal regos work).
Yes... you are on v0.4.3, yes? Are you using the downloaded version, or the latest commits from git?
The last commit from June 30th should've fixed that bug for en_US...
@julian boom, apparently did not have than June 30th commit.
Issue is resolved. Thank you