Community

Fixed in qna plugin https://github.com/NodeBB/nodebb-plugin-question-and-answer/commit/07c58b1ae00114a4bdae935db6a66e544b8201ee
[email protected]

Seems like the urls are wrong should be https://community.nodebb.org/post/82372 I will take a look.

Did you check the privileges? Seems like spiders have access but guests don't.

I guess that happens if you don't have the suggested topics and footer widget so quick reply is the last element on the page. Might have to add some bottom margin in that case so it doesn't get hidden behind the navigator and bottom bar.

https://github.com/NodeBB/nodebb-plugin-composer-default/commit/8346b3a462ea86ae711b3b24bbea42a8d8b88b6f

I changed the default behavior so the preview will be visible on first open, unless it was hidden by the user or it was hidden by the admin in the acp page. [email protected]

I will likely change the behaviour of the quick reply box to automatically act as a reply to the LAST post.

Hmm, I don't like this idea, it would result in every post to have the replies dropdown.

Not sure I understand, can you post a screenshot? Mixing rtl and ltr inside the same post content is probably problematic.

NodeBB does not support resizing the image in the composer.

Yeah you can modify the templates https://github.com/NodeBB/NodeBB/blob/master/src/views/404.tpl or use custom css. The body tag gets a class based on which error is rendered like template-404 page-status-404

They are just like regular tags so they can be used via API, but if the user making the request isn't a privileged user they would get an error.

Twitter sso plugin does require an api key/secret pair from twitter.

@NikolaiPatrushev can you access our forum with tor browser without errors? Or is it happening here as well? v3.1.3 has a security fix that changes how we connect with socket.io https://github.com/NodeBB/NodeBB/pull/11573 essentially it uses the csrf_token during the initial connection. Not sure why that breaks tor browser and not others.

It's a standard bootstrap popover so you can use the .popover class to target it. It has .popover-header and .popover-body classes inside.

<div class="popover bs-popover-auto fade" role="tooltip" id="popover619161" data-popper-placement="top" style="position: absolute; inset: auto auto 0px 0px; margin: 0px; transform: translate3d(230.4px, -661.6px, 0px);">
	<div class="popover-arrow" style="position: absolute; left: 0px; transform: translate3d(99.2px, 0px, 0px);"></div>
	<h3 class="popover-header">Level 1: Newbie</h3>
	<div class="popover-body">
		<div> REPUTATION: 1 / 100
			<div class="text-sm fw-normal">Next level: Regular</div>
		</div>
	</div>
</div>

@darkpixlz Most of our home page is built using different widgets. So it is completely up to the site admin.

try.nodebb.org is only using a sidebar widget for example.

I agree with Sam here, please do not try to circumvent the limits. If you want NodeBB to win vote once, spread the word and get your friends & family to vote instead.

@lma-lma thanks for reporting fixed here https://github.com/NodeBB/NodeBB/issues/11620. Was happening when line numbers were enabled.

It's the last week of voting, if you haven't voted already now is your chance.

Let's see if we can get the first spot

The bootswatch warnings are fixed in the dependency https://github.com/thomaspark/bootswatch/pull/1246

You had 2 different problems .

Your package.json had a broken version for request-promise-native and you didn't have indices when you restored your database.

Not sure how the first one happened but the missing indices happens when you only export the objects collection from mongodb. If you want to export the whole database you can use mongodump --db <name_of_db>

You can ignore those scss warnings, they will be fixed once bootswatch updates their scss files.