Tom Richmond

Where is your htacces file placed?
is it in your wordpress root folder, or in the website root?

The website root. If I place it in the WP root (/blog) I get the 500 error message.

Nope, no “Bad Behavior”. I also deactivated all my plug-ins and tried to no avail. I also tried the full path thing, but perhaps I did it wrong. Should I then erase the entry above? I entered fullpath with https://www.etc but still no love. Busted.

Can you open a support ticket when you self host your WP blog?

I upgraded to 2.5 and my image uploaded is broken as many have described. I have tried all the .htaccess solutions here to no avail. I have one .htaccess file in the root directory of my entire website, of which there is a /blog directory wherein resides all my WP files. Thus my dirctory structure is https://www.tomrichmond.com/blog/<all wordpress files>. Adding any of the many .htaccess codes listed above make the blog inaccessable with a 500 Internal Server Error error (Apache/1.3.41 Server at https://www.tomrichmond.com Port 80). No fixes seem to work. My images upload to wp-content/images.

I have every limited programming knowlegde and stuff like chmod, 770 and making sure my directories are “writable” I do not understand.

My blog is almost unusable without the ability to upload images internally. I can “get around” that using FTP and URL image placement, but what a huge disappointment. Is there a link to a detailed explanation of steps to fix this problem for idiots like myself?

Re: the footer code. I am a PHP noob. The link says that this line of code <?php wp_footer(); ?> needs to be added in the “theme” right before the end “body” tag. It does not specify what php file needs this code added. index.php? single php?

Hi- I just wanted to thank you both for this post. It resolved my exact same difficulty.

I don’t know what you are talking about. The technorati dashboard feature showed me updated, recent links into my blog that changed frequently and were very accurate. Google’s list hasn’t changed since I upgraded to 2.3, and most of the links it shows me are from within my own blog, referencing older posts.

No offense, but I think Google is the one that is useless.

Uhhh. I just read that the htaccess file might have been there but been invisible to my FTP program (Fetch on a Mac). Did I just overwrite my htaccess file and destroy my permalinks info?

I tried it again, and this time it worked fine. I think the problem was I did not save the file as a plain text document, so I suspect it was saved as a rich text document by default. WordPress must not like that.

Thanks very much!!! I greatly appreciate the help!

I didn’t have an htacess file before. I use a custom template put together by my website programmers. Does that matter?

Thanks. I tried that but it makes the entire admin area of the blog inaccessable.

Figured it out on my own. Thanks for the nudge. This line in my CSS was the culprit:

.entry ul li:before, #sidebar ul ul li:before {

content: “OOBB OO20”;

width:230px;

}

I replaced the “OOBB OO20” with

none

and presto! the >> that showed up in FF and Safari but not in IE disappeared. Life is good.

I have read the following:

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

but my CSS file is not cooperating. The corresponding line

#sidebar li {
list-style: none;
}

Does not exist in it, nor does adding it change anything.

Really? In front of each link on my blogroll, including those to pages, archives and in each web link category, the link is preceeded by a >>. It’s the same with Firefox or Safari on my Mac. It must be some kind of a browser setting issue.

https://www.tomrichmond.com/blog/index.php

I see your point. As a php noob I haven’t the faintest idea how to change my theme, which was set up for me by the programmers who did the CMS system for my website. Maybe you can help me. All I’d like to do is remove the “bullets” from in front of each of my links on my blogroll. I tried experimenting with changing some code in links.php by replacing < ul> with < p> tags in my current theme folder, but nothing changed.