It would be great if somebody who knows how to do that could upgrade the plugin to also support URLs with x.com instead of twitter.com as domain name.
Klaus6
Posts
-
[nodebb-plugin-twitter] Twitter tweet embed plugin -
[nodebb-plugin-ns-embed] NS EmbedDid anyone make it work for Threads?
-
[nodebb-plugin-ns-embed] NS EmbedIs this plugin compatible with NodeBB 2.0.0?
I can't display the website to display the plugin's configuration options anymore. Only an empty page shows up. The log shows the warning
warn: [deprecation] The `/plugins` shorthand prefix is deprecated, prefix with `/assets/plugins` instead (path: /nodebb-plugin-embed/css/acp.css)
-
[nodebb-plugin-ns-spoiler] NS SpoilerThanks a ton, that looks interesting.
I wonder, though: Shouldn't it be possible to just strip the spoiler content in the preview? That is, filter the content and remove the spoiler content for the preview? I don't know how NodeBB is programmed - maybe the template language supports some kind of transformation/filtering?
-
[nodebb-plugin-ns-spoiler] NS Spoiler@crazycells On the main page with the listing of the posts, there is a preview that reveals the spoiler content.
For instance, I put a spoiler with the text "Spoiler content" into a post, and on the post listing page the text is revealed.
-
[nodebb-plugin-ns-spoiler] NS SpoilerThanks for the suggestion @crazycells ! That plugin works indeed (I used this version which seems to be more up to date). The only problem my users have with that plugin is that the spoiler content is displayed in the post preview. Any suggestions on how to block spoiler content in post previews?
-
[nodebb-plugin-ns-spoiler] NS SpoilerIs there really no way to get a working spoiler plugin for the current version of NodeBB? All alternatives seem to be even more outdated than this one.
-
[nodebb-plugin-ns-spoiler] NS SpoilerThis plugin isn't working anymore on my forum since a couple of months.
I'm on version 8.0.0 of the plugin, Nodebb version 1.19.1
The problem is that the spoilered text isn't loading when pressing on the spoiler header.
When turning on the JavaScript debugger, I get an
Error has occurred, error: [[error:no-privileges]]
in
spoiler.js:50
.The relevant JavaScript function that triggers the error is this one:
function toggle($button) { var $spoiler = $button.parents(elements.MAIN), $content = $spoiler.find(elements.CONTENT), open = $spoiler.attr('data-open') === 'true', postId = parseInt($spoiler.attr('data-pid')), index = parseInt($spoiler.attr('data-index')), icon = $button.find('i'); $spoiler.attr('data-open', !open); if (!open) { icon.removeClass(classes.OPEN_EYE).addClass(classes.CLOSE_EYE); } else { icon.removeClass(classes.CLOSE_EYE).addClass(classes.OPEN_EYE); } // Check if content is empty if ($content.html().length === 0) { socket.emit( 'plugins.ns-spoiler.getSpoilerContent', {index: index, postId: postId}, function (error, content) { if (error) { return console.error('Error has occurred, error: %s', error.message); } $content.html(content); } ); } }
The
socket.emit
call always yields the "no privilege" error.Any ideas?
-
Invalid CSRF Token, againI'm using the latest NodeBB v1.16 via Cloudron.
An error that must be related to one of the more recent NodeBB updates is that forum users report strange errors where they only get the single word "Error" in some situations when they use the forum.
These situations seem to coincide with log entries in the server log that look like this:
Dec 22 19:42:18 2020-12-22T18:42:18.963Z [4567/289] - error: /api/v3/topics/6185
Dec 22 19:42:18 invalid csrf tokenI have seen that "Invalid csrf token" has been discussed in this forum before, but those discussions were many years ago. Could this strange behavior be related to this recent addition to NodeBB, maybe? Any other idea?