Community

@sweetp easy to do with custom css

yes, its working!
thank you!

@julian said in Good VPS hosting recommendations wanted:

if you have a tech guy who recommended OVH, why don't you use that resource for your tech support needs

He is. Me 😄

I like button menu 😉
Test that ASAP

@julian ok, I have a self-hosted version working in principle, so all I need now is the modified plugin, which I'm happy to test 🙂

here is mine

This settings for widgets not work on /category and /recent page

Set the topic IDs you want to display this widget on (separated by commas) Set the category IDs you want to display this widget on (separated by commas)

Cat Typing GIF

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.

I’m running NodeBB v3 + Harmony

@Gliding9426 Yes, they should... when you install a plugin via NodeBB, the package.json file is updated, and the plugin is downloaded to the node_modules/ folder, along with its dependencies. Both of those are on-disk, which is ephemeral on a Docker instance.

If package.json is updated to include the plugin, then when ./nodebb upgrade -i (or npm i, etc.) is run, the plugin will be installed alongside, automatically.

You can use filter:config.get to add a new variable. That value becomes available in all templates as {config.myVariable}