AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Site sucker wordpress1/25/2024 ![]() 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.) 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. I’m excited to continue playing around with Sitesucker, but very impressed so far.Current version: 2.5 How the HTML Import 2 Plugin Works Not a bad for a little afternoon project. This way I can begin to alter the content that currently sits at, while simultaneously familiarizing visitors with the new domain.įrom start to finish, this took less than ten minutes complete. I used Chrome’s inspect feature to figure out where the link was located in the code and then used the command+find tool to fix it in my File Manager.Īs my final step of maintenance cleaning, I created a redirect so that all visits to be redirected to for time being. I had an issue with one of my visual builder buttons still linking back to the old domain, but that was an easy fix. I refreshed my browser and boom! The site now loads beautifully (and quickly!) over HTML only. I navigated to the directory, removed the existing cloned WordPress files, and uploaded my new static HTML files. Once having the files on my local hard drive, I closed out of SiteSucker and opened up my FTP client. Within two minutes it was done! I pressed the folder icon (top bar, middle) and could immediately see all the WordPress site files that had been translated to Static HTML. I simply entered the URL and pressed enter. ^Screenshot of what the SiteSucker window looked like while it was working. Kind of a bummer, but I imagine if you do some serious archiving you’d make your money back rather quickly with the amount of time you save. ^I then cloned the original conference website from to using this method.Īfter confirming that the site was completely up to date and loading securely on the new domain, I opened up the SiteSucker MacOS app that I had previously downloaded. I started first by making the subdomain,, and then added it as an AddOn domain to the cPanel account where the current conference site resided. ![]() So between this workshop and the Domains17 site, I thought there would be no better time than the present to get going: Though I’ve recommended SiteSucker to many Reclaim users in the past, I’ve never given myself the chance to play it. As part of my preparation for the workshop, I’ve been wanting to play around with and explore some of the digital archiving tools that are already out there. So to say the least, I’ve had archiving on the brain over the last week or so. On an unrelated (or is it?) note, I’m headed to California in a couple of weeks to take part in Stanford University’s Preservation Workshop to chat about archiving digital projects and possible strategic partnerships with preservationists and technologists. What’s even more, the Domains 17 site was sitting on, meaning if we were having a Domains 19, things would obviously need to be shuffled around. I was also growing rather tired of logging in every now and then and making sure all plugins, themes, and softwares were up to date. This has meant that the conference website,, was just sort of sitting there with content that is now close to a year old. We loved Domains 17 (and are currently mulling over a Domains 19) but we deemed 2018 as a gap year a couple months back. It’s hardly news at this point, but Reclaim Hosting isn’t doing a Domains conference this year.
0 Comments
Read More
Leave a Reply. |