I tinkered with settings. Disabling “Enable blocks in comments” allows me to comment again. I did have to do a hard refresh (<cntrl><F5> in most browsers), so if it still doesn’t work for you, try that.
Hoping to see a comment from someone soon so I’ll know it’s working!
Adding a quote so we can see the styling both in post and in comments.
This is not a comment.
Ceci n’est pas un commentaire.
Sounds like a good fix, Phil!
Hmmm… I can submit a comment, but now I can’t seem to BOLD or italicize today, whereas yesterday I had no trouble formatting text using a menu at the top of the comment input box.
Testing the BOLD formatting through b and /b markup tags. (Testing it again with double asterisks.)
Testing the italics formatting through i and /i markup tags. (Testing it again with underscores.)
J-L: I don’t think that’s from disabling Blocks; seems more like it’s related to the bug, since what I at least observe was that as soon as I’d start typing, a weird, empty bar would appear at the top of the text input box. And only the first letter of what I’d typed seemed to register. I deleted a one-letter comment from a frequent commenter (i.e., it wasn’t spam) who had probably done what I first did: typed a comment, didn’t see it, shrugged and hit the Comment button to see what it would do.
I’ve set a reminder for Monday to try re-enabling Blocks to see if the problem is fixed. Still baffled that it doesn’t seem to be pervasive, i.e., that the one or two other folks using WordPress aren’t complaining! Or maybe they can’t make comments on some blog about WordPress problems… (“Sure is quiet” “Yeah, too quiet” dept)
I have a feeling J-L likely is correct in linking the disabling of blocks in comments with the observed difficulty formatting via that floating bar tool. That would probably be a feature of using a Text Block, which now is not automatically invoked.
Edit: I initially called it a wysiwyg tool, but now as I think back it might be the kind of hybrid where the tool inserts the correctly paired start and stop tags for formatting, and you see them in your text, just as though you had manually typed th
This is a comment.
This is a bold comment, in theory.
This is an italicized comment, in theory.
Since that didn’t work, not trying to bold and italicize when I edit the comment.
When I do that when editing the comment, the appropriate fences do show up around the words.
But, since I’m one of the site editors, I don’t know whether this function is available to all.
It seems to be taking a comment. Based on the comment about effects I will also try bold and italics the old markdown way.
Let’s see.
Hey, for some reason I can log in normally now, instead of having to login repeatedly.
bold and italicize
This was achieved by using [strong]bold[/strong] and [em]italicize[/em] but with less than and greater than signs instead of the [brackets]
Clumsy, though.
J-L got it working with markdown – bold and italics (let’s see a) if I remember the right marks and b) if it works).
Hmmm. I don’t know if it worked because (after it asked for my password) I don’t see my comment. Well, that’s even less useful than having to log in to comment… Hopefully it will show up eventually.
bold and italics (markdown style – underscores and asterisks). I wrote a comment with this before; it made me log in; the comment didn’t appear. I wrote a comment (above) without markings and (after it made me log in again), the comment showed. Does it not like markdown? It worked for J-L.
No comment.
A separate tech issue, but perhaps originating from the same original background problem. The numbering of comments, and the improved look for blockquotes, have been lost.
This was reported, and we began discussing, in the middle of a regular CIDU co,mic content thread, so it was suggested we copy that to here and if continuation is warranted, continue it here.
Ed said:
Editor Phil said:
I added:
Ok , numbering is back.
For the record, in case we need to add it back again sometime, the line added in Additional CSS was
.comment,clear li {list-style:decimal !important}
(I hope that prints as is, not used as script!)
Blockquotes modified., both for post and comments. This may be a little more distinct than we really want, but it at least fixes the huge font size that the srtylesheet on its own give.
For the record, the current settings are:
blockquote {
max-width: 550px;
text-align: left;
margin: 20px;
padding: 20px;
font-family: Arial,Helvetica Neue,Helvetica,sans-serif;
font-size: 20px;
color: #428bca;
background: #ccc;
}
Carl Fink (9): That would be great!
I am beginning to think I like the idea that I sign in once a week – or again the next day if I did not finish the week’s comics – so I can avoid problems. :-)
Mitch did a bunch of spelunking last week to fix what I broke by tinkering. I’m not touchin’ it again! Seems to be working OK.
Wha? No, your work on the difficulty people were having with commenting did the trick, when it was needed. (The setting about whether comments can use editing blocks.)
It was a design flaw in WordPress that another attempted rescue — substituting another Theme — erased our custom Additional CSS, which is what “runs” the numbering of comments, and gives a reasonable appearance to blockquotes.
There were some advantages to the blocks and the formatting controls, but we got along before and it’s not a big deal without if it ends up that way.
I just had problems posting to the strips after this one. I would get a message that the post could not post. Post would go out after I cut each one down to minimum words (and I was not wordy with the original post attempts). I got a message similar to when the powers what be think it is too off color in the general world of posts – though they were definitely not in anyway able to be considered same. I am hoping that this post goes out. I am posting at 3:23 am 2/20/25 EST if that means anything.