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