• This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn more.

Cursor Arrow keys problem when adding comment

OwenJames

Active member
#1
Hi

I searched, but could not find anything about this problem, so I am making a new thread. Sorry if it has been posted before, but I could not locate anything.

Right, here is the problem.

When a user disables "Use the rich text editor to create and edit messages" in Browsing Preferences and in doing so sets the default comment input to BBCode, the up and down cursor keys stop working. This only occurs in the comment box directly on the forum page, and not in any other instances of the comment box. When "Use the rich text editor to create and edit messages" is re-enabled, the problem goes away.

Anyone know how to fix this, as it is annoying some of my members!

Thanks in advance.
 

Mike

XenForo developer
Staff member
#2
I can't reproduce this and I don't see how it's really possible (without some very dodgy JS). It's just a regular <textarea>.
 

OwenJames

Active member
#3
Right, yeah, I have tried to replicate it right here, and I can't do it either. Weird. Obviously you won't know what I have been doing to my forum to cause this, but would it be possible something I have added (an add-on, or whatever) is causing this?

Thanks for the reply.
 

Brogan

XenForo moderator
Staff member
#4
Disable all add-ons and try again.

If you have added any additional JS to the templates, remove that too.
 

OwenJames

Active member
#5
Thanks for the advice. I will work through, disabling the addons systematically and see which one is possibly the culprit.

Great, quick responses on this forum. Great stuff, thanks!
 

Brogan

XenForo moderator
Staff member
#6
If you want to disable them all quickly, edit the library/config.php file and add the following:
PHP:
$config['enableListeners'] = false;
 

OwenJames

Active member
#7
OK I will give that a go quickly. If that does fix it, is there a way to then go through the addons I have, turning them back on one by one to see which one is the offending member?
 

OwenJames

Active member
#9
OK, your suggestion did fix the issue, so I will not go through and disable things one by one to find the problem addon. Great help, thank you!