Lack of Love 1.0c for Kubrick/WP

OK. I have uploaded the latest 1.3 nightly. I have created a themes directory in wp-content. In there I have added the the sub dir for my theme. I have loaded up an index file and some CSS. But it does not activate in the admin panel under presentation. Is there something I have missed ?

In the CSS, at the top, there should be something that says what name it is like so:
/*
Theme Name: Kubrick
Theme URI: https://binarybonsai.com/kubrick/
Description: The Kubrick theme.
Version: 1.3.0-rc1
Author: Michael Heilemann
Author URI: https://binarybonsai.com/ */
If you put the wrong name in, like if you upload the Kubrick css for Lack of Love, it will display Kubrick. I haven’t checked to see if having spaces in the folder title makes a difference like it does with the skins. Oh and the stylesheet should probably be titled style.css. Worked for me.

You guys need to change the name of the design — or at least the name of this topic/thread. Every time I see that, I think “No one loves the Kubrick design”, not “Here is a design called ‘Lack of Love’ and it’s for Kubrick”!!

So mog there is rather more to this than you first let on. Now I have done all that stuff above and mine is not running. There must be another step to do with editing wp-blog-header at a guess. Plus I am beginning to suspect that this may have worked in one particular nightly but not is subsequent ones. Still as long as you have Kubrick running who cares. We will just wait to do what we are told. Whatever.

So they’ll work like plugins? Very cool. Sounds like there’s still some work to be done with the hooks but this should be a great feature.

Oh forgot, might have to load all the images in the header.php as is done in Kubrick and not call them from the stylesheet. Some problem with differing install paths. Which means breaking up the index.php file.

Is that all?

Root, if you’re curious as to what the changes in 1.3 are, how they work/are going to work, why not sign up for the Hackers mailing list? This has already been outlined long ago on there…

Ive been signed up long ago.

That’s all fine and dandy Michael….. but what about those of us who aren’t signed up, but would like to get started on porting our existing layout to the “new & improved” theme/layout manager? If I had the time, I’d sift through the archives and try to get what I need out of it. If I had more time, I’d go through it all, and maybe try to come up with a distilled document that laid it all out. I’ve got a sneaky suspicion that when people upgrade from 1.2 to 1.3 and find out that their existing index.php doesn’t work (as I found out to my horror and dismay) there’s going to be problems. But if there was something available to the average person using WP, people can prepare.
podz, root, anyone else – would it be worth my time & effort to go through the archives and attempt to pull together some kind of document on developing themes/styles for the new 1.3 format? This would mainly be targeted at the non-programming, non-geek type WP user. Would anyone else be interested in helping me out in pulling together this info? And just as importaint, helping keep the information current – as we all know, things change from day to day.
Imagine my surprise when my 1.2 upgraded to 1.3 site no longer functioned as expected. I assumed it was the index.php file and the template itself, but now I’m wondering if it was maybe a broken function call. Hmmm….. maybe I should check that out before I suffer from “foot-in-mouth” disease. ??
TG

Imagine my surprise when my 1.2 upgraded to 1.3 site no longer functioned as expected.
It wouldn’t surprise me. 1.3 is still in Alpha.
I don’t understand why everybody wants 1.3 as it is now on live sites. On a test server fine, but using alpha software on a live site isn’t the best idea. There’s no big hurry – wait for beta at least ??

True, but can’t you see why template makers and tutorial writers might want to have stuff ready for when 1.3 does come out and average users want to take advantage of any new features? I agree that they are rushing things a bit, but that’s because nobody knows when 1.3 is due. An announcement along the lines of ‘don’t expect an official release before Xmas’ would calm things down a lot.

Well Techgnome that is a kind offer. I am just about on top of this myself but go right ahead if you think we need to move forward. To operate a basic model only about four key pieces of info are needed and they are pretty simple but it is very frustrating if you do not know what they are. Once I put it together with a lot of input from different people in bits and pieces it was was pretty straightforward. I have used Odyssey Alpha One as a testbed and it seems fine AFAIK.

from gpshewan
I don’t understand why everybody wants 1.3 as it is now on live sites. On a test server fine, but using alpha software on a live site isn’t the best idea. There’s no big hurry – wait for beta at least ??
Don’t take this the wrong way, but DUH! I’m not stupid enough to do that. Development is what I do for a living, so I know better than that. BUT, knowing that 1.3 is comming, I decided to give it a try, so that when it does come out, I’m READY FOR IT. So I stuck it on my test server, just to see how easy it would be for me to upgrade. When I went from 1.01 to 1.2, my index.php still worked. I want to know how much effort it is going to take to move to 1.3. I’ve put a lot of time and effort into the current layout. When it suddenly stopped working, knowing that one of the biggest differences was the templating addition, I assumed that is the part of WP that is breaking my site, since now my wp-loop only shows one post, and not even styled right (have some of the css class names changed?) This is stuff I’d like to know up front so I’m not caught with my proverbial pants down.
<stron>from Root
I am just about on top of this myself but go right ahead if you think we need to move forward. To operate a basic model only about four key pieces of info are needed and they are pretty simple but it is very frustrating if you do not know what they are. Once I put it together with a lot of input from different people in bits and pieces it was was pretty straightforward.
And it’s exactly that kind of frustration I’m now experiencing, that I think could be avoided. The reason I’m suggesting starting now, knowing full well that things could be changed be between now & release, is that it is easier to go back and change the documentation as you go along, rather than try to write it from scratch after the fact. It may also happen that while doing the documentation, it may spark a better way to do something, or identify some sort of usability problem. Better to get that stuff up front.
Root – if you have any kind of notes that would of use to me, could you shoot them my way? christoph at anderson dash website dot net
I’ve got the theme pack that you had posted on your site…. not bad, currently I gots the tomato red one running…. my monitor looks like it’s been on the business end of a trauma center! Would one of those be a good place to start with as far as delving into the files to see what is what and how it all works?
TG

Yup. Odyssey is a fine place to start. Just remember that WP looks for the style sheet first. I am going to publish some notes on this very shortly.