Are there any doc of the nodebb's API?

General Discussion

Suggested Topics

  • 2 Votes
    3 Posts

    As mentioned prior, you can use the privileges to restrict access to the topic.

    but I'm not entirely sure how this works.

    If a spider is detected (not a 100% guarantee, by the way), then they are either allowed or denied access to the topic based on how your privileges are set up.

    For example, if you grant spiders "access-topic" privilege, but do not grant "registered-users" that privilege, then web crawlers will be able to access the topic and crawl it, but regular users will not. The groups are mutually exclusive.

    On one hand, I'm thinking that allowing spiders to access all content could potentially boost my site's search engine rankings. On the other hand, I'd like to keep one or two paragraphs hidden from spiders, so that only verified users can view them.

    That's harder, you'd want to use a custom plugin to restrict the post content if a spider is detected. Doable, just not available right here right now.

    There are plugin hooks that are fired when a post is rendered, and you can probably check caller.uid or req.isSpider (depending on what is passed in) to see whether it is a spider or not. A uid of -1 is a spider as determined by the library we use.

  • 0 Votes
    8 Posts

    @pichalite Hi, I haven't heard back so I'm following up.

  • 0 Votes
    1 Posts

    I just did an install of NodeBB 0.8.2 and it installed nodebb-plugin-emailer-mandrill 0.3.1 with it which is only compatible with NodeBB 0.9.^. In addition to the declared version problem I was also getting a related error on NodeBB startup until I removed the mandrill plugin.

    I worked around this problem by removing mandrill and then installing it like this:

    npm install [email protected]

    I poked around to see how nodebb installs nodebb-plugin-emailer-mandrill and it appears that this plugin is installed in a special way? It is not mentioned in the package.json requirements for nodebb.

  • 1 Votes
    4 Posts

    Oh probably 301 is better, since it teaches Google to use the new one instead, but remember what happened last time we tried a 301? ended up not ranking for months 😄

  • Can't set up NodeBB

    General Discussion
    0 Votes
    19 Posts

    @lukelarris I run into the same issue in 14.04 server too. You need to install nodejs-legacy through apt and it's running well then 🙂