Technical Support

@phit said in Invalid CSRF Token:

for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration

Thank you very much. This really made my day !!!

@FrankM said in Probmes with login after upgrading to 1.11.0:

But in config.json i have http://...... Edit it to https:// solved the problem.
Before version 1.11.0 i don't have this problem.

Thanks, that solved the problem for me as well, changing http to https. And as for you, I did not have this problem before 1.11.0

But then an other problem turned up: "Invalid CSRF Token"

Pls see this link https://community.nodebb.org/topic/9222/invalid-csrf-token

My solution for this was what is written in the end (I use Apache2)

for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration
with ssl

RequestHeader set X-Forwarded-Proto "https"

without ssl

RequestHeader set X-Forwarded-Proto "http"

you might have to enable mod_headers to do so!

So upgrading to 1.11.0 gave me a problem that had to be solved in 2 steps. First by changing in config.json, then I had to modify Apache2 settings.

@PitaJ i've made a persona child theme mantaining the same widget :

{ name: "Categories Sidebar", template: "categories.tpl", location: "sidebar" }, { name: "Category Sidebar", template: "category.tpl", location: "sidebar" }, { name: "Topic Sidebar", template: "topic.tpl", location: "sidebar" }, { name: "Categories Header", template: "categories.tpl", location: "header" }, { name: "Category Header", template: "category.tpl", location: "header" }, { name: "Topic Header", template: "topic.tpl", location: "header" }, { name: "Categories Footer", template: "categories.tpl", location: "footer" }, { name: "Category Footer", template: "category.tpl", location: "footer" }, { name: "Topic Footer", template: "topic.tpl", location: "footer" }

but i can't see other's than linked screenshot

@baris said in Error after upgrading to 1.11.0:

NodeBB is on version 1.1.0 so the command should use v1.1.x.

1.11.0 worked fine for me.

Worked it out.

In the admin panel:

Manage>Privileges

then tick the 'upload files' box for registered users.

Okay, I'll also look for bugs. I think this happens when I either build, stop, or start from the command line.

Maybe a permission to activate the setting?

Darn, that makes debugging difficult. I guess I'll file a bug with the errors that stopped the digest send.

If you click clear index on the ACP page for the plugin and then reindex it should only reindex the category not excluded.

Greetings,

We are using the default theme, is it possible to make the font size larger? If so how do we do that?

Thank you.

Hello,

I am currently using NodeBB to run a community forum and now I am looking at integrating a Drip Email tool into the forum.
Are there any recommendations on which tools are the most campatible with NodeBB?
Please find a list of popular drip email tools here.

Looking forward to a positive response!

@baris

New error, hope it's okay:

4. Updating NodeBB data store schema... Parsing upgrade scripts... 2018-11-30T15:21:24.425Z [24448] - warn: [upgrade/appendPluginScripts] Unable to read plugin.json for plugin `nodebb-plugin-import-smf-1`. Skipping. OK | 1 script(s) found, 67 skipped → [2019/1/26] Changing dbsearch mongodb search schema to use _id... 2018-11-30T15:21:24.509Z [24448] - error: ns not found MongoError: ns not found at /var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"} 2018-11-30T15:21:24.512Z [24448] - error: ns not found MongoError: ns not found at /var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:581:63 at authenticateStragglers (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:504:16) at Connection.messageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/pool.js:540:5) at emitMessageHandler (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:310:10) at Socket.<anonymous> (/var/srv/nodebb/node_modules/mongodb/node_modules/mongodb-core/lib/connection/connection.js:453:17) at emitOne (events.js:116:13) at Socket.emit (events.js:211:7) at addChunk (_stream_readable.js:263:12) at readableAddChunk (_stream_readable.js:250:11) at Socket.Readable.push (_stream_readable.js:208:10) {"ok":0,"errmsg":"ns not found","code":26,"codeName":"NamespaceNotFound","name":"MongoError"}

Thanks for the help BTW.

Problem solved with version 3.

here was the offending line:

body { height: 100%; }

@baris said in Choosing forum software - a couple of questions:

There is no quick way to find threads that you took part in but you can watch topics or bookmark posts, or watch topics automatically when you reply to them.

I see. But this way requires user action on each post and does not work on old posts. I could make it the default but that would make the normal usage of watching posts not very useful.

So I hope it would be easy to write a plugin or some other extension which would add the "threads you took part in" link?

thanks!
all good now.

I hadn't noticed that the header.tpl template had been changed here:
https://github.com/NodeBB/nodebb-theme-persona/commit/90a1ba1eb1f5377c45c44656d3172389656c5a90

Great Idea! I took your solution and added a few lines of CSS to hide the downvote arrow and remove the whitespace.

// Change the icon for votes span.votes { // not voted is outline heart .fa-chevron-up:before { content: "\f08a"; } // upvoted is solid heart .upvoted .fa-chevron-up:before { content: "\f004"; } } // hide the downvote element to remove whitespace a[component="post/downvote"] { display: none; } // reduce margin of post-submenue for alignment .topic .moderator-tools { margin-left: 0px; }

Inspect your category data, it seems you have some invalid data in there.

@baris Those are already updated on my side. So the developers need to bring out updates, right?

Thank you - no more errors/warnings.

@PitaJ we can't do that at this time, it seems like it is working good, in few weeks we would acquire more ram if it's the problem.

Thank you very very much!