https://github.com/NodeBB-Community/nodebb-plugin-spoilers
I will update it for 4.x but it should still work if you install from the CLI
A place to talk about whatever you want
This is a forum category containing topical discussion. You can start new discussions by mentioning this category.
https://github.com/NodeBB-Community/nodebb-plugin-spoilers
I will update it for 4.x but it should still work if you install from the CLI
Published 1.0.1 which is compatible with 4.x and 3.x
Now that it's upgraded it should show up in the admin page.
Is the word Spoiler hardcoded? How to change if I want it to say Answer, for example?
Also if my spoiler has 2 lines how to put page break in E.g. >! Line1 Line2
To come out Line1 Line2
You can change the Spoiler
text to something else.
In Federated messages, the !> doesnt work even between nodebb instances that have the plugin.
Not a big issue but its actually interesting that it doesnt work.
For example here a mastodon site sends that code in a post to a nobebb site that has spoilers installed,
when it displays the post why isnt the Functionality triggered?
Not sure why it doesn't trigger for fediverse posts. At the very least it should have turned into a blockquote. @julian will have to take a look at the fedi issue.
@eeeee Mastodon posts are interpreted as-is, so that symbol combination is meaningless for Mastodon, and that is reflected in NodeBB
Will have to test between NodeBB
@julian yes I never expected it so function on Mastodon, of course not. but when putting that symbol combination into Mastodon post, and sending it to nodebb you would think it would trigger nodebb side. Actally its hard to understand how it doesnt activate spoiler on nodebb side, given its the same 2 characters. Im more perplexed, than bothered, that it doesnt!
@eeeee when Mastodon posts enter NodeBB we save the html in the database as-is (and sanitize it on output).
This is different from NodeBB internally which saves markdown into the database.
The spoiler plugin might not be matching the symbols because from remote communities the line begins with <p>>! spoiler
instead of just with >!
itself.