WP Bootstrap 0.3.0 released

The most of Christmas celebrations is behind us and in the wake of it all, some time was available to get WP Bootstrap 0.3.0 out the door.

What’s new in 0.3.0 ?

The single most important feature of 0.3.0 is that it introduces the concept of manifest files. So far, it’s really only used for taxonomies, but the general idea will be used for all content types. A manifest file is created when content is exported from a WordPress installation and contains some of the configuration that was used to create the export. During import, data from the manifest file is used to tune the import better.

0.3.0 also introduces the concept of “postid” taxonomies. Some plugins and themes uses taxonomies to tie different post types together using carefully named terms. One of the most popular sliders uses a custom post type “ml-slider” to represent a slider, so that each slider is a post of the “ml-slider” custom post type. Then it creates a term in a custom taxonomy, also named “ml-slider” with the same name/slug as the slider post ID and “tags” attachments (aka images) to that slider using that taxonomy term. In order to successfully export and import this, WP Bootstrap now handles “postid” taxonomies in a way so that even if the slider post has a different ID on the target system. the taxonomy term is renamed accordingly.

Refactoring and testing

Code quality is one of the most important aspects of WP Bootstrap development, so a lot of time was spent on refactoring code and making sure code coverage remains high. All testing activity is done in a separate github repo just for testing. If you want to contribute to WP Bootstrap, this is where I recommend you start looking. The overall test coverage is currently at 86%. I believe that around 90% is a reasonable target to aim for until we get closer to a 1.0 version of the tool. Any contributions to WP Bootstrap are more than welcome, you can just send a pull request or better, shoot me an email first at: erik@wpessentials.io

Case studies and development process

In the next few days, a case study on how a simple one page WordPress site is managed using WP Bootstrap will be released. While creating that case study some additional bugs were caught and fixed which was good. I also realized the need to implement manifest in order to get the “postid” taxonomy handling in to place. Overall, I think that since WP Bootstrap is now somewhat competent in itself, using real world examples with popular plugins and themes might be the best way to uncover issues and challenges with the tool. The case study will be released on the blog within the next few days, so stay tuned.

New version of the eBook WordPress DevOps

While WP Bootstrap is going to consume a lot of time in early 2016 there’s another project that can finally get started. I’ve promised myself that once WP Bootstrap had a certain level of features, it’s time to update the WordPress DevOps eBook. The current version of the book, let’s call it 1.0, doesn’t even mention WP Bootstrap but instead talk about the concept of using Grunt and a set of  loosely defined PHP scripts to do the same work. With the 0.3.0 release of WP Bootstrap it can not only do everything those Grunt scripts could but it can do it better, so the work on next version of the book has officially started.

If you’ve already purchased the book on Leanpub, the next version is free and you will get notified when it’s ready for download.

Stay in the loop

A good idea if you want to stay in the loop is to subscribe to the newsletter, I promise you’ll be the first to know. If you sign up now, you’ll receive a PDF guide with some tips and techniques I use to identify options that needs to be managed using WP Bootstrap and WP-CFM. It’s an 8 page guide that describes how to use wp-cli and some other tools to understand what options that are the most important on your site.

[newsletter_signup_form id=2]




WP Bootstrap 0.2.8 released

Work with WP-Bootstrap is coming along quite fine. Since the last update, the version number have bumped from 0.2.2 to 0.2.8.


Monolog have been added for proper logging. Along with this, three new optional properties have been added to localsettings.json.

  • logpath: The path to the logfile. The file will be created if it doesn’t exist.
  • loglevel: Loglevel for the logfile. Uses one of the constants from the Monlog package; DEBUG, INFO, WARNING etc. See https://github.com/Seldaek/monolog/blob/master/doc/01-usage.md for more information. The default log level is WARNING, so if you specify a log path but no level, warnings and errors will be logged.
  • consoleloglevel: Log level for logging on the console (standard out), uses the same Monolog constants as loglevel. There’s no default for console log level, so if you don’t specify it, nothing will be logged to the console.

Media management

Also in recent releases, media handling has improved. First of all, media are included in exports if they are attached to a post. The new thing is that a featured image (that technically does not have to be attached) will also be included (and restored during import). Lastly, media that is referenced in the post text or in a widget or in a meta property of the post will also be included in the export process. When importing, these files are added to the media library.


Sidebars and widgets are now managed in the export and import process. This means.

Taxonomy terms

Last but not least. Taxonomy terms handling is much improved. Taxonomy terms no longer needs to be explictly mentioned in the export settings to get included, all that is needed is that a post is connected to a term or that a menu item refers to it. During import, taxonomy terms are added or updated and posts are tagged accordingly.



With all the above improvements, WP Bootstrap have now somewhat matured into a quite competent import/export tool for content aside from just being able to “bootstrap” an installation with plugins, themes. I’ve already been using this to do a few site migrations, like when moving content from my personal blog (http://erik.torgesta.com) to this one.

Curious? Take Wp-bootstrap for a spin, read installation instructions and most of what you need to get started over at the github page.

Questions? Use the comment field below and let me know what you think.

Next? I’ve got a post lined up that explains how to use Wp-bootstrap for moving content between installations. Stay tuned.