scribblerguy

Depending on what you want to do, you could…

(1) Use a custom Loop with a custom query_posts call before it.
(2) Use wp_get_archives with the “type=postbypost” argument.

Hope those help, but without a fuller explanation of your intentions (is this an archive page, a listing of pages from a category, etc.), I can only provide a general answer.

I was getting the endless wait for liddles.net, but could get to a specific page (e.g., liddles.net/?p=3), but now I get this:

Error 500 – Internal server error

An internal server error has occured!
Please try again later.

Though, that was only for a moment. Now, it’s back to the non-resolving loop.

The “500” error suggests that there’s an error in one of the configuration files that Apache (the software on your web host’s server that actually “serves up” the web pages). Though it could be related to the PHP processor.

Since this is happening on two domains, this seems more likely to be a pure server configuration issue, but you’ll need to some testing first, to make sure.

The first place to check for Apache configuration files is the root of your domain. I see that on liddles.net, you’re use pretty permalinks, so WP should have generated a .htaccess file in the root (or, if you installed WP in a subdirectory, in that directory).

Rename the .htaccess file to something and try accessing your domain. If the problem stops, then the issue is probably some setting that is contained in that .htaccess file.

If that stops the issue, go back to the Permalink settings page in the Admin Panels and update the permalink structure so that WP can regenerate its .htaccess file. If you don’t do this, WP will continue to use pretty permalinks, but the Apache web server won’t know how to process those requests.

If none of the above fixes the problem, then turn pretty permalinks off and switch to a default theme and deactivate all plugins. If the problem still occurs, then we can likely rule out something that WP or a plugin is doing.

Then, this is probably an issue related to your webhost’s server configuration (maybe they just upgraded something), and you should ask your host’s support for help in further isolating the problem. But, you need to do the above things, first.

EDIT: I was able to get https://www.liddles.net/index.php to come up, but it seemed to take thirty seconds at least, but since I had that going in a background tab, I wasn’t paying attention.

For someone to help you better, could you please…
(1) post the address of your website.
(2) post the specific address of the page that wp_list_pages is not finding.
(3) mention how you are using wp_list_pages. Is this just the “Pages” widget? Inside a theme (and which theme)? Or something custom? If you’re using a theme or some custom usage of wp_list_pages, please post an excerpt of your code.

If wp_list_pages() is being used with arguments, e.g., wp_list_pages('depth=1'), that could be limiting the output. But, without seeing your particular site, all I can really do is guess at what the cause of the issue could be.

…/wp-content/mu-plugins/gt_search_all_blogs

Are you using WordPress MU (multi-user)? If so, they have their own forums:
WordPress MU Forums.

If you just have one blog or a few WordPress sites, then ‘classic’ WordPress is what you want. WordPressMU isn’t designed for the average user.

I checked william.petruzzo.com, that meta tags list the generator as WordPress 2.5.1, which is the ‘classic’ version.

WordPress 2.5.x now searches all posts and pages automatically. If you’ve somehow installed an MU plugin in WP ‘classic,’ then you’ll need to remove and uninstall that plugin.

Consider creating a text widget (which can include whatever HTML you want) with a list of manual list of links

Does pinging happen automatically when you post?

Yes, if you haven’t enabled the privacy setting, haven’t touched the “Update Services” area on the Settings > Writing page, and haven’t unmarked the “Attempt to notify any blogs linked to from the article (slows down posting.)” checkbox on the discussion page.

Also the Pings checkbox under the Comments & Pings section near the bottom of each post, is this ping just related to commments and not pinging the blog directories?

That is my understanding. Also, the “pinging of the blog directories” is normally done via pingomatic.

Not that I’m recommending this approach:

Google: CSS dropdown menus

In your theme’s stylesheet, around line #110 is:

#content p img{
	float: left;
	border: none;
	margin-right: 15px;
	margin-bottom: 10px;
	}

The quick fix would be to remove the “float:left;” — though no guarantee that it won’t screw up something else.

Consider getting the IE Dev Toolbar for Internet Explorer and/or the Firebug extension for Firefox.

All I can see is one post – “2008 Charity Bike Rides.” I checked your RSS feed and the About page — no content is showing up for any of those, so this doesn’t look like to be a theme issue.

To help us debug this problem, please do the following steps:

(1) Login and edit that page. (There should be an “Edit” link visible on the actual post page once you’re logged in.)

Is there any content in the visual editor? If not, just add a quick sentence or two and save the post. Now, when you go to view the post, does the content show up?

(3) Deactivate any and all plugins (if applicable).

(4) Switch to a default, unaltered theme.

(5) If the problem is still occurring (which I suspect it will), back up your theme and reinstall WordPress — new database, new files (clear out all the old), etc.

(6) Hopefully on the reinstall, the default “Hello World” post should be displayed. If so, then please let us know and mark this thread as resolved.

If you’re still having a problem, then say so, as this could be some sort of odd bug, whether with WordPress or the settings of your web host’s server.

The most elegant solution would be to create a second “sidebar” that is actually part of your footer.

Useful instructions on multiple sidebars are at quickonlinetips.com.

I see that you are using absolute positioning for your main div’s, which is not necessary for your current layout. By switching to “static” positioning, it’ll be much easier to accomplish what you want.

Since you’re not using a sidebar, the basic structure of your site is essentially three div’s:

<div id="header">
Header stuff here
</div>
<div id="content">
The main content here
</div>
<div id="footer">
Footer stuff here
</div>

Because div’s, by default, are “block” elements (like a “p” – paragraph – element), they will take up the whole width of the browser. The next element after a div will show up below the first div.

If you want these divs to be some distance away from the edges of the browser window and you want the content to be a fixed width, then use the following CSS declarations in your stylesheet:

#header, #content, #footer {
width: 750px;
margin: 0 auto;
}

This should restrain the widths of the divs to 750 pixels and by setting the left and right margins to “auto,”* this will automatically center the content in the browser window, regardless of whether the user has a small laptop screen or a large widescreen monitor.

*The zero is for the top and bottom margins.

If you’re in need of a good CSS / stylesheet tutorial, the one at w3schools.com isn’t bad.

Also, the Codex has a number of articles on theme development, including CSS stylesheets. It’s usually easier to search for what you want then navigating through the menus and pages.

If you’re in need of a better editor for your theme’s files, consider
Komodo Edit, which is free. It does have a bit of a learning curve, but it also has some useful power features that are handy for non-experts such as inline code suggestion.

Just use server-based redirection. For Apache, the mod_alias documentation covers that. Also, see this Redirection Guide.

Please see this forum post.

If you don’t have pretty permalinks enabled, the same thing can be done with “https://www.example.com/?cat=3” where “3” is the ID of the specific category.

That looks like an “error” caused by your web host’s server having enabled a specific add on for the Apache web server, which is called mod_security.

Basically, the spell check routine is triggering a false positive by that module.

There is a workaround that’ll probably work. Take a look at this post and later posts in that thread for details.

I’m hesitant to suggest a specific course of action, other than checking with your web hosting provider and seeing what they’ll do or recommend.

Are there any global issues with WP that may have led to this, or is it more likely a css problem?

Browser rendering issues are a very tricky subject. WordPress should not be causing any problems. Sometimes themes have errors in them, which could lead to broken HTML code. The same thing goes for plugins. Broken HTML markup will screw up the CSS rules that a browser applies when rendering a page.

But, without a link to a live website, then one can only guess at the specific issue.