@baris Works! Also just noticed you'd pushed the fix as soon this was notified. Appreciate it!

Hi @baris
Thanks for letting me know. I will do that!

Hi @baris
Theme - Persona
Version - 13.3.37

Not sure if it helps but I personally use No Skin and it's still visible for me.
TIA!

Hi there,

I have upgraded the forum from 3.6.3 to 3.10.3 recently.

Everything seems to be alright except: the notification count is shown twice as follows:

The HTML is as follows:

I have uninstalled 3rd party plugins, rebuilt and checked again and yet the issue is still there.

I was wondering if anyone could give any idea on how to go about this.

TIA!

Hi @baris Thanks for getting back to me. Running v3.6.3. Noted. Will update soon. Thanks!

Hi there,

Greetings!

We have requested the forum to be indexed.

Not sure if this is a bug but posting here as it seems to be (or a potential improvement)

We received the following response:

Was wondering whether there is anything we have to change to set it up from our side?

For ref - Google Search Central Documentation

TIA!

Hi @baris
Sorry about the delay. Had to confirm again.
Yeah this header was present throughout the site surprisingly. Have to check if it's the same once upgraded.

Hi @baris

Commenting the following out in composer.js file did the trick:

res.locals.metaTags = {
		...res.locals.metaTags,
		name: 'robots',
		content: 'noindex',
	};

Does this mean all forums are by default set to be 'noindex' ? or have I missed a step when setting the forum up.

Hi there,

Greetings!

So wasn't quite sure where to post this so figured might as well try my luck in General.

I am running v3.6.3, the usual setup with Nginx.

During testing, I added a noindex tag via Nginx after which I removed and straightaway edited the src/meta/tags.js file. However, I've now removed it but even when I rebuild and restart, the noindex header is still shown when I look at the site via developer tools.
I am not sure what's causing this. I have checked build files but haven't been able to figure it out.

Hoping someone would point me in the right direction or where to look.

Thanks!

Update: I did a local build and tested using multiple browsers. Still the behaviour is the same as https://community.nodebb.org/post/98116

I see. This is how it is in my case.

Behaviour - Video

Inspect - Video

Hi @baris
We have found what seems to be a bug with the Persona chat modal.

1. chat-modal class is spanned across the screen even though the actual chat modal is modal-content class. When the chat modal is open, nothing above and to the right behind it are clickable.
2. 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.
3. When we move it all the way down, it disappears and if we want to take it back, we need to refresh the page

Hi @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?

Seems 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

Hi @baris
Thanks very much. Will try that out

Are the following NodeBB behaviours normal? Is there a way around them?

1. Editing chats by admins is possible. Is it possible to turn it off?
2. 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?
3. 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.
   

@marksibly
I encountered the same issue. InternalLink

Sorted it by adding proxy_set_header X-Forwarded-Proto $scheme; in the nginx conf file

@DownPW Haha jinxx

Update: It got solved by adding the following in nginx after reading InternalLink.

proxy_set_header X-Forwarded-Proto $scheme;