Update: I did a local build and tested using multiple browsers. Still the behaviour is the same as https://community.nodebb.org/post/98116
yasas
Posts
-
Chat and Search Behaviour NodeBB 3.x -
Chat and Search Behaviour NodeBB 3.x -
Chat and Search Behaviour NodeBB 3.xHi @baris
We have found what seems to be a bug with the Persona chat modal.chat-modal
class is spanned across the screen even though the actual chat modal ismodal-content
class. When the chat modal is open, nothing above and to the right behind it are clickable.- When we have opened multiple chats, it's stacked on top of each other so if we want to go to another open chat, we need to minimise the one we opened last.
- When we move it all the way down, it disappears and if we want to take it back, we need to refresh the page
-
Chat and Search Behaviour NodeBB 3.xHi @baris
We have to keep using Persona instead of Harmony so we cannot use those theme settings.
Any availability of a custom CSS that we can use for replicating the chat behaviour from 2.x? -
Chat and Search Behaviour NodeBB 3.xSeems the error with search was that
nodebb-widget-search-bar
is not compatible with 3.x. I think since there was a port from scss -> less or vice versa, the styling isn't loading -
Chat and Search Behaviour NodeBB 3.xHi @baris
Thanks very much. Will try that out -
Chat and Search Behaviour NodeBB 3.xAre the following NodeBB behaviours normal? Is there a way around them?
- Editing chats by admins is possible. Is it possible to turn it off?
- Chat dialog blocks the whole site. It there any way to to turn that off and have it work like in 2.x where you can navigate the forum with a chat open?
- Using the Persona theme. Any chance of stopping the search results from blocking the page? (When there are more posts, it blocks the whole thing). Also seems it's not styled well but don't see any errors in the Network tab about loading CSS.
-
Login failing, "likely due to an expired session."@marksibly
I encountered the same issue. InternalLinkSorted it by adding
proxy_set_header X-Forwarded-Proto $scheme;
in thenginx
conf file -
CSRF Error - NodeBB 3.x@DownPW Haha jinxx
-
CSRF Error - NodeBB 3.xUpdate: It got solved by adding the following in nginx after reading InternalLink.
proxy_set_header X-Forwarded-Proto $scheme;
-
CSRF Error - NodeBB 3.xHi there,
I have a test forum (3.x) where everything works. Set it up following the instructions (serving using nginx) and its
config.json
looks like:{ "url": "http://forum.beta.....", "secret": "super_secret_xxx", "database": "mongo", "mongo": {... }, "port": [4567,4568,4569], "redis": {... }, "upload_path":"some_upload_path" }
I recently setup HTTPS (using letsencrypt) and since plugins are using the
url
fromconfig.json
, I changed it fromhttp
tohttps
.
Now I cannot login or do anything as it's throwing a CSRF error. I deletedbuild
files andnode_modules
just in case and rebuilt and the issue is still there.
However, when I change theurl
back tohttp
, the issue goes away but this isn't preferable as then the client side is requesting via bothhttp
andhttps
which the browser blocks. I've attached./nodebb log
,config.json
, and login screen with the error.Any help would be appreciated. TIA!
[FYI]:
I have followed instructions but the issue is still there InternalLink, ExternalLink -
./nodebb build vs ./nodebb upgrade -
./nodebb build vs ./nodebb upgradeHi @baris Got it.. Thanks. So
./nodebb install
is just to install the node_modules yeah? -
./nodebb build vs ./nodebb upgradeOut of curiosity, I was wondering what different actions these two perform as often I've used them interchangeably during upgrade testing (upgrading 2.x to 3.x) which has seemed to work without issues.
Like, does
upgrade
perform install and build too? And what's missing from build is just the migration steps?TIA
-
3.6.0 Upgrade Support@baris Perfect. Thanks very much for clarifying!
-
3.6.0 Upgrade Support -
3.6.0 Upgrade SupportHi @baris
Thanks for the response.- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
* Install v3.6.3 in one go on a new VM, restore the dump and connect the DB and public uploads
Do you mean that instead of installing v3.6.3 straightaway and restoring the DB dump (dumped from v2.8.1 earlier), it would be wiser to install v2.8.1 on a new VM, restore the db dump, and then upgrade to V3.6.3?
- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
-
3.6.0 Upgrade SupportHi @baris
Thanks for opening this topic.
I am currently running v.2.8.1 and need to upgrade to the latest (v3.6.3).
I plan to shut down my current VM and choose a different provider. I will be taking a dump from the current MongoDB and backing up public uploads so I can connect the same DB with v3.6.3.
I did some reading but could not find anything that says that there is any discrepancy between a v2.x db and a v3.x db. Neither have I had a chance to perform this on a test server yet so was wondering to perform the upgrade as above in a totally new VM whether I need to:
- Install my current version on a new VM, restore the dump and connect the DB and public uploads, and then upgrade that to v3.6.3
- Install v3.6.3 in one go on a new VM, restore the dump and connect the DB and public uploads
Any insight would be appreciated!
Thanks -
NodeBB Assets - Object StorageHi there,
Greetings!
I have been thinking about serving assets from an S3 bucket or another object storage. (I came across the plugin https://github.com/NodeBB-Community/nodebb-plugin-s3-uploads but yet to check)
I was wondering whether it's possible to "effectively" serve from S3 buckets/a different object storage in different availability zones depending on the client (US/UK/Europe/Asia) to reduce the time that the assets take to load.
Also, I would love to hear about any other possible configurations anyone is using/suggesting with "serving different geo-locations" in mind.
Thank you
-
Unread Count on Custom Navigation Item IconUpdate:
Was able to sort this with a client script.
Example usage:
plugin.json ->{ "hook": "filter:navigation.available", "method": "addNavigation" }
plugin.json ->"scripts": [ "static/lib/client-script.js",... ],
library.js addNavigation:
append the following to the hookData object:{ route: '<some route>', title: <some title>, id: 'unread-count', iconClass: '<some icon> custom-class-name', text: <some title> }
client-script.js:
$("#unread-count .custom-class-name").attr("data-content",<unread count>)