Posts made by PitaJ

I believe that is what the markdown plugin uses. Are there any specific features you're wondering about?

@Jenine-Liwanag so first, are you calling it server side or client side? Second, have you set the Access-Control-Allow-Origin header in the NodeBB ACP to allow access from your other site.

You're fighting with CORS: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS

What version did you upgrade from?

You want to use the request module server-side. Look it up

@zaasmi are you seeing any errors in the browser developer tools console?

In the Custom JavaScript section, you shouldn't have the <script> tags

@zaasmi same issue, as in it still tells you to upgrade when you start nodebb?

Try ./nodebb slog

@zaasmi did you try running ./nodebb upgrade like the error suggests?

@zaasmi have you checked if nodebb is running? ./nodebb log?

@Muhammad-Saqib not currently possible to run tests using NodeBB modules. The way this has to be done is having the NodeBB test run the tests of your plugin.

It's currently not supported, though. Please open an issue on GitHub requesting this feature.

Try clearing your cache or using a different browser. If that doesn't work, please share your nginx config.

@zaasmi try disabling cloudflare protection on your domain and see if you can access it directly

@zaasmi can you take screenshots instead of copying the text in here, please?

@zaasmi did it work?

@zaasmi your mongodb database is probably not running

@Tiktak you're entirely incorrect about that benchpress warning. It's a warning, not an error. I should make that more clear. It simply means that compiling templates will be slower, so ./nodebb build will take longer.

No. NodeBB chose a flat topic structure long ago and this is unlikely to change. The replies expanding list below a post is nothing more than a convenience.

Have you tried restarting? Rebuilding? Running with ./nodebb slog?

@Areeba-Asad the option was removed due to bad UX behavior.

@byAppeL look in your browser address bar. Are you accessing the site at http://foro.az-rp.com:4567? My guess is that the port (:4567) does not show up in your address bar, and you're accessing the site at one of the default ports. In that case, remove the :4567 from the url value in config.json.

I don't know how many times I'll have to say this, but the url value in config.json should be set to exactly the url at which you access your site. The protocol, domain, path, and port should all be identical to what you see in the address bar of your browser.