brainwidth

Have you upgraded to 1.5.1.1. The latest version includes some feed fixes which may remedy your problem.

There’s one on this page for PHP, but I don’t know of one for wordpress.

@ifelse: the Sassy & Slim theme used stock art from iStockPhoto. The author later discovered that the license agreement for their art prohibits distribution, and so she took the theme down.

Basically, you want the different kinds of posts to each have their own style, correct? One way to do this is with a plugin; Structured Blogging was designed for this purpose. Another way to do this would be to have custom key for different kinds of posts, and you would define different css styles for the different kinds of posts. The Blix theme has implemented this for its use of mini-posts.

Very nice, although I may be a bit biased towards Blix as I use it myself. You have a few validation issues, but I’m sure that can be fixed.

On your short entries at the top, did you just change the styling associated with the mini key built into the theme, or are you using a different implementation of asides?

You may find it easier to use posts for both journal entries and articles. You can use categories to separate the two kinds of posts, and display one category in one list, and the other category in another list. That way you can take advantage of excerpts and other functionality built into the post function.

I think you should basically follow the steps required to upgrade WordPress. If you delete all of your old wordpress files except wp-config.php, you will have a fresh version of wordpress with the default theme, but you will save your database, which includes the posts you’ve made to your blog.

I’m not sure what kind of site it needs to be, but you might try a wiki, like Instiki, which lets you create the site dynamically, but publish to static pages suitable for inclusion in static media.

If all else fails, you can change the link to a hardcoded location. In other words, change this:

<li class="sidebullet">
<a href="<?php bloginfo('blog_url');?>">Home</a></li>

to this:

<li class="sidebullet">
<a href="https://www.migginsstudioarts.com/myblog/">Home</a></li>

Works fine for me in FF 1.0.4. I would uninstall Firefox, delete your profile directory, and reinstall.

You make an excellent point, Kafkaesqu?-. I don’t mean to exclude support from those trying to fix a local installation. I don’t really mean for my statement to be a hard and fast rule, and I don’t want to require anyone to give a link to their site. I only think that we should be wary of helping potential spammers.

Re: the second case. It’s definitely a linkfarm. The numbered links all lead to pages with only marginally different content, all of which looks to be automatically generated and is linked to the bfast ad service. Also, at the bottom of each of those pages is a huge block of links to nearly identical pages with slightly different names Also, do a google search on the author names. Many of them come up with results at EzineArticles.com. That’s a service that specializes in writing fluff articles geared toward optimizing search results. Finally, the front page has at least 4 blocks of google ads and 2 blocks from other ad services. It’s a classic example of a linkfarm. I bet its page rank is gone the next time google refreshes its index.

In your WordPress admin, go to Options > General Options, and look at the settings for WordPress Address and Blog Address. One of those settings probably has that extra smiggles at the end. Change that and you should be golden.

You can use .htaccess to filter referrers, so people can only access a file or page if they clicked on a link at an you specify. Here is a very useful thread on it.

It’s a linkfarm.

I’m sorry, I didn’t mean to imply that you needed to do any additional processing for your feed; you do not. I use feedburner just so I can get feed-related statistics and take advantage of splicing services.

Live Bookmarks is trying to add this feed: https://www.nicktoye.co.uk/feed/. That gives me a 404, which tells me you may have a problem in your .htaccess file, or you have an actual /feed/ directory which you need to delete. More info in a related thread here.