@julian Maybe this could just be the first one of a series, this one about why forum are important, and then others about why NodeBB is a good choice. I agree with you on competition, those video should not compare NodeBB to current competitors but rather to how forum used to be.

@bogus "normal" users like us only see "This post is deleted!" but admins will see the post content, so it's ok.

Actual deleted post for reference https://community.nodebb.org/topic/4033/security-problem

@julian I think, yes, as this would have the same value than my own change.

See https://github.com/NodeBB/NodeBB/issues/2882#issuecomment-84054443

Ribesg created this issue in NodeBB/NodeBB

closed Template engine closing tags for no reason #2882

Opened issue https://github.com/NodeBB/NodeBB/issues/2882
This is very strange and should be fixed. If it comes from me doing something invalid, it should output some error or warning somewhere. Something has to be done, whatever the cause of this is.

Ribesg created this issue in NodeBB/NodeBB

closed Template engine closing tags for no reason #2882

Hi, I'm working on a theme extending Vanilla. See https://battle-realms.fr/.

I've got a problem where NodeBB generates something completely wrong on my hompage. Here's the associated template part:

          <div class="content-container">
            <img src="\{categories.children.posts.user.picture\}" class="pull-left img-circle" />
            <a href="{relative_path}/topic/\{categories.children.posts.topic.slug\}<!-- IF categories.children.posts.index -->/\{categories.children.posts.index}<!-- ENDIF categories.children.posts.index -->">
              <div>
                <div class="content">\{categories.children.posts.content\}</div>
                <div class="home-fade"></div>
              </div>
            </a>
          </div>

As you can see there's a div inside a a here.
Now the result:

<div class="content-container">
  <img src="https://secure.gravatar.com/avatar/e0f46640ee183127e536c55b660aafe3?size=256&amp;default=retro&amp;rating=pg" class="pull-left img-circle">
  <a href="/topic/5/téléchargements/2">
    </a><div><a href="/topic/5/téléchargements/2">
      </a><div class="content"><!-- SNIP --></div>
      <div class="home-fade"></div>
    </div>
</div>

A complete mess. The a is closed before the the div it's supposed to contain starts, it inserted another a in this div (wtf?) and multiple other ones in the content.
You can see how wrong it looks on my mainpage, second post of first category in second section.
Here's a screenshot:

My question is, wtf is NodeBB doing here? How can I fix this?

EDIT: Added some \ in the code snippets to prevent NodeBB from removing things in braces

Bumb, this single line of JS added is the onyl change I have to do to NodeBB's sources for my theme to work, would be nice if I could get rid of it!

@akumbhare the linked code is in master. You're certainly using the v0.6.x branch. I don't see the uid passed in the v0.6.x branch.

@hek I used redis-cli to remove everything which was not a category, a topic, a post, a user. I had less than 20 entries for each of those things so it wasn't too hard to do by hand, of course you could automate this using some script.
Then I installed the new NodeBB normally, using that cleaned Redis DB as this instance DB. It just didn't add default categories as some where already there, but it worked. I was able to login and all posts were there.

Of course you lose everything else, configuration, plugins, etc. But I think it's better. NodeBB is still a bit early to modify it too much. Plugins just started being versioned. The only thing really worth investing time in is theming, as long as you mainly do CSS and modify few templates.

I did that on a test separate instance of course (different redis instance on different port + nodebb instance clone running on different port).