space bar is not working

Permalink
Hei there!
I put a side into concrete5 5.7.
Everything works fine. The only thing is, I am not able to put space between the words.
Someone knows the reason for this?

 
WillemAnchor replied on at Permalink Reply
WillemAnchor
That's strange. Maybe you can add a little info:

- What version of concrete5 do you use
- what add-ons have you installed
- do you use internationilization, and what language do you use
WillemAnchor replied on at Permalink Reply
WillemAnchor
Or do you mean space between lines ?
You can add <br> tags in the html view.
chrisizang1 replied on at Permalink Reply
No its the space between
The words.
Nur maybe Its a good idea to deinstall
some Addons...
My site language is german.
kspitzley replied on at Permalink Reply
kspitzley
We are also experiencing this issue in both Firefox and Chrome in the basic content block. Basically what happens is you press the spacebar and it doesn't register. It only occurs in the content block in the redactor editor - it works fine in redactor's html view. it happens intermittently - sometimes it works fine, sometimes we are forced into html mode.

This is occurring in 5.7.5.6, and it's never occured for me i other versions of concrete 5.7.

Also, here are the packages we have installed: Spacer (0.9.3), Vivid Simple Accordion (1.0.1), Zoomer (1.0.1).
kspitzley replied on at Permalink Reply
kspitzley
I found this potential solution in a forum post:https://www.concrete5.org/community/forums/5-7-discussion/the-curren...

"I ran into a weird issue with Redactor, just thought I'd document this here:
I loaded Google fonts off their link, and in Chrome (not FF, Safari), whenever I'd press spacebar whilst entering text, the spacebar would not advance visually in the editor, but if I typed the next letter, the space would appear. This was leading to inadvertent typing of double spaces, because if I double spaced, a single space would appear visually. However, this was inserting a lot of entities in the HTML. Yet, those would not render in Chrome! It turned out to be something with the Google-served webfont. I downloaded the font, and processed into a typekit at FontSquirrel, then loaded it via @font-face, and it all works normally now."

We are using Google fonts so this might be the problem for us.
WillemAnchor replied on at Permalink Reply
WillemAnchor
Ah, hope you solve it. Maybe you can post if it worked for future reference.