andwat

Are WP-specific Greasemonkey scripts eligible? I’m guessing not, but thought I’d check.

Thanks very much for these fast and helpful responses!

Hundreds of thousands of the photos at flickr are under Creative Commons, and thus available as graphics for your blog provided you observe the licenses selected by the owners. My blog uses such photos, not all of which are my own work. Here’s a post on CC at flickr:
https://changingway.net/archives/56

Usability is a priority for WP development. For evidence of this, see:
https://changingway.net/archives/51
Given this priority, posts such as the one that started this thread seem very valuable. Thanks, kay9, for initiating this discussion.

Again, K, I thank you. It works fine. And thanks for the bonus info also.

I’ve now done most of what I set out to do. You can see an account of the steps at:
https://changingway.net/archives/28
While you’re reading that post, you can of course switch themes. That means you’ll switch .css and .jpg while using the same .php throughout.

Yes! I now have two themes, winterway and thegatesway. They differ in link color and in font (although not yet in images used – see below). The .php files live in winterway. thegatesway includes the line:
Template:winterway
to specify that winterway is the parent theme, from which all templates should be inherited. I’ve installed the Theme Switcher plugin in the (right-hand) sidebar, as you can see at:
https://changingway.net/

I’m still having trouble with the images. When I tried using
<img src="images/sidebar.jpg"...
in sidebar.php, the images from the theme just don’t display. So I’ve switched back to getting the images from flickr, and the images are the same in both themes, which they should not be.

Root,
Could you send me the files from the Aphrodite project? I think I saw an offer to make said files available before I started getting connection refused errors.
Thank you,
Andrew: andagainma at yahoo dot com

As I just noted in “my” related thread, this seems to be exactly what this line in the theme’s style.css is for:
Template: use-this-to-define-a-parent-theme–optional
Check it out in the Codex, and see if it does what you want. I think that it will, and pretty simply too.
Andrew

It now seems to me that this is why one can specify in a theme header the line:
Template: use-this-to-define-a-parent-theme–optional
The child theme just grabs all .php files from the parent. Anyone used this V1.5 feature?

Hi Jinsan,
You ask whether what you need is “a style switcher or themeswitcher.” I’m not sure that there is really a difference, given that the file in which a theme is defined is style.css. So if you switch files, you switch themes at the same time. At least, that’s the way it seems to me.

I just asked a rather similar question in a different way. See the topic about metathemes, or families of themes, or the more detailed post:
https://changingway.net/archives/25

Andrew

When you say, “Stay the heck away from hosts using Windows. (IIS),” are you advising that we avoid:
– Windows, the operating system, the competitors of which include Linux
– IIS, the web server, the competitors of which include Apache
– any and all Microsoft products
?

There is at least one host that uses Windows as the o/s and Apache as the web server. It’s the one I use, happily so far: weblogs.us.

As so often in the wonderful world of WP, there is a plugin to do just what you want. Take a look at:
https://codex.www.ads-software.com/Pages#Using_a_Page_as_the_Front_Page
There’s also a previous thread in the forums here, but I think that the codex makes it clear.

I can see something like this making sense as part of a hosted service. It would offer WordPress with some of the most popular plugins. I’m not familiar enough with enough of the WP-based hosted services to know to what extent anyone is already doing this.
The relationship between such a service and WP would be similar to the relationship between MT and TypePad. So I checked to see if the PressPad domains are available. PressPad.com is taken, and is a hosted blogging service, but it doesn’t look much like WP. PressPad.org and .net are available, though.

Kafka,
Thanks again. The comments popup now restricts itself to comments, rather than trying to stuff the whole post page into the popup.
The #commentform textarea {width
suggestion didn’t seem to affect the width of the text area on the popup, though. Perhaps it refers to the text area summoned by comments_template? (That was ridiculously wide when I tried comments_template.)
If you are Template Tag Documentation Guy, then you are even more of a hero. And it might be worth an explicit comment on the page on comments_popup_link that it won’t work from single.php (with the WP 1.5 code – not sure whether this is seen as something that should be fixed in 1.5.1).