Oh, i found my problem. That was an incorrect testing procedure. Did not enable the vpn on the second tab, so system somehow detects it and rejected the ref. Nice. For anybody testing the ref system and has faced the same problem: check the node logs for a string "Error: Hijack attempt blocked", if it is check if you are using the same session (I suppose?) on a second tab.
[nodebb-plugin-spoilers] Spoiler text in posts
esiao last edited by
@psychobunny I should have a plugin conflict because it doensn't seems to be solved on my board (plugin updated)
zay last edited by zay
i build this plugin with my version
*its not same or copy your plugin i just see how it work for notbb v.0.6
thanks for inspiration
i build with function toggle down and up
Does the plugin still work in a recent nodebb installation?
If yes, do multiline spoilers generally work?
I am getting exclamation marks at the start of a line after an empty line has been used in the spoiler text. It seems that the parsing somehow won't work correctly.
@phl if I understood what you were saying, that's typically how markdown works; a blank line will stop rendering the text in the same block.
> here's a quote With a new line After a broken line
here's a quote
With a new line
After a broken line
Your new line will need a spoiler tag too to be included.
Well that's of course what I tried. Every possible combination of spoiler tags I could imagine (At the start of text blocks, in every line, in a new line, ...)
> citation more citation > > even more citation
renders as expected,
>! Spoiler more Spoiler >! >! even more Spoiler
produces visible exclamation marks in the output at lines three and four.
Arc last edited by
Is this unavailable for newer NodeBB versions?
Arc last edited by
@AOKP Yup, ended up going with it. The change in syntax is irritating though.