How can I print out a specific array entry in my template?

Moved Technical Support

Suggested Topics

  • 0 Votes
    2 Posts

    Ah, not really... topic subscriptions are considered (in my opinion) user private data, and that is not shared by default.

    You could instruct your users to adjust their settings if they are being notified about a specific topic too often:


  • 0 Votes
    3 Posts

    Solved by myself, this documentation could be a bit updated for easier implementation, for those who will the same problem, let me give necessary steps:

    Install the plugin Rebuild then restart NodeBB Add some custom fields You can edit them by going to edit profile and "Change Extra" To display them in user profile, in case if you're using Person theme, go to nodebb-theme-person -> templates -> account -> profile.tpl Paste the code wherever you want it do be visible <!-- IF customFields.length --> <div class="custom-fields"> <!-- BEGIN customFields --> <div class="custom-field-item"> <span class="field-label">{}</span> <span class="field-value">{customFields.value}</span> </div> <!-- END customFields --> </div> <!-- ENDIF customFields.length --> Rebuild then restart NodeBB
  • 0 Votes
    2 Posts

    Anyone please give little bit of clue. How a topic works in nodebb?

  • 0 Votes
    2 Posts

    Install nvm or n and then use one of those to install Node 6.

  • 0 Votes
    14 Posts

    @ron_jeremy said:

    I'm not 100% sure.

    I have "failed" to install NodeBB on a DigitalOcean Droplet about 25 times by now. Seriously, I'm not exaggerating. The people at DO must have wondered "wtf is this guy doing?" because I was creating and destroying Droplets non-stop for days.

    I think what made the difference for me this time was not installing redis or nodejs as per the official NodeBB install document. Instead, I only installed the Chris Lea files.

    I was so tired to trying different methods of installation I actually started keeping a log of what I was doing. I got it down to where only a few lines would change, and I am pretty sure this is what finally worked for me (remember, this is on a DO Droplet running Ubuntu 14.04 x64):

    add-apt-repository ppa:chris-lea/redis-server apt-get update apt-get install redis-server apt-get update apt-get install git apt-get install build-essential apt-get install imagemagick apt-get install python-software-properties add-apt-repository ppa:chris-lea/node.js apt-get update && apt-get dist-upgrade mkdir nodebb git clone git:// nodebb cd nodebb npm install node app --setup
    - only modify first line where I enter my server's address http://your.server.ip.address (without the port) and hit 'Enter' for all other options node app
    - Now you can go to http://your.server.ip.address:4567 to see the forum

    I have try this but when i go to npm install
    i get this :
    E: Unable to correct problems, you have held broken packages.

    Got fixed with :

    apt-get remove --purge nodejs npm
    curl -sL | sudo -E bash -
    apt-get install nodejs