yami

I think this is what she meant:
https://codex.www.ads-software.com/Wrapping_Text_Around_Images

Add this to your image tag, tweaking the margin size as necessary:
style="float: left; margin: 1em"

Vspace, hspace, and align are deprecated HTML attributes. I’m not sure they’re even supposed to work in XHTML (which is what WordPress works in by default).

https://codex.www.ads-software.com/Template_Tags/wp_list_cats

You’ll need to use CSS to style the sub-lists produced by the “hierarchical” option.

Do a search for whatever message is showing up that you want to remove, and you’ll get to the right spot. If you’re not very comfortable working with WordPress templates, the simplest and safest way to go is to enclose the objectionable text in comment tags: <!-- -->

But templates aren’t all that tricky, and I’d recommend reading Stepping Into Template Tags as an introduction to how it all works.

Chaz, a better way to do that might be to use the anchor tag that’s already embedded at the top of your comment form. Simply edit your theme’s index template to link to #reply instead of #comments. The page will load pre-scrolled, but people can still scroll up if they need to reread something while they write their comment.

First, edit all your pages (Manage > Pages) and uncheck the boxes under ‘Discussion’ marked ‘Allow comments’ and ‘Allow pings’.

Depending on the theme, you might still get a little message saying that no comments or pings are allowed on the page. In that case, you’ll have to edit your theme template (probably page.php).

Use the “no formatting” option in the Text Control plugin.

Feed: is a new protocol that hasn’t been widely adopted and is not supported by most browsers. Simply edit wordpressdir/themes/default/footer.php to remove it.

Ask your host about their mod_security setup; they might be filtering out your requests due to the presence of suspicious security-type strings.

My host throws a 406 whenever I write a post with the word “.htaccess” – I have to remove the initial dot to make it work.

https://codex.www.ads-software.com/WordPress_Localization

Alex King’s new popularity contest plugin looks like it might do what you need, with a little tweaking.

Do you want the headline from the article displayed in your comments RSS feed? Or do you just want it to show up in the “recent comments” list on your site?

For the former, you need to edit your RSS template. For the latter, there are a number of recent comment plugins you could use.

Hoorah for things working!

To try and put this a little more coherently: include and require are the same function. They act in exactly the same way, except for when they can’t find the file they’re looking for. With include('/wrong/filename');, that file will simply be skipped and the rest of the page will be displayed without it. With require('/wrong/filename');, the PHP processor will stop trying to execute the file, and you’ll see something like “Fatal Error: can’t find file wrong/filename on line 236 of blah.php”.

So you should be able to change include('/wordpress/wp-blog-header.php'); to require('/wordpress/wp-blog-header.php'); and not notice any difference. Or at least, that’s what the php manual says! I’m always reluctant to fiddle with these things once they’re working ??

Somefool: the difference between include and require is how they deal if they can’t find the file. Include just gives a warning, require halts processing of the page and screams bloody murder.

Includes through http should work – have you tried this with other files? Can you successfully include a plain text file from your theme directory using this method?