It's localhost:4567 and I'm using a reverse proxy to point traffic from port 80 there. It's not an issue anywhere else in the site, it's only an issue with the "mentions".

I just noticed that "mentions" in the "Recent Posts" widget are pointing to the wrong destination.

They SHOULD be pointing to "site_base_url/user/id" but instead point to "config_base_host/user/id".

In the example I discovered, it's pointing to http://localhost:4567/user/jason-c when it should be pointing to http://forum.mysite.com/user/jason-c"

This is the only case I've found of this so far. Any ideas regarding this behaviour?

Thanks!

• I should mention that I'm using a reverse proxy to push localhost:4567 to forum.mysite.com on port 80. Everything works perfectly, but I suspect it's using the wrong variable to create the link in this case and is using the base config rather than the site's base URL as defined in my settings.

I first noticed this when I ran into issues with jquery not executing on the ACP, but now with a separate installation, on a totally different server, I'm seeing it again.

I can see clearly that jQuery or javascript isn't executing, but the browser console remains totally blank.

In the previous case, another user here was able to display the contents from his browser console, but mine stayed blank.

This time around, the lavender theme's masonry script isn't executing, but there's no output from my browser console. Thoughts?

NOTE

I am running this directly from an IP address without a FQDN. Could this be part of the issue?

UPDATE

I started up nodebb in dev mode and watched the terminal, but I'm not getting any errors or warning after the site loads. I'm totally stumped why masonry.js isn't loading. It's not even showing up in the console's resources, but there was no error thrown either in the client or the terminal.

Just noticed this, did a quick search on the forum and didn't find anything:

When using special characters in a category name, it gets HTML encoded, (Which is good), but when you attempt to make a second edit to the name of the category, it get HTML encoded a second time (because of the ampersand at the front).

Reproduce:

This is easily evident with the default "Comments & Feedback" category.

1. Edit the name of Comments & Feedback, but keep the ampersand.
2. Save the category
3. Edit the same category a second time.
4. You'll see the doubly encoded category name as &

Expected behaviour:

When editing the name of the category, it should show the fully decoded category name, and encode it when it's saved. At the moment, it displays the HTML encoded name, then encodes the name as if it wasn't already encoded.

You could also scrub the name first, but displaying the HTML decoded name seems like a safer bet to me.

Hope this helps!

J

@pichalite You're awesome man.

Very excited about nodebb and what it can do.

I look forward to becoming an active part of the community here.

Kudos to @psychobunny for all of the AWESOME plugins he's developed here too!

I have to say, I'm loving the active community here for NodeBB. Reminds me of when SMF was still pretty new.

Would it help if I forked the repository, made the fix and asked for a pull into the master?

Not sure about the order of operations expected here in the community.

Hmm... Weird. Why am I not seeing any of this in my browser's console?

I can confirm with the neutrino84 forked git that ./nodebb dev doesn't spit anything out in the terminal either.

'Tis a puzzlement.

DISCLAIMER: First post here, I discovered nodebb less than 24 hours ago and my node.js experience is fairly limited. If I'm missing something blatantly obvious, forgive the noob in me. All in all the forum software is brilliantly executed as far as I can see, and doesn't suffer from the same issues as Discourse concerning extensibility. Well played devs.

So, there doesn't appear to be a centralized topic for this particular plugin, so I thought I'd create a new topic.

Here's the issue: The category sections plugin (IMHO) is pretty core for forum functionality. I'd love to use the plugin but sadly it doesn't appear to be working with 1.x.x

I've already installed Lavendar as the base theme. I've attempted to use this fork of the main git as it was updated 15 days ago. Seeing as 1.x.x was released 16 days ago, you'd assume this would resolve the issue at hand... But it doesn't appear to.

I'm getting no in-browser js errors, and I'm just getting a generic The following plugins may not be compatible with your version of NodeBB. This may cause unintended behaviour or crashing. * nodebb-plugin-category-sections from the log.

It's really strange, since sections.js doesn't seem to be executing client-side at all. No errors, click and drag functionality is non-existent, and there's no event listener attached to the buttons despite them being declared via jQuery in sections.js.

category-sections.tpl IS loading in the ACP, but the "Add Section" button does nothing and there's no click and drag functionality.

Strangely, hitting "Save Sections" DOES have an effect as the homepage will go entirely blank when clicked (Assuming that no sections = no content on the homepage)

@psychobunny, I'm sure you're super busy with all the awesomeness happening here with nodebb, but perhaps you have some thoughts into your brainchild here?

As I've stated, I'm less than 24 hours into exploring nodebb and I'm at a complete loss as to what's occurring here to prevent ACP functionality. Thanks for any insights you all could provide here.

Few Notes

• I'm running a DO droplet, Ubuntu 14.04, there are no conflicting containers, app was installed via NPM, server is up to date and the application is running naked, no docker.
• There's not a FQDN attached to the instance of nodebb however. config.json is using the static IP of the VPS, and I'm running nodebb on port 4568