Michael Fields

1) my search form’s file name is “searchform.php”, but in the Appearance > Editor > Template list it also has a name of “Search Form”.

“searchform.php” is the name of the php file as it is viewed by the file system on your server. “Search Form” is a title that the Template Editor gives to the aforementioned file. Basically, “Search Form” is a human readable version of the filename.

2) And when you want to include it into somewhere such as the sidebar, you call it “search_form”, as in <?php get_search_form(); ?>

get_search_form() is what is known a a Template Tag which is basically a php function that allows you display different parts of your blog in various different templates. This Template Tag looks for a file called searchform.php in your current theme’s directory and if it finds it, it will include this file in the template. If the file is not found , it will print a default version of a search form to the screen.

Where do these alternative names come from?

I think they are just there to confuse new users:)

I’ve created a new newsletter subscription form called “subscribeform.php”. I’d also like to give it a plain English name and include it in my sidebar.php. How do I do this?

Not sure about giving it a Plain English name, but it is rather easy to include into your sidebar. First, upload subscribeform.php to your server – into your current theme’s directory. Next, open your sidebar.php file in a text editor and add the following code in the spot where you would like the form to appear:

include( TEMPLATEPATH . '/subscribeform.php' );

If your theme is widget enabled, you will want to put this bit of code outside of the “widget conditional”… it looks something like this:

if ( !function_exists('dynamic_sidebar') || !dynamic_sidebar() ) : ?>

Best of luck to ya!

Why are you using 2 installs for the same site? I seems to me that the best solution would be to use one. Just trying to figure out your motivations. There is probably a better solution than using two installs. Please reply with a link.

Oh, I’m sorry… after re-reading your first message I see that I misunderstood your question. If you are looking to display previous next navigation for single posts, then you can use these two functions: http://codex.ww.wp.xz.cn/Template_Tags/next_post_link and previous_post_link(). Note, these functions have almost the same name as the ones that you posted.

Your blog should be here: http://mysite.com/blog/. It is possible that your server’s install package did not set a few important variables in your database. navigate to you setting/options page in wp-admin and see if the following two fields are set to “http://mysite.com/blog/&#8221;

Blog address (URL)
WordPress address (URL)

To my knowledge, this functionality does not exist in WordPress. Both the next_posts_link() and previous_posts_link() functions are programmed to work on “page views” that naturally display posts: category & archives pages as well as the default homepage view. Adding these functions to page.php (or any page template for that matter) will render no results. WordPress has no way of knowing which posts to show as “previous” or “next” unless there is data given in the query string.

IMO, you would have to create your own custom paging system that would pass variables in the url which would allow a visitor to stay on one “page” (as WordPress sees things), but cycle through chunks of posts – say maybe 5 at a time.

Best of luck… and if you figure out the code, please post it. You are not the first person who has asked a question like this and you certainly won’t be the last 🙂

That site usess Brian Gardners’ Revolution2 Theme. It looks like his site is down at the moment, but keep trying 🙂

If you are using a plugin that is creating a w3c error, than it is best to fix the error in the plugin that is causing the error. most of the time it is an easy fix. Then you could alert the plugin author that there is an error in their code and ask them to fix it in a upcoming release. If the plugin is licensed under GPL you can also re-release including your valid html/css fix. This was actually done with the realse of WordPress 2.5 where the gallery shortcode was causing invalid code to print. Someone created a plugin that fixed the errors + added a bit of cool functionality.

If you really don’t want any plugin to touch the head of your document, you could just not add the wp_head() action from your header.php file, but, this will cause more trouble for you down the road when newly installed plugins fail to function properly. If you are releasing your theme for others to download and use, I would strongly suggest including the wp_head() action in your header.php file.

you can use: wp_page_menu() instead of wp_list_pages().