Static Pages

The .htaccess file belongs in the same directory or in a directory above the one that has the static files. If you have a directory called "salesinfo" with html files in it, you can place the .htaccess file in that directory. You can place a copy in any directory where you have static files. You only have to place it in the topmost directory as it will work on all subdirectories. You can also place it in your document root directory where it will affect every static HTML file on your website. Be careful not to replace any existing .htaccess files. Copy the existing .htaccess files to your local disk, edit them, and paste the new directives to the end of the original .htaccess file. WordPress creates an .htaccess file at your installation root. Be careful not to delete or overlay this. You must edit it and place the new directives at the end of it.

The plugin just slams the old page into the new formatted page. It makes no attempt to correct any of the formatting in the old page. If there are headers, side menus, footers or fancy formatted sections, especially with absolute positioning, the only hope is to edit the static file to make it better behaved.

This is a problem with your .htaccess file. Either delete any new .htaccess files, or restore them to the original state. You may have made a typo when you created the new files or you may have screwed up the original. If there is a problem that can't be fix, then you need to delete the .htaccess file outright. If you lose your permalinks in WordPress, you need to go into WordPress settings and select Permalinks. Change the permalink structure, and save it. Then change it back to where you want it and save it again. This will recreate your WordPress .htaccess file.

This happens because there is no index file in the directory. Copy the main page in the directory naming it "index.html" and try again.

Windows doesn't like files starting with a dot. Try copying an existing .htaccess file from the internet and edit it. You can als edit a file named htaccess without the dot. Copy this up to your website using ftp, and then use your ftp client to rename it. I have done this with both Filezilla and WS_FTP.

I have set up the plugin so that it works with html, txt, pdf, some music files and some video files. I put a section in the code to handle a large list, but not all will work. The settings page will create the contents of an .htaccess file for a few that I have tested. (Tested means that I got it to work most of the time - it does not mean it worked perfectly.) If your browser can handle a file type then the plugin will work. You can't be sure that a visitor's browser will work. Just add a new line to the .htaccess file for one of the file types listed and see what happens. Report back success or failure. Here is a list of file types that may work. html, htm, shtml, xml, gif, jpeg, jpg, atom, rss, mml, txt, jad, wml, htc, png, tif, tiff, wbmp, ico, jng, bmp, svg, webp, jar, war, ear, hqx, doc, pdf, ps, eps, ai, rtf, xls, ppt, wmlc, kml, kmz, 7z, cco, jardiff, jnlp, run, prc, pdb, rar, rpm, sea, swf, sit, tcl, tk, der, pem, crt, xpi, xhtml, zip, deb, dmg, eot, iso, img, msi, msp, msm, mid, midi, kar, mp3, ogg, ra, 3gpp, 3gp, mpeg, mpg, mov, flv, mng, asx, asf, wmv, avi, m4v, mp4. WARNING: if you use htaccess to send image files (jpg, gif, etc) to the plugin then you will not be able to display images on your website normally. If you have a directory of images that you want to wrap, you can put a new .htaccess file in the directory and use the plugin to wrap them - but the images cannot be accessed in any other way.