We're experiencing spam accounts relatively regularly and I'm looking for advice on reducing the workload.

I searched this forum for the word "spam" but most of the posts are from a long time ago. So hopefully it is useful to all to open this discussion again.

First, we have enabled the "Post Queue" feature so that our moderator must review the posts of new users. This allows us to catch the spam accounts and posts, but when these spam attacks come (usually in waves) it eats up a fair amount of the moderator's time – time when he should be helping our users.

The Spam-Be-Gone plugin is installed, but not all options are active. Here is the status of each of the features:

• Askimet: Off (paid option only)
• Project Honeypot: On
• Google Re-Captcha: On
• Stop Forum Spam: Off (free)
• hCaptcha: Off (free and paid options)

Of those that are enabled, Re-Captcha doesn't seem to be doing much to stop registrations. Maybe they are being done manually, or the AI behind these bots is simply too good for that to work?

Of the three options we don't use (Askimet, Stop Forum Spam and hCaptcha), I'd really like to hear about the experience of others regarding their effectiveness

Given that Stop Forum Spam is free, I guess we should enable that one. Do others here agree?

Several online reviews speak highly of Askimet, and I'm very much willing to pay for this if it really does the job.

Thanks in advance for sharing your knowledge and wisdom on this topic.

Best Wishes,
Mark

On our version of NodeBB (v1.17.2) which uses the Redactor plugin for text entry, clicking the Redactor's Video button to embed a video, the dialog that opens suggests:

Video Embed Code or YouTube/Vimeo Link

But if you actually enter the embed code from Vimeo, it messes up the post to the point where the user can no longer edit it.

On the other hand, a YouTube or Vimeo link by itself works fine.

I know Redactor is no longer supported, but do you have any idea how we could fix this issue?

Best Wishes,
Mark

On our site at https://community.troikatronix.com we continue to use Redactor with NodeBB 1.17.2

For a logged in user, if you:

1. Go to the forum
2. Click a topic to open it
3. Hit the blue "Reply" button

Redactor opens fine and you can type your reply, etc.

But if you

1. Go to the forum
2. Right click a topic and say "open in new tab" – which causes the topic to open in a new tab (obviously)
3. Hit "Reply"

There is no response.

This happens on Safari, Chrome and Firefox.

In both cases the button;s HREF is something like

https://community.troikatronix.com/compose?tid=XXXX&title=Post Title

Why does this work when you go into the topic directly and not work when you open it in a new tab?

Best Wishes,
Mark

@julian

Can you offer any feedback to the post above from our tech person?

Thanks in Advance,
Mark

P.S. One other question: is it possible for a single user to choose to use the standard markup editor instead of Redactor/Quill via some kind of setting? It doesn't seem to be an option, but I wanted to make sure that I'm not missing something.

@julian said in Bugs in Quill (NodeBB 1.16.2):

Redactor hasn't been disabled, per se, we just no longer actively develop on it.

Our tech found that it was not possible. I have asked him to post here to explain why it didn't work.

@julian said in Bugs in Quill (NodeBB 1.16.2):

Quill is probably the better path moving forward. How are you trying to embed youtube videos, via a plugin?

Well, in redactor this button that allowed you to specify a movie URL.

using this dialog:

Quill does not seem to offer the same option. So I'm just dropping the URL into Quill. The link works. But it doesn't embed.

(Note: pre NodeBB 1.16.2 posts that had embedded video still show them as embedded; switching to Quill did not change the behavior of these older posts.)

Best Wishes,
Mark

Dear All,

We are in the process of upgrading to NodeBB 1.16.2. It seems that, in this version, Redactor has been disabled and that the only option for a WYSIWYG editor is Quill.

We have immediately discovered two issues in Quill, which are mentioned in a post from November 2020:

1. If you select some text in another user's post and hit the reply button, Quill does not enter the selected text as a quote as seen below:

@blahblahblah Said:

Quoted Text here with a bar to the left

2. You can no longer embed a YouTube video.

Will either of these get fixed any time soon? It is discouraging when an update offers them reduced functionality.

Thanks in advance for whatever insights any of you might have.

Best Wishes,
Mark

We have a self-hosted version of NodeBB 1.15.0. We use Redactor when users post, because our core audience are not the kind of folks who generally would "get" using markup.

Over the last several weeks (and this does seem to have come up long after we upgraded to 1.15.0) users have been complaining that they cannot reply, as you can see in this thread on our forum

Is this a known bug in 1.15.0? Does the latest version address this issue?

Thanks in Advance for Any Info,
Mark

Howdy.

We're self-hosting NodeBB v1.15.0. (We upgraded to that version a few months ago.) I've noticed that when replying to posts and typing @... where I enter a few letters of the users handle, it no longer offers a popup menu to let you choose the correct person.

Was that feature removed from NodeBB, or did it stop working?

If it's a bug, will it come back?

Or could it be something about our configuration?

Thanks in advance for the help.

Best Wishes,
Mark

@mark-coniglio

bump? has anyone taken note of this?

Workaround/clue to the problem: If you click the "file upload" button and enter text where it says "name (optional)" then the link will appear.

Dear @julian

I created a fresh trial NodeBB on NodeBB.org, installed v1.8.1.

When I tried uploading files non-picture files with the normal composer, everything worked fine.

When I tried doing it with Redactor enabled, it has the same behavior as our site. The upload progress bar at the top temporarily appears, but no upload appears in Redactor.

So this issue does not seem to be specific to our site.

Best Wishes,
Mark

In NodeBB 1.8.2 we can no longer upload any file types except pictures.

Please note that we are using the Redactor Composer for entering text.

We have the following file types enabled:

Uploading jpg and png files work fine. But when I try .zip, .izz, .pdf the upload indicator at the top of the window briefly shows up, but no file is deposited there.

In previous versions of NodeBB, uploading these kinds of files worked fine with Redactor.

I tried deleting all the file types, saving the settings, and entering them again, but to no avail.

Does anyone have ideas on this for me?

Is there some way to temporary disable Redactor (without uninstalling it) so I can try with the normal composer?

@julian - could you possibly try uploading files with Redactor to see if you see the problem also?

Best Wishes,
Mark

@julian

We did that and it worked. Thanks a million.

Best Wishes,
Mark

Is there any news on this issue? We'd really like to have a fix.

Best Wishes,
Mark

@pitaj said in [1.8.1] Serious Bug: Can't Reply in Numerous Browsers and OS'es:

Have you tried running ./nodebb build and restarting?

Yes, we tried that. We also installed the v1.8.2 update and it did not solve the problem.

We've just upgraded to v1.8.1 and the users on my forum are experiencing numerous problems. One of them seems to happen on numerous browsers and operating systems.

I have filed a detailed bug report on GitHub, but the issue boils down to this: the position of the toolbar and/or editor when hitting reply is dependent on the length of the thread. If you reply to the first post, things will work OK:

If you reply to the second post, you'll note that the editor window is now starting much higher on the page:

Finally, if you reply to the last post on a long thread you'll see the following and the editor will be unusable. (Or at least seem to be... when you type, you see nothing, but maybe the text is so far above the viewable area you can't see it.)

As you can see in the user discussion here:

This is affecting a number of users on numerous browsers. Clearing the cache does not improve the issue.

Best Wishes,
Mark

@julian said in Redactor 3.0.3 Bugs in NodeBB 1.6.1:

Will reach out and see if I can snag a download

Any news on this?

If there's anything I can do to help with this process, please let me know. It's a bummer to have gone from something that was working perfectly to something that has several annoying bugs.

Best Wishes,
Mark

@julian said in Redactor 3.0.3 Bugs in NodeBB 1.6.1:

I can't reproduce the bold/italic bug

I didn't specify my platform or browser. I'm working with Mac OS with Safari and Chrome.

I just created a Fresh NodeBB forum at https://nodebb.org to test this issue so that I can ensure it's not something specific to our site. I'll had to refine my reproduce case for Bug #1, but now it seems totally reproducible for both Safari and Chrome. (See edit to Bug #1 in my original post.)

Bugs 2 + 3 were immediately reproducible on Safari, but Bug 3 did not happen on Chrome.

So the summary is:

Mac OS Desktop: Safari = all three bugs happen
Mac OS Desktop: Google Chrome = bugs 1 + 2 happen

Finally, the same tests performed on a Redactor test page

Redactor Test Page

did not exhibit the bugs.

I've emailed the Redactor team to see if they can do anything about this as well. (Note that there was no bug with using the command keys to Bold an item... just when italicizing.)

Best Wishes,
Mark

@julian said in Redactor 3.0.3 Bugs in NodeBB 1.6.1:

Are you on 3.0.3 of redactor plugin

Yes, we're on NodeBB 1.6.1 and Redactor 3.0.3. It's interesting that you can't repro this. Could there be something about our setup that is causing the bug? Is there a NodeBB site running 1.6.1 where I could try the Redactor setup myself to try to repro it?

Best Wishes,
Mark