Posts made by PitaJ

@scottalanmiller mind opening an issue detailing your specific problems?

I'm having a really hard time thinking of cases where a redirect isn't the best solution.

The only case I've seen that makes sense is when you want it accessible through TOR and clearnet.

Also, nobody has really detailed what still doesn't work when the socket.io origins are set up correctly.

FYI instructions for setting up origins are here: https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins

I will offer up one more solution:

Embedding your new url within a lightweight iframe wrapper on your old url.

Works fine here: https://community.nodebb.org/api/search/?term=we&in=titlesposts

Perhaps you don't have the search plugin enabled?

@mrb I don't see that being terribly difficult. Please open an issue on GitHub

No idea what's going on there but I recommend trying it after building in dev mode so you can see the original code responsible for the error:

./nodebb build --dev

Just trying to understand what exactly you're asking for here:

At least in infinite scroll mode, we already have the post position overlay. It shows up in the header bar for desktops and at the bottom of the screen on mobile devices. The difference with Discourse in that case is that we don't have datetime information and the position in different.

So are you asking that we add post datetime information, or that we add the post position overlay even when in pagination (not infinite scroll) mode?

@oplik0 oof those template docs are really outdated. I need to do some work to bring them up to date.

In the meantime, please refer to the Benchpress docs instead: https://github.com/benchpressjs/benchpressjs/blob/master/docs/readme.md

You should have the theme in it's own git repository, then pull and link that repository into node_modules when you deploy.

Use the post queue for guest posts

Selecting badges is done is the profile editor:

/me/edit

@crazycells this plugin is called "db search" because all it does it use the database's internal search functionality. That's why your first two requests are not possible to implement in this plugin.

Unfortunately other search plugins are difficult to set up since they require entirely new programs on your server.

Your third request is just entirely off topic, nothing really to do with the plugin. Personally I think the tagging system deserves a lot of help. I think removing the actual tag fields and instead just parsing post content could be a better system.

https://community.nodebb.org/topic/13388/faq-websockets-not-working-due-to-misconfigured-origins

There's no way to expose HTTPS without a reverse proxy. This was a conscious decision to keep a separation of concerns, reduce development overhead, because reverse proxies have better support, and because anyone running multiple instances will need one for load balancing anyways.

Nginx is quite easy to set up, and LetsEncrypt has very good support for it.

@VaasKahnGrim you can use a different reverse proxy but I don't believe NodeBB supports https.

I recommend you set up nginx as a reverse proxy with Let'sEncrypt for your TLS certificate, which is safer than using CF SSL protection.

Once you get that working you can experiment with different cloudflare options, since that seems to be your problem.

What is your cloudflare setup? Is it set up to add SSL/TLS to your site?

You have ports and stuff set up weirdly, what are you trying to do there?

• To tell nodebb what port to use, set "port": 80 in config.json
• The value of the URL field should be exactly what your browser shows when you access the site, including the protocol

So what setup are you trying to accomplish? Are you using a reverse proxy like nginx?

It's essentially the same code we use in core: https://github.com/NodeBB/NodeBB/blob/master/public/src/modules/helpers.js#L9

So I don't know why you'd encounter this undefined issue. I assume you've tried rebuilding and restarting. Maybe try wrapping all of that in $(document).ready(function () { ... }); ? Try $(window).load too

What exactly did you try?