benjamin

Unfortunately, no, but unless I am missing something–there’s nothing in my wordpress folders or my database tables to indicate it was an attack on my site level.

Yeah, every page. I’m emailing tech support right now with the suggestions listed by you guys.

I appreciate everyone’s concern.

Alas, for all I know my server is something like 1000 km away.

I am going to try and see if it was only my site affected or the entire host.

iFrames = Bad.
Scrollable <div>s = Bad.
People expect to scroll one way: vertically with no miniature windows.

There’s a glitch with some of the plug-ing, I’ve noticed as well. You can’t run the “Latest Comments” plug-in, as it requires the individual IDs.

Here, download this and rename it as a .php document. I’m new to PHP as well, but I think I got rid of the unnecessary code.

You’ll find Laughing Lizard’s Nicer Archives helpful.
There are manual ways to do this, but this is practically plug-and-play.
And to get rid of the forms at the top, delete the corresponding functions, forms and jaavascript.

Same here. I was considering bringing up the accessibility thing, but that would just create another monstrous link debate.

Maybe this thread will help.
Scriptygoddess wrote a hack, too.

The Wiki has documented all WordPress templating tags.
Trackback tags
Permalink tags.

Perhaps more permalink options should be available in 1.3, then.

That’s the reason for right or CTRL clicking. By opening windows, users have a cluttered desktop.
The main pages of directories should always be called /index.extension. This allows for better linking, more memorable URIs. If a main page is named index.extension, there is no need to put the file name at the end of the URI. An example: which is better?
/archives/2004/08/yes/
-or-
archives/main.php?post-22
Also, target="_blank" opens a new window no matter what. target="new" will open a new window, and then any subsequent links clicked will open in that same window.

I love the idea, thanks. I’ll just leave the entry id’s then, I’ve already set up proper permalinks.
Besides, who does permalink to comments?

By default, WordPress uses PHP_SELF for the search function. The problem is that if you put the search form on another page, it tries to search that page.
I might have changed around the search form a bit, but locate where said form is in your template.
Replace the first line of the search form with this:
<form id="searchform" method="get" action="<?php get_settings('siteurl') ?>">
This will search only where your blog is located, in this case index.php.

Hm, if someone figured this out, it could be applied to post id’s, as well. Thus, keeping your archives better.
(Example: I tested posts about 14 times before I got the blog running; my entry id’s are skewed.)