rossjamesparker

Hi @anlino –

Thanks for the reply, I appreciate it. I understand the situation now. I guess I will have to wait for Lovecraft 2.0 someday.

Your theme design is fantastic – thank you for making such high quality work available.

— Ross

Okay, thanks all. Looks like it’s not coming to core any time soon.

Hi Marius, thanks for the response. A few logical queries here.

1. Perhaps the causality runs the other way? For example, it is quite plausible that “the majority of users” don’t make private sites in WordPress because the feature is not in core. Obviously plugins bring with them additional complexity and risk, which some people may not be willing to take. So they choose different software instead of WordPress. This hidden demand is therefore not reflected in your statement.

2. Why do you expect www.remarpro.com users don’t want to use a feature that WordPress.com users use? Do you think that people with a .com blog are for some reason more in favour of private sites? I would tend to assume the opposite.

3. As a WordPress user since Cafepress, I have seen hundreds of features that were once available as plugins brought into core (e.g. Sticky posts). What makes private sites different?

4. There are many WordPress features that are not used by “the majority” of WordPress users. For example, Child Themes. By your logic of a simple majority, is there a case for removing these features? If not, then what is the validity of the “simple majority” metric?

I short, I think your answer amounts to a tautology: “we don’t do it because we don’t do it.”

I had this issue too, then I realised why. I had “require user to be logged in” checked. When this is checked, for some reasons you *don’t* see the “leave comments” link when logged in as an admin.

Beau – that is excellent, thank you! I have just tested that on the live site, and it works. I’ll now work on getting a local bird icon in a Ryu-like format.

Great work on KSI by the way (no idea why I called it KSL above!), it’s a very smooth piece of software, which is surprising when you consider the scope of the plugin(s). There are some features it doesn’t have – like auto-expanding Twitter images, and highlighting tags, but the plugins that do offer this don’t seem so polished, and I prefer polish to features!

I have now solved the first part (getting background colours) by using the following in styles.css:

.category-tweets { background-color: #9AE4E8; }

Now it’s just whether I can use a custom genericon.