.htaccess generation issues

Hi Stephanie,

There are some issues with the .htaccess redirect that are annoying. Don’t get me wrong–I’d rather shift a few lines around there than copy-paste hundreds of html files:

The first one probably doesn’t matter but it was the first thing I checked when I got a 500 server error from the file.

1. The syntax used is different than the Apache specification
   

   Redirect [status] URL-path URL

   which may or may not cause issues

2. It doesn’t urlencode the old file names. This was a definite cause of the 500 error. I had a space of some sort in a file or directory name.
3. It creates redirects for directories that go to–THE SAME LOCATION (redirect loops) whenever the old directory name is an acceptable WordPress slug.
4. For the directories that I would want redirected to a new WordPress slug (and thus I leave the redirect in .htaccess), it is in the wrong order. For example,
   Redirect permanent /archive_for_articles/ http://21tnt.com/archive-for-articles/
   (spec syntax) is before
   Redirect permanent /archive_for_articles/kickme.htm http://21tnt.com/archive-for-articles/kick-me-hard/
   , so when I go to /archive_for_articles/kickme.htm, I’m met with a 404 error page and a URL of http://21tnt.com/archive-for-articles/kickme.htm, which is not and should not be in .htaccess.

For bigger imports, it’s a lot of work to correct these things, and for non-geeks, it’s a big deal.

In spite of these, thanks for a truly great plugin

-g

https://ww.wp.xz.cn/plugins/import-html-pages/