@baris Correct, that admin setting has been removed.
Re: topic.create... looks to be a UI issue then. If "Topic Create" is checked, automatically check "Topic Post" as well in the modal.
@baris Correct, that admin setting has been removed.
Re: topic.create... looks to be a UI issue then. If "Topic Create" is checked, automatically check "Topic Post" as well in the modal.
@frissdiegurke Mmm, noticed just now that this plugin interferes with page searching. I tried searching "HAR" and the page reloaded
Any chance it can detect when the "find in page" dialog is open?
Actually, the markdown plugin did use highlightjs before, and I switched to pygments because highlightjs would choke on very large snippets of code (I believe it was a Varnish script)...
If you dig around in the plugin commit history, you can see the code for highlightjs, possibly
I don't know enough about nginx internals to be confident enough to write a single server block to do both of those, but try this:
server {
listen 80;
server_name www.35hz.co.uk;
return 302 https://35hz.co.uk$request_uri;
}
And possible for the /forum
redirect...
location ^~ /forum(.*) {
return 302 $scheme://$http_host/$1$is_args$query_string;
}
YMMV?
When it starts working, switch those 302s to 301s. Then Google will know to transfer requests from one to the other.
@Giorgio-Chiodi said:
@psychobunny you mean us? not really, still witnessing weird behaviour on https via mobile connection from mobile devices (smartphones + tablets)
Yeah, it'd be either your browser (stock browser, or chrome?) or your ISP (sometimes websockets not established on 3G). The new socket.io version is not implemented in NodeBB yet...
The scripts/inject message is a little worrisome...
When you require the composer like you've shown in your code, it should automatically load the composer asset. What is the problem? Any js errors when that button is clicked?
@nik Yes, that looks to be the problem then, set it to false
and give it a whirl. (If you're using nginx, use_port
should be false, in 99.99% of cases)
@nik Your config.json
file (If this is the source of the problem, then perhaps this is a candidate for inclusion into the NodeBB FAQ...)
@Giorgio-Chiodi likely, yes.
Is your use_port
set to false? If so, NodeBB will trust referrer IP as passed in via nginx. Otherwise, it will assume 127.0.0.1, as that is really where the requests are coming from
@Giorgio-Chiodi at the moment, the Pushbullet API is not mature enough to allow pushes to NodeBB... But it will be, soon!
However, this brings up the problem of which category to push to...
The hack has finally come around to bite me in the ass
Thanks @a_5mith
Given that I recently added Push Notification support via my Pushbullet plugin, I'd say Jabber/XMPP support could also be done via a plugin as well
Perfect for finding bugs in NodeBB's codebase.
Sounds like it's time unveil our new product, NodeCart*.
* No, NodeCart is not real.
@dylenbrivera We're in talks to get something rolled out soon. Don't worry!
@Giorgio-Chiodi Please have the console open when you trigger this bug... then, go to the network tab, right click, save as HAR.
Then send me the HAR file
That's correct @Giorgio-Chiodi, to have NodeBB load a little bit faster, some assets (like the composer) are not loaded until they are used the first time. Problem?
Earlier, we were running into issues with certain plugins crashing NodeBB (since fixed)... whenever NodeBB crashes, the loader brings it right back up again, but there's a delay while the javascript is being compiled.
@dylenbrivera This fell off the front-page for me. Ask away, we'll try to help