Glad to hear it is resolved

@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 !!!

I'm switching from Mandrill to Amazon SES. There is an option to send using SMTP. I wasn't able to find an up-to-date version of the Amazon SES plugin that works with NodeBB >= 1. Similarly, based on the Git issues, it looks like the emailer-local and emailer-ssl-smtp plugins also aren't compatible? What are you guys using for SMTP?

Thanks for the write-up @Guiri, always nice to read about other peoples' implementations. Has anyone investigated the use of logrotate for rotating backups?

Is the plugin composer-default activated?

Currently testing with <link href="//vjs.zencdn.net/4.12/video-js.css" rel="stylesheet"> <script src="//vjs.zencdn.net/4.12/video.js"></script> <script type="text/javascript"> $('document').ready(function() { document.createElement('video');document.createElement('audio');document.createElement('track'); }); </script>

You may want to take a look at the Write-Enabled API. Might be helpful from a scripting perspective!

Occurred when hitting /users/. Content loaded but profile image hung for awhile: 29/5 14:32 [15911] - info: NodeBB Ready 29/5 14:32 [15911] - info: Enabling 'trust proxy' 29/5 14:32 [15911] - info: NodeBB is now listening on: 0.0.0.0:4568 29/5 14:32 [15910] - info: [plugins/spam-be-gone] Settings loaded 29/5 14:32 [15910] - info: NodeBB Ready 29/5 14:32 [15910] - info: Enabling 'trust proxy' 29/5 14:32 [15910] - info: NodeBB is now listening on: 0.0.0.0:4567 29/5 15:40 [15910] - error: /trackback/ invalid csrf token

I'm currently using: node -v v0.10.37 on Ubuntu LTS 14.04.2. Has anyone upgraded from Chris Lea to Nodesource? Has anyone tested NodeBB with v0.10.38?

@a_5mith said: Then it shouldn't be recommended as a fix. Yep!

Can you merge into 0.7.x?

One possible problem with this testing is since you use ip_hash in the nginx config and run the locust/siege/ab etc from a machine all the requests will be directed to a single nodebb instance. So having 2 nodebb processes does't help since all requests are coming from the same IP. You can confirm that by checking cpu usage in top during the bench.

Change your config.json to domain.com:4567 Then use nginx to forward reverse proxy 80 to port 4567 using the example in NodeBBs documentation

Thanks again, Baris. Testing now.

Awesome, it's up. How do I get the theme on this forum? It seems to have copied my old lavender with masonry.

@julian @pichalite Any idea if this can be done with some CSS around a widget image? I.e., Only displaying an image in a specific category? The closest key I see is: <span itemprop="title">Category Title</span> But I think we'd have to check that value using the DOM in javascript?

@Shaun said: Have tried git reset --hard So the resolution for me was: git reset --hard 4686ae992318eeaaff1945868ee4cc094dcda17d git pull Wasn't sure where to find the hash, but git put it in the package.json file. I did not alter this file or any other after installing 0.6.0, so I'm very confused about how this conflict arose. The conflicting line was the version number, which in my local file was, apparently, 0.7.0-dev (I believe). Again, no clue how that got in there.

@julian Awesome, thank you.