When I quote a post & try to type something in response, the spacebar won't work. Works fine when I create my own post, just not for quotes.
When I quote a post & try to type something in response, the spacebar won't work. Works fine when I create my own post, just not for quotes.
I'm using Chrome & yes, XV.
I can reproduce it in the WYSIWYG editor, but not the plaintext editor. Interestingly, when I switch to the plaintext editor and back again, it works again.
Don't have time to figure out how to fix it right now, sorry. Maybe during the weekend.
I had this happen to me yesterday. I'm on simplified light, only when quoting.
I'mhavingthisproblemtoo.I'vefoundthebestwaytofixistorefreshthepage.
Usingthethistheme:
I will just chip in to say I get this as well. Chrome, using the Old Skool (ugh, school with a 'k') skin. It's fine when I'm not quoting, but when I quote, I cannot use spaces once I've hit enter twice to write below the quote. Interestingly, not pressing space and writing immediately after the quote allows me to use spaces. It's... finicky, for the moment, but serviceable.
As Rantz seems to have worked out, the problem is the WYSIWYG editor (unless some of you aren't using this one, then we have a whole new problem) - until we get this sorted, a temp fix would be switching to the simple editor via the settings page. Or power through using the little fixes you've all worked out for yourselves!
I'll see if we can get someone to look into this.
I stumbled upon another weird workaround - if you just type a line break and then move back up a line (leaving the line break below) you can use spaces again. Weirdest bug.
Still haven't had the time/energy to really dig into this.
Did some googling and found this: http://www.vbulletin.com/forum/forum...rking-on-reply
It seems there won't be any fix for this issue from their end unless they stumble upon some quick solution. There may possibly be a fix in Chrome at some point if it is indeed a browser bug. Until then, probably not much we can do aside from use workarounds and wait, or switch to another forum software (which I don't think is in the cards right now).
In other news, seems vBulletin's support team is keeping up their tradition of acting like petulant children - though some of the other posters there are too, to be fair. Still, it baffles me that any company handles customer service like that.