WordPress Plugin Review: WP Static HTML Output

wp static html output plugin paths

I came across this plugin from WPMUDEV‘s newsletter called The WhiP. This plugin seemed like something I could use. It would be nice to see some WordPress Themes moved out into standalone templates. However, I was disappointed, the plugin did not work. Just because the plugin didn’t work on the first try, doesn’t mean I won’t show you how to get it to work.

Download WP Static HTML Output

You can download the plugin from the WordPress plugin repository, and also install it via the WordPress CLI tool.

  • wp –allow-root plugin install static-html-output-plugin –activate

or

Activate and Run

wp static html output pluginOnce it is installed you can go ahead and activate it and then visit the admin page. On this page is where all your options/configurations will happen. There seems to be a few options for free users and then some options for upgraded users.

  • Create a zip file
  • Exported site folder with symlink
  • Keep the generated zip file

 

Configuration

These three options above are the options we have on our free version. Let’s go ahead and select all 3 and move on to the next section of the plugin. The next option is to export the files to our upload directory. The plugin even gives us the full path to our directory.

wp static html output plugin directoryThe next option I see is a little confusing. This option is asking to upload ALL files from out uploads directory with the exported static web site. I am not sure, I will just leave it blank and see what happens. I am not sure someone would want to export all the uploads, probably just the ones they need, so it would have been nice to be able to choose which ones to keep with the static site.

wp static html output uploads directory

The next option is an option to include other files that the plugin may not find. I am not sure how the plugin wouldn’t be able to find these files. If this part is for identifying remote files that are included with our new static site, it may download them remotely, I am not sure yet. If they do, I suggest not using large files here. The next section is dealing with paths, go ahead and leave these default and run it.

wp static html output plugin pathsFirst Run

You can press the button near the bottom, under the export section.

wp static html output plugin export

Once exported you will see a textarea with some progress in it below (above it’s featured under “Export Log”).

wp static html output pluginAbove you can see the path to our download, so let’s see what we have. If you move into the directory and look at what’s in there now you will see a symlink, the new directory and the zip file with our static site.

wordpress to static html unixSo let’s see if we can visit the site and see how it looks. I used a client’s website to try this out on. When I visited the link (in my uploads folder) I was disappointed to see the images are broke, and it also doesn’t look like it included CSS or Javascript files.

static site from wordpress

So let’s see what went wrong, it must be a configuration issue. Below you can see the paths that are messed up, which is a result in a bad configuration of the plugin before we exported it. I also see the path has a -admin pre-pended to the file’s name.

Conclusion

I decided to stop here. The configuration has issues and doesn’t give much of a “how to” to use the plugin’s configuration options. You can’t leave the fields blank, and if you do it doesn’t work. Hell, it didn’t work after I configured it and unzipped it to it’s own directory on my servers www directory. I think that if the plugin is going to export the files to a zip, when you unzip it it should work. Do not use this in a production environment.

Leave a Comment

Your email address will not be published. Required fields are marked *