liquibyte

I made a little bitch about not using the index to hack with in another post, but now that I look at the options that I have, I have an idea. If it’s not validating, change it so it will. Isn’t that what it’s all about? There is a validating link on the index page after all. There are actually a world of possibilities here:
#searchform { }
#wp-calendar { }
#prev { }
#next { }
.pad { }
.credit { }
body { }
div { }
h2 { }
h3 { }
p { }
table { }
tr { }
th { }
td { }
thead { }
tbody { }
tfoot { }
caption { }
abbr { }
form { }
input { }
strong { }
cite { }
li { }
ul { }
a { }

I have a question. If we can’t touch the index php, how are we supposed to do anything creative? For one thing, you have all of those ul’s and li’s in there and they are actually holding me back (Well, not really. I hacked the **** out of it anyway). I mean for one thing, the category link in the actual post is an li and I really don’t want three lines as opposed to one and it’s doing that with the font size I’m using, Plus, I don’t really need them. Having things like that hardcoded in the php is probably not a good thing as far as usability. I had to go into b2template.functions.php so I could actually make my code smaller in index.php by taking out the ones it kept inserting whether I wanted them or not. Which brings me to the main point once again. How are we supposed to do, say, a three column layout when to do that you have to hack into index.php? Doesn’t having those hardcoded items defeat the purpose of a template driven site?

This fixes Opera but makes the submenus in IE have a little gap from the main menu. All in all it looks ok on both.
#menu #submenu {
display: block;
font-variant: normal;
left: 50%;
margin-left: -300px;
position: absolute;
top: 98px; (from top: 91px;)
width: 570px;
font-size: .8em;
}

OK, cvs 12.08.03 had differences in what I was using, so I did a fresh install of that version. First, I installed, then I logged in (no problems) and changed my info. Second, tried to post and got the following (pardon the dashes for slashes, makes it easier to read):
SQL-DB Error:
[Unknown column ‘post_name’ in ‘field list’]
SQL-DB Error:
[Table ‘blog.wp_post2cat’ doesn’t exist]
Warning: Cannot modify header information – headers already sent by (output started at c:-apache-htdocs-wordpress-b2-include-wp-db.php:98) in c:-apache-htdocs-wordpress-wp-admin-wp-post.php on line 143
Third, ran the upgrade-072-to-080.php script (no problems) and logged in and then posted (had to refresh edit page to get the post to show up). Fourth, tried to delete Hello world! post and got this error:
SQL-DB Error:
[You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1]
SQL-DB Error:
[You have an error in your SQL syntax. Check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1]
Warning: Cannot modify header information – headers already sent by (output started at c:-apache-htdocs-wordpress-b2-include-wp-db.php:98) in c:-apache-htdocs-wordpress-wp-admin-wp-post.php on line 363
Works ok if you use the back button and then refresh, the post is gone. Everything else seems to work ok so far, but I haven’t really tested past this error yet because I hate letting a challenge go by and I’ve been trying to solve it myself.
I must be missing something here, because I think the winapi is easier than trying to understand the structure behind this language. Perhaps I just don’t get the naming conventions. Is there a place someone can point me to that has recommended rules for class, variable, and other such stuff etc. in php?

Oh, and I forgot to add that I also used the upgrade-072-to-080.php script. Just remembered that one. I’m just not a php coder yet, I have heard that php is not unlike c++ now but I’ll stick with the hardcoded stuff and just fiddle with the net, it changes too damn much.