Mark

@samuel B:

That should probably be more like this:

AddType x-mapp-php5 .php
AddHandler x-mapp-php5 .php

And that needs to be added to a .htaccess file that is either located in your Web site root directory, or to .htaccess located in your WordPress directory.

If the .htaccess file doesn’t exist then create it.

jvazjr: Just delete the code you posted. Then add your own footer and wrap it in the appropriate HTML as show by Rich. Something like this:

?> <div id="footerwrapper"><div id="footer">
<div id="footerleft">
Copyright © 2010 - MY_NAME_HERE
<p><?php wp_footer(); ?></p>
</div> <!-- Closes footerleft -->
</div> <!-- Closes footer -->
</div></div> <!-- Closes footerwrapper --><!-- Closes wrapper -->
</body>
</html> <?

Note to theme devs that want to encode junk in their theme (which is entirely lame, but whatever…) — Do what Automattic does: Use Javascript and encode THAT instead. Then you don’t violate the GPL license.

Sorry, there’s a typo. This line:

ini_set(‘post_max_size’,105M’);

Should be this:

ini_set(‘post_max_size’,’105M’);

Here are the basics for PHP code that you can put in another PHP file (your static HTML page) – you’ll have to adjust this to fit into your own site (directory path, etc):

<?php
include('wp-config.php'); // include the basic WP startup stuff
query_posts('showposts=10');  // get the last 10 posts
while (have_posts()) { // got any posts?
// start writing the HTML output for each post here....
    the_post(); // stuff the required parameters
    // write the title
    echo '<h3><a href="'.the_permalink().'">the_title().'</a></h3>';
    // write the content
    echo the_content();
// etc etc etc
}
?>

You could do what I do: Pretend the auto-upgrade feature was never added. It’s broken on a mega-ton of Web hosting sites and it’s broken if you implement strong file permissions security on your site.

Better to manually handle upgrades. For now anyway. Until somebody gets the idea to fix the WP upgrade code so that it actually tests for compatibility FIRST before proceeding to break stuff and generate a lot of support requests….

Something in your site is sending output to the browser BEFORE WordPress has a chance to send formal HTTP headers. That could be caused by a plugin or faulty theme code. First switch to the default WP theme and see if the problem disappears – if so then it’s your theme obviously. If it doesn’t then deactivate all your plugins and try again. If it’s gone then start activating plugins one at a time, checking your site after activating each one until you find the one that causes the problem.

Every other post has an “alt” class in the surrounding <div…> tag – like this:

<div class=”hentry alt2 post publish author-admin category-uncategorized untagged y2009 m01 d29 h13 alt” id=”post-17″>

So that “alt” class changes the H2 A tag style (e.g. the < a href … > tag that wraps the post title) for the post heading. With the “alt” class the CSS style for the “A” tag is this:

.alt a {
-x-system-font:none;
color:#F5F5F5;
font-family:"Lucida Grande",Geneva,Helvetica,sans-serif;
font-size:10px;
font-size-adjust:none;
font-stretch:normal;
font-style:normal;
font-variant:normal;
font-weight:lighter;
letter-spacing:1px;
line-height:1;
margin-right:1px;
padding:10px;
text-decoration:none;
text-transform:uppercase;
}

Without the “alt” class the CSS is this:

a {
color:#555555;
text-decoration:none;
}

So there are 3 basic ways to fix that problem:

– Delete the “alt a” class from your style sheet if you don’t want to use it (check around line 67)

– Find the code in your theme files that injects the “alt” class in the post title < a … > wrappers and remove that code

– Adjust the “alt a” class styling to meet your needs (in your theme’s style.css file, again look around line 67)