Ming

If you use a new database you won’t need to change the prefix.

WP calls the tables by database name -> table prefix. So as long as the databases are different it won’t reference the same table.

Personally, I still change the prefixs. It makes no difference to WP and when you backup your database it’ll have a more descriptive name.

Yep, absolutely. Permalink URLs make your links easier to understand and navigate. But the real advantage is that they never need to change. Even if you switch from WordPress to MovableType to Textpattern your link (and everyone’s bookmark to that article) will stay the same. Without permalinks you can’t guarantee that. But if that’s not a problem then don’t worry about it, yoursite.com/index.php?p=[post-id] will link/bookmark/etc just fine.

Here’s two links that’ll help

http://codex.wordpress.org/Using_Custom_Fields

http://www.coffee2code.com/archives/2004/06/30/plugin-get-custom/

Have you installed any plugins that are using the output handler? Try disabling all your plugins. Do you still get the error?

This is possible in CSS. What you have to do is think like a table 🙂 By that I mean you’re using table cells as ‘hooks’ – ie somewhere to place the appropriate background image. So you have to convert <td> elements to css elements.


<div class="dailypost">
<div class="top">Today's date</div>
<div class="middle">Post Text</div>
<div class="bottom">...</div>
</div>


Then what you could do is add all the images together into three strips. So you’d have left corner + top bar + right corner as one image and set it as the background of top. Do the same for the middle and bottom. That’ll give you the same effect. Keep in mind the one image per row only works for fixed width layouts because the image is premade at one size. To do it in a liquid layout, like you’re currently doing, you need to add a few more hooks. I can’t remember the exact article but you should check http://ala.com (A List Apart). I know it’s had articles about this in the past.

Sorry that doesn’t directly answer your question. Just wanted to show you some CSS alternatives.

remove_filter('the_content', 'wpautop') will keep WP from adding <p> elements to your content field. You can put that in the post loop before you display your content. I assume ‘nl2br’ works the same.

The reason filters are applied each time the post is called, instead of storing the converted text in the database, is for flexibility. For instance you could change wpautop to add <p class="blah"> and then all posts will immediately reflect the change. If you saved the <p> into the database you’d have to write a function to either remove them from old posts or convert the old posts to the new class. That’s difficult because how could the function know whether it’s a <p> that you entered or that wpautop entered? But you’re right, it does take extra processing to do each time so there’s definitely a trade off.

Did you make a page in WP called stats? If WP has a page for something then it’s included in the rewrite rules and WP is used to fill that request. So if you have a page called stats, delete it and regenerate your permalinks.