Oh ... Really?

Posting a test

Or ... testing a post. The Google Reader issues "seem" to be resolved. But still much of a mystery ...

The web host tech support disabled the .htaccess file and called it all good.

I call BS. There is NO WAY that an .htaccess file could cause a server to give out an incorrect Http status code on RSS and Atom feeds, unless explicitly coded to do so, which mine is not. Only the two feeds from this site, and the one on the Designs site were failing to update. The others were still working. The .htaccess file in question resides in the www root directory, so if it was the culprit, it should have affected all the feeds on this account.

Further, there were no changes made to that file when the problems started. What did change was something in Google Reader itself, despite their massive protestations otherwise ... and other issues my server was having with ImageMagick, Phpsuexec, file permissions and Internal Server Errors. Tech support mucked around for a week trying this and that and the other thing ... never did get all that resolved. But my feeds stopped updating at the same time.

Sunday night, I downloaded all my software files, then deleted them off the server. I dropped the MySQL databases, and restored only the ones I still use and need. I cleared a bunch of old files in old subdomains, and basically started fresh. At the same time, I asked tech support (for the umpteen billionth time) to look into the Http Status Codes, and the settings changes that were previously made. That is when they also disabled the .htaccess file. Something apparently worked, Google Reader updated two posts made that day. Before declaring it all good, I am posting this too now ... we shall see.

And then I want my .htaccess file back ...

UPDATE: Holy crap. This post showed up in Google Reader almost instantly! At least the RSS feed did ... nothing on the Atom feed yet.


Posted by LissaKay on 11/28/07 at 11:37 PM in Blogging
• (5) Comments Pop UpPermalink
Just thought I'd mention that Google Reader updated my subscription to this at 9:53pm. smile

MarkRH

Posted by MarkRH on 11/29 at 03:43 AM
 
Yawn...stretch...scratch...blink...

yes, you're updated in my google reader!

welcome back!

Posted by serr8d on 11/29 at 08:14 AM
 
I have no clue about any of that technical mumbo jumbo. Fact be known, I can barely type. Anyhoos, I have you saved in my favorites and that-a way I can find you anytime =)

Don't hate me cuz I'm computer lame.

Posted by Diva on 11/29 at 11:40 AM
 
Nice blog page you have! Good job.

Have a question. Do you keep a robots.txt in your root directory and if so, are you restricting any search engine bots?

Posted by MysterHK on 12/02 at 12:47 AM
 
LissaKay's avatar
The robots.txt was ruled out early on in the troubleshooting process. For one, the Google Reader uses a crawler, not a bot, so it isn't affected by that file. Two, I only have search bots blocked from second and lower level directories that I don't want indexed or archived.

I am convinced that the issue was caused by the server settings getting all mangled when the ImageMagick and then Internal Server Error 500 issues were being investigated. I think something mucked with the PHP engine or something. Don't know, don't care ... going to a new server and refreshing all my files and databases apparently did the trick.

Thanks for stopping by!

Posted by LissaKay on 12/02 at 03:05 AM
 
Commenting is not available in this channel entry.

« Back to main


.