Fixed some incorrectly escaped options that would trigger translations on things that shouldn’t be translated
Page template selections are now pre-selected when returning to the options page (props Lee Fent)
2.4
You can now specify more than one index filename (e.g. ‘index.php, default.htm’)
New option to remove the imported title from within the content area
Fallbacks: if your chosen tag/area is empty or does not exist, the importer will select <body> for content and <title> for the title. As a last resort, if there is no title, the original file name will become the title.
You can now use a custom field named ‘post_tag’ to import tags from a portion of the file
UI fixes for the custom fields tab
Bug fix: the importer now correctly recognizes absolute links to images
2.3
New option to import an entire file’s contents instead of selecting a portion of it. (Props Shawn Zilbert.)
New option to generate the title from the filename. (Props Shawn Zilbert.)
New option to preserve the original filename (minus the extension) as the imported page slug. (Sponsored by NYCinsiderguide.com)
New option to choose the date from an HTML tag or Dreamweaver region.
New option to import custom fields.
UI cleanup. The tabs should work a bit better.
“asXML() on a non-object” errors should be less frequent now.
Fixed a problem with file types that would cause blank thumbnails and images. (Props mchev2 and Carsten Bach.)
2.2
Now imports media files other than images. Uses rawurldecode() to remove junk like %20 from file names, and thus should now handle situations where your link is something like my%20file.doc and your file is actually called my file.doc.
Now handles images with https srcs.
Removed a pointless security check that was preventing people from uploading valid image files.
2.1
New option to fix internal links. Also, the importer now bakes you cookies. (Kidding about the cookies.) (August 23, 2011)
2.0.2
Added some helpers to work around servers that do not support PHP’s multibyte string functions. (August 12, 2011)
2.0.1
Added option to set the page template for hierarchical post types. (August 2, 2011)
2.0
New option to import images linked in the imported HTML files. It can handle most relative paths as well as absolute URLs. The report includes a list of the image paths that couldn’t be found.
Now supports all public custom post types and taxonomies (including hierarchical ones).
Completely different, much better handling of special characters.
The import screen now lets you upload a single file.
New user interface. The options form is now broken up into several tabbed sections. Categories and other hierarchical taxonomies are selected with checkboxes.
The options form is now separate from the importer. It will now check your settings before the importer runs — for example, you’ll get a warning if your beginning directory isn’t readable.
The importer itself is now based on the WordPress import class, which means it looks and works more like other importers. It is located under Tools→Import (but you should visit the settings screen first).
Files’ old URLs are now stored as custom fields in the imported posts. There’s now an option to regenerate the redirects for your imported files, which is handy if you changed your permalink structure after you finished importing.
When importing directories as hierarchical post types (like pages), the importer now uses the default directory file (like index.html) for the parent page’s contents.
Now skips Dreamweaver _notes and Frontpage _vti_cnf directories automatically.
Now makes proper use of the Settings API for better security and data validation.
The ‘.,..’ directories are no longer optional, so you can’t accidentally import hundreds of empty posts/pages by removing these from the skipped directories option.
The beginning directory default is now based on the path to your WordPress installation. There’s also a hint shown below the field. This should help people locate their import directory correctly.
There’s now an option to enter your old URL. If you enter it, your .htaccess redirects should work as displayed. If you leave it blank, you’ll have to doctor the paths afterward, as before.
Character encoding is now optional. If your special characters did not import correctly before, try again with this option unchecked (which is now the default).
Options are now deleted on plugin uninstall instead of deactivate. (Sorry about that.)
Code cleanup in preparation for version 2.0. (June 24, 2011)
1.21
same as 1.2; not sure why the plugin repository can’t count
1.2
Added custom taxonomy options
Better handling of mb encoding function and asXML
Better security checking
Added translation support (January 24, 2010)
1.13
Fixed a bug in 1.11 when importing content specified by a tag (thanks, mjos)
Added an option to assign a category or tag to all imported posts
This is 1.12, only uncorrupted (September 13, 2009)
1.12
Fixed a bug in 1.11 when importing content specified by a tag (thanks, mjos)
Added an option to assign a category or tag to all imported posts (September 13, 2009)
1.11
Left some debugging code in 1.1, oops! (August 15, 2009)
1.1
Added Word cleanup option (August 14, 2009)
1.04
Better user capability check (August 3, 2009)
1.03
Still better error handling
minor code cleanup (August 1, 2009)
1.02
Better error handling for fopen and file_get_contents (July 31, 2009)
I have about 2,600 pages to get up on a Wordpress site and this is saving me so much time. It works perfectly. Especially helpful that I can use the file name as the slug, so I can do an easy quick htaccess rewrite for each folder.
Ok, it does not do all the job for you but how can I complain? It did save me a lot of hours of work! Thanks a milion time for this little gem. Hope you'll keep it updated because it's very usefull and well done.
We have a wiki from Wikispaces consisting of 880+ pages and needed to find a new format to host it in without cutting and pasting all of those pages somewhere. A quick HTML output from that site, some mass search and replaces of URL in the HTML files, and an import using this and we had a functioning site again! I hope Stephanie Leary can consider continuing work on this plugin as it has a very specific purpose that can help some of us under certain conditions. It was a great plugin to find and immensely helpful.
This is awesome, just what I needed.
I just got one issue, surely caused by some wrong setting. Each time I import a HTML page int WP, I get all my existing pages copied too (so that I have multiple pages duplicated)
Please help wth this.
Thanks in advance
After spending over a week with in-house developers, web hosting advanced customer service, added php memory, purchased a whole new site for clean install, emails to the developer, posting o boards, etc, we have not been able to import even one page. Even the hosting company worked on it personally. We have attempted a direct full import, small directory files, etc in an attempt to overcome the fatal errors to no avail. Maybe this is a main reason there has been no update to the plugin in several months. Point of interest, we have also attempted the import conversion ontwo different WP releases. Poor execution.
No problems at all. Have to admit I was a little skeptical especially given that it hasn't been updated in a year, but it worked great. Added to my must have plugins list.