The feedback from the previous post is pretty clearly on the side of requiring registration. However, there was also a lot of love for Disqus. So here's a second question: Should I install Disqus or stick with the stock WordPress commenting system?
UPDATE: For now, the consensus seems to be FOR registration but SPLIT on Disqus. So I've turned on registration but I'm keeping the stock WordPress comments for now. We'll see how it goes.
UPDATE 2: As for the orange text in the comment box, I have no idea what's causing that. Like everything related to WordPress, there's an easy fix for this but only if you know which CSS variable controls it. There's no simple way of looking this up (that I know of) and I finally got sick of chasing around trying to figure it out for yet another minor appearance change. If anyone happens to know, tell me in comments and I'll change it.
UPDATE 3: Let me be clear: If you know which variable to change, let me know. If you just have a guess, please don't bother. I'm already pretty familiar with the WordPress guessing game.
Disqus gives the commenter better editing controls, which I personally truly miss.
Agreed.
I could go wither way.
Disqus has the ineffable value of giving me the ability to "execute" a knave. I loves me some Block button!
That reminds me: what's Aquarian Dreamer up to?
Disqus for reasons I mentioned in previous post.
If you want commenters to just comment on your posts, then the WordPress commenting system is fine.
If you want commenters to engage in discussions in the comments, then the WordPress commenting system is pretty worthless.
As its name implies, Disqus excels at facilitating discussions. (Even though I always pronounce its name like the athletic event rather than the way I think they mean for it to be pronounced.)
Whatever you do, get rid of the orange text in the comment editor.
Experimenting with the "quote" tag...
The hex code for this orange text color is #FFA864. Or RGB 255,168,100. If I had access to the stylesheet, I'd search for that, and change it to #222222. I would consider it age discrimination to do otherwise.
Exactly.
WordPress Comments are a letter to the editor. Disqus comments are a talkback.
I should perhaps note that the Disqus plug-in for WordPress has pretty terrible reviews.
I did not see any way to comment on your Covid post. You asked how China has been relatively unscathed. I raised this on another site and was informed:
1. Lies.
2. Draconian lockdowns.
3. Low prevalence of comorbidities means almost all cases are mild and can be ignored in stats. This is even more true in Japan.
4. There's a theory with anecdotal support that many east asian people were exposed to similar viruses in the past.
I think it was just a test post to ensure the page will publish.
The original is still at MotherJones.
Please, just eliminate comments. You don't need them.
You are not required to comment.
I find Disqus is easier to use. WordPress sometimes gives me grief when logging on, editing, etc. That's not to say Disqus hasn't had its share of troubles, but I just find that I can work with it more easily than WP.
Disqus is good. Very user friendly. The single sign-on for the commenter who comments in multiple places with Disqus is also a plus.
Discus has been good in the past, and has better moderation tools, I believe.
But really, whatever meets the level of effort you want to sustain is better.
NOT Disqus please. (I deleted my account and won't be re-creating one.) See, e.g. https://medium.com/hyvor-talk/19-reasons-to-remove-disqus-from-your-website-5f709a6677d4
I like Disqus but do what you want
Disqus please. 🙂
As long as it's not Twitter... Not after what they did to Donald Trump.
I dislike Disqus though Lawyers Guns and Money does ok with it.
The big advantage is the comments will run in their servers instead of your (likely underpowered) BlueHost server.
Testing...
I will be happy with whatever you do to provide comments as long as I can hide them from my view.
disgqus
Disqus never liked me, thus leaving me unable to respond to the websites that use it. However that may be a good thing for me in the long term.
As long as I can jump through whatever hoops your commenting system puts up, I don't care.
I would prefer Disqus. Disqus is really good for commenting - you can easily reply to people and track your comments and replies to them, and you can collapse threads really easily if you want to ignore a discussion.
Disqus, for the blocking power.
disqus
Disqus, please. A Blue Jays blog recently ditched it and the replacement was very difficult to edit and format. Complaints were many.
Creighton or Toronto?
Mild preference for Disqus.
I prefer disqus.
**For now, the consensus seems to be FOR registration but SPLIT on Disqus.**
I take it you got emailed opinions? Because the comment threat seems be running 5-1 in favor of Disqus.
Anyway, looking forward to the new site being fully up and running. Also, REALLY nice photos of OC!
**For now, the consensus seems to be FOR registration but SPLIT on Disqus.**
I take it you got emailed opinions? Because the comment thread seems be running 5-1 in favor of Disqus.
Anyway, looking forward to the new site being fully up and running. Also, REALLY nice photos of OC!
It looks like the relevant CSS is this:
.entry-content a:hover, :focus {
color: #ff8627;
}
I'm not sure where else that might be important, so you should be able to disable it just for the comment textarea by adding this to your custom CSS:
textarea a:hover, :focus {
color: initial !important;
}
Or you could set it explicitly to black by replacing "initial" with "#000000".
On second thought, I bet the best way to fix this is just to find that first stanza in your custom CSS and change the ":focus" to "a:focus". I'm guessing that's intended just to change the color of links when you mouse over them, but it's doing odd things with, for example, nested comments as well. If you click inside Larry's comment, the text (except for the quoted part) turns orange, and I doubt that's the intended behavior. I think changing the selector to "a:focus" will fix that as well.
Oh, I'm sleepy and making mistakes. That's not how css selectors work. The problem, I'm pretty sure now, is that ".entry-content a:hover, :focus" means that _anything_ with focus gets turned orange, because the comma separates completely new selectors, not attributes of the first one. So it's not applying to ".entry-content a:hover" and ".entry-content :focus" (which I'm not sure is what you want either); it's applying to ".entry-content a:hover" and ":focus", and that ":focus" is catching the comment textarea. So the fix will depend on what you intended that stanza to turn orange. Removing ", :focus" should fix the comment box, but might make something you wanted to be orange not be. I think. See above about being sleepy.
Testing, is this thing on?
To follow up on @Rosette's comments above, the bad style causing the orange text while editing looks like this:
.entry-content a:hover, :focus{
color: #ff8627;
}
It should be:
.entry-content a:hover, a:focus{
color: #ff8627;
}
(Notice the insertion of an additional "a" before "focus.")
I've verified that this works by making an on-the-fly adjustment to the page via Chrome dev tools.
This style is embedded directly in the HTML of the page (that is, it's not coming in via a stylesheet), so I don't know exactly how it's being inserted, but it does have the id wp-custom-css, so that should at least be a hint.
@Steve_OH: If that's the case it must be coming from comments.php. The theme developer believes it builds character to figure these things out for yourself, so I guess we'll have orange text in the comment box...