Ryan Boren

The use of SCRIPT_NAME in 1.5.1 was a mistake. It’ll be gone in 1.5.1.1.

Private posts behaved like this once upon a time and then get broken. Now they are fixed depending on your definition of fixed. 🙂

I may be misinterpreting the question, but can’t you use $_GET['fontsize']?

You will trip over this bug if you are having database connection problems. You can simply remove line 304 of wp-db.php, which looks like this:

header( 'Content-Type: ' . get_bloginfo('html_type') . '; charset=' . get_bloginfo('charset') );

With that line gone you will be able to see the real error message. Details here.

Read the thread.

http://trac.ww.wp.xz.cn/browser/tags/1.5.1/

In the get_pagenum_link() function, try replacing this:

$index = $_SERVER['SCRIPT_NAME'];

with this:

$index = 'index.php';

This will break paging in the edit posts page, but should fix paging elsewhere. This is just a workaround while I figure out how best to workaround environments where SCRIPT_NAME is populated with the PHP executable name.

The Loop is just an interface on top of the global $wp_query object, which is created before templates are loaded. If a query resolves to a single post, page, category, or author, the object for that single entity can be obtained with $wp_query->get_queried_object(). For a single post query, this will return the equivalent of $post. Or, you can use $wp_query->post.