The importer accepts multiple filenames simply list them all, separated by commas. This is usually index.html on Apache servers and default.htm on IIS. The name of directories’ default (index) files for this site. For example, if you are importing /Sites/old_site/public_html/about/, the URL should be.
#Sitesucker faq update#
If you are importing a subdirectory and not the full site, update this URL to include the subdirectory. This is not where the importer will search for files to import those must be specified using the directory option above. The old URL should correspond with your beginning directory. This MUST be a path to a directory on the same server as your WordPress installation. The importer will figure it out.ĭo not enter a URL for the directory to import. The importer will then be able to locate any linked images in the uploaded file.ĭon’t fret about whether or not to include the trailing slash. You may leave this blank if you plan to upload a single file later, but if you can fill that file’s path anyway, do so. users/username/home/public_html or /Library/WebServer/mysite). On a UNIX-based server (including Macs), the path will begin with a slash (e.g.
#Sitesucker faq windows#
On a Windows machine, that path will begin with a drive letter (e.g. Filesįind the absolute path-not a site- or file-relative one-to this directory. The sixth (Tools) contains links to some tools that are helpful after you’ve imported, and lets you regenerate the rewrite rules to imported documents–useful if you change your structure after you’ve finished importing. You need to look through the first five before you run the importer. The settings page (Settings → HTML Import) is broken up into six sections. This is a complicated importer with lots of options. (Bulk Edit doesn’t work on titles.)Įven more important: you need to make sure that the content you want to import from each file is surrounded by the same HTML tag or Dreamweaver template region in every file.įinally, if you want the importer to copy your linked images and documents into the Media Library, make sure the image paths are correct! The importer can handle all of the following path styles, as long as they work: Importing HTML Files Of course, you can change the page titles after the files have been imported, but it’s usually faster to edit the files than to edit and save each WordPress entry. (Most WordPress themes automatically insert the site title into the tag, so you don’t want that to be part of each post’s title, or it’ll be duplicated.) In order for this to work, the phrase must be exactly the same in all your files. For example, the importer will give you an option to remove a repeated phrase from page titles. It’s a good idea to look through your HTML files and make sure things are consistent before you run the importer. Otherwise, you’ll flood your social network with your imported posts! Cleaning Things Up If you’ve installed a plugin that crossposts your content to another site (like Facebook or LiveJournal) or automatically notifies another site of your new posts (like Twitter), be sure to deactivate those plugins before you import. If you’re importing content into a WordPress site that already contains content, back up your database and put the site into maintenance mode before you begin importing.
#Sitesucker faq install#
You’ll probably need to do a little bit of cleanup work afterward, so you’ll need to install the Search and Replace plugin as well. I like DB Backup for its simplicity, and I recommend it if you don’t already have a backup plugin. Therefore, it’s important to install the a backup plugin in case you need to start over. Importing can be tricky, and it doesn’t always go well the first time. If the directory contained a default index file (in this case, index.htm), the contents of that file will be used for the parent page. If you choose to import the files as pages (or any hierarchical post type), the new page hierarchy will match your original directory hierarchy. (I’ve done this a few times for clients who’d forgotten their passwords.)
#Sitesucker faq download#
If you do not have (S)FTP access to the old site, you can use wget or an application like SiteSucker to download the files.
The files you are importing must be on the same server as your WordPress installation. The importer will try to import improperly nested HTML, but it might not work as you expect! Your files don’t necessarily have to validate according to the W3C specification, but they should at least contain tags that are properly nested. It therefore works best with well-formed HTML. The plugin works by reading HTML as XML and copying the specified tags’ contents into various WordPress fields. Current version: 2.5 How the HTML Import 2 Plugin Works
0 kommentar(er)
