@PitaJ said in Nodebb build stuck: Try adding "series": true in your config.json thanks! I was struggling what to do, I have only 1GB ram machine, now I can finally make builds there. But I had to add also swap file.. https://linuxize.com/post/how-to-add-swap-space-on-ubuntu-18-04/#before-you-begin

@MintertalkOrg If you give us a shout at [email protected], we can send over a quote

there is 1 benefit too in having the topic ID in the URL. but facebook has them too but urban dictionary URLs are SEO friendly (no IDs in URL) and it has massive traffic.

@julian said in About GDPR email sending: It is safe to assume that if a user explicitly set their user digest setting, then they can consider having opted into the email. For those users that have not set any setting explicitly, you can change the default in the ACP, and that value will propagate to those users as well. So you'll probably want to disable the email digest for default users. I will try that for now Problem with the new law is that users need to re-confirm his preferences and if they dont confirm it should be disabled

@pitaj said in Plugin activation depending on system: hmmm... well ideally plugins and core would only load their assets when necessary. For instance, in core, we only load jQuery UI if we have some jQuery UI thing. There are many other places where we could pull more code out to be on-demand. you mean ideally but not on reality, right? my idea was for example to enable plugins like... -people viewing this topic, reactions, polls, etc only on desktop

restarted a few times again nodebb working now thanks

Uppppppp

@julian said in About timestamp changes: I've adjusted the milestone setting for that issue accordingly. It'll be in the version to-be-released. Thanks

@pichalite said in Category doesnt exist on 1.2.1: @exodo @torn2 v1.x.x branch is now updated with working composer. Pull again and run upgrade. Hey I'm having the same problem. I'm up to date on branch v1.x.x but no luck on the error. Also composer is on 4.2.13 for my site.

I think it is best to start room names as "" and display the usernames, if the owner changes the room name then we display that.

Does the browser you use on that phone support websockets?

@exodo I would imagine it's something like node --prof app.js

@exodo said in [ nodebb-plugin-embed-combo ] Embed Combo for Nodebb: @torn2 said in [ nodebb-plugin-embed-combo ] Embed Combo for Nodebb: Why not just self host Iframely? i was testing iframley and it doenst have spotify. vocaroo and others so wont fit for me ok thank you will try adding some more embeds next weeks Are you trying the fee version out? Not sure about those two as we've never used them in our forum. LiveLeak is another that does not embed if you use https. Works well enough for us instead of having to dig through multiple plugins.

@PitaJ said in Nested quotes: @alberto__segura Why not remove it? Because it's an intrinsic part of markdown that requires work to remove. we only need a simple regex, we did it in older versions with a custom composer (https://github.com/exo-do/nodebb-plugin-composer-exodo/commit/da2351cf94baf1c8580af4c760b1ff19785e3198), but we cannot maintain our own custom composer. It should be part of default NodeBB composer.

solved, the removed users were still present on username:uid the id 0 and global guest comes from trying to search non existant users on user:uid

Sorry for resurrecting this very old topic. This seems the very thing I want with NodeBB and wondering if these will work with the current version of NodeBB. Thanks.

@baris said in Tracking composer not opening: This is likely caused by https://github.com/NodeBB/NodeBB/issues/4978 I sent a PR to the ns-spoiler plugin that should fix the issue for now. all right , check this please https://github.com/NodeBB/NodeBB/issues/4964#issuecomment-242585842

@julian Yep that's correct. It wasn't showing at the moment @exodo 's wrote, but a while after that it showed up. Thanks @julian

Hi @BuZz For sendmail, on our own servers, we run the following commands: echo "PATH=/usr/sbin:$PATH" >> ~/.profile and echo "127.0.0.1 localhost localhost.localdomain $INSTANCE_ID" >> /etc/hosts You can see the reasoning behind the latter here: https://brianhogg.com/how-to-fix-slow-sendmail-on-a-digital-ocean-ubuntu-droplet/