Comments on: AutoCorrect 0+1i

By: Fletcher

Fletcher — Fri, 11 Apr 2003 16:00:00 +0000

Could the issue be related to Blosxom having it’s own $path_info variable? Just a thought… Perhaps the source should be changed to CGI::path_info() by default?

By: Fletcher

Fletcher — Fri, 11 Apr 2003 15:44:00 +0000

I changed it to CGI::path_info() and now it seems to be working fine.

Thanks!!!

PS> As for the “error” on your site, I think I was so tired of looking at the file not found warning on my site that I didn’t notice that their was a difference between the url I clicked and the page I was shown. My bad!!

Thanks again!!!!

By: Todd Larason

Todd Larason — Thu, 10 Apr 2003 21:41:00 +0000

The path_info() problem can probably be fixed by replacing it with CGI::path_info(). I’m not sure why some systems need the CGI:: and some don’t.

The second problem I can’t reproduce, at least not on my site — valid .html links work fine, as far as I can tell. Can you give an exact example?

By: Fletcher

Fletcher — Thu, 10 Apr 2003 15:51:00 +0000

I downloaded autocorrect, and it worked perfectly on my local installation (Mac OS X 10.2.4). Then I installed it on my live site at freeshell.org. It would crash during load due to an error on line 75.

I was able to fix this by changing path_info() to $blosxom::path_info. This allows it to load, but it doesn’t seem to work properly. And when I go to a valid link ending in .html, it gives me a page not found error, but redirects me to the exact same page I entered. (Just as your site does… But I just realized your site only chokes on html, not on writeback.…)

I am not sure if these two problems are related, but I was wondering if you had given any thought to this.…

Thanks, and it has potential to be a great plugin if the last few bugs can get worked out!!!!