Also have an issue where iphone users on any browser are having issues.

@julian Yeah, https://github.com/NodeBB/nodebb-plugin-emailer-local does work! Thanks a lot!

SSL version works . I'm having probs editing user profiles. I did make it private but I can't even edit my own admin profile to change the email atm any1 know how this is easily remedied ?

I'm learning something new here everyday! Muchas gracias Señor

@julian said: @priapo Keep in mind putting a socket.io section in config.json doesn't do anything We had just talked about this configuration option short time ago in the issue so obviously it does affect. But "transports": ["polling","websocket"] is now the Standard. @priapo if you can't use the websockets you can set also "transports": ["polling"], then you will only get the failures for the long polling request which throws errors. I just tested by connecting directly without any proxy before NodeBB. The timeout disappears. So one failure source is that the timeout is higher than what is allowed by the proxy e.g. cloudflare. So an option to adjust the timeout would be great! The failure throwing which are left now are: GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766084670-12&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766094756-13&sid=U4674pe85Cyiv5fiAA0b 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766096635-23&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766106720-24&sid=8hFwdN-s5JA2NQQdAA0d 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766108697-34&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766118775-35&sid=N9btkX1jyZnnsbfPAA0f 400 (Bad Request) nodebb.min.js?9604615c:9 GET http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766120692-45&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request) nodebb.min.js?9604615c:9 POST http://localhost:4567/socket.io/?EIO=3&transport=polling&t=1419766130783-46&sid=HL2WrppvFQVLUZZcAA0h 400 (Bad Request)

This was a setting under admin>settings>sockets it has been moved to config.json. Old name was websocketAddress now its just address under the socket.io object. Sample config.json { "url":"yourforum.com", "socket.io": { "address": "", //or url to socket.io server "transports": ["websocket", "polling"] } } Relevant commit: https://github.com/NodeBB/NodeBB/commit/14e46a87a63f5e983a58a73109710027297924f3 The reason is if you put a invalid value here sockets will not connect and since the admin page uses sockets to save settings you can't change it back.

@baris I started working on a more SEO friendly theme/plugin. I hoped I could keep all the changes within a lavender derived theme, but I cannot. Some changes will be in the core. FOr example, server side rendered pagination. I am looking for some advice on how to coordinate making changes in a theme and core nodebb?

I figured out my issue... MongoDB user I was using had a readWrite role, but I guess it needs the dbAdmin role as well. When I tried creating a new user in the nodebb admin area, then it would make things go wonky without the dbAdmin role and result in invalid csrf tokens.

Finally the pull request is open https://github.com/NodeBB/NodeBB/pull/2527. I'm out for today guys, hope you get everything. If not just ask, gn8.

@frissdiegurke Knowing what I know now, @julian post can be construed to contain all the information :). I would word it differently though as SSO is probably veyr widely used. And if so, then calling port optional is...well, still technically correct.

Sample adaption code: if( app && app.router ){ callback = middleware; middleware = app.middleware; controllers = app.controllers; app = app.app; }

If you have any plugins that use action:topic.save, action:topic.restore or action:topic.edit please read below on the changes coming in 0.6.0. If you have any questions about how to update to the new hooks please feel free to ask. The parameter passed to all three hooks has been changed from a topic id to a topicData object. plugins.fireHook('action:topic.save', topicData); plugins.fireHook('action:topic.restore', topicData); plugins.fireHook('action:topic.edit', topicData); topicData object contains at least the following data. { tid: 3, title: 'test topic', mainPid: 5 }

I correctly assumed (and this has been validated through actual plugin upgrades) that the latest hash in npm points to the most recently published version, and not the highest version. That is, given your plugin nodebb-plugin-example If v1.0.0 is compatible with v0.5.4 If v1.1.0 is compatible only with v0.6.0 The latter is published first A user typing npm install nodebb-plugin-example will receive v1.0.0 of the plugin, irrespective of what NodeBB version he/she is running, even though v1.1.0 is technically newer Now, special note: The NodeBB Package Manager doesn't do this. When the ACP calls nbbpm to request a suggested package, we query npm for the plugin data, and sort the versions before checking compatibility, so this issue is moot.

I'm unsure if I'm seeing a regression or an undocumented? change here. I'm currently getting: TypeError: undefined is not a function at /mnt/Extra/home/dbolack/Projects/nodebb-plugin-rscloudfiles/index.js:203:4 Which maps to: callback(null, { url: rsCloudFilesCDNSecure + '/' + image.name, name: image.name || '' }); Which is equivalent to the current imgur plugins bit: callback(null, { url: data.link.replace('http:', 'https:'), name: image.name || '' }); Any ideas?

@baris Thanks Baris, that showed the issue, was using // as the URI instead of https which was incorrect apparently. Plugin updated to 1.1.5 for 0.6.0 of NodeBB.

Updated with header.tpl changes, relevant thread https://community.nodebb.org/topic/3488/header-tpl-changes

I know I made a promise to have the 0.5.x branch last more than 2 releases, but we added more breaking changes again, and 0.5.0 hasn't even been released yet In any case, for those plugin developers who are interested: Notification pushed action hook (action:notification.pushed) incoming data has changed: From: An object containing the notification data To: This object -- {notification: notification, uids: uids}); As always, this list will be updated as new breaking changes are added. In the case of this list -- don't commit and publish your change to npm yet, as 0.6.0 has not launched. We recommend you maintain these changes in a separate branch until then.