If you’d like to import the posts and pages and images from the Utility Pro Demo site, you can do that!
Finding The XML File
First you need to download the file. It has an XML extension and you download it here.
How To Import The Demo File
Go to Tools => Import while logged in to your Admin Dashboard.
Choose “WordPress” from the list.
Upload the file you downloaded above.
You will be asked to map the authors in the export file to users on the blog. For each author, you may choose to map to an existing user on the blog or to create a new user.
You will then have the choice to import attachments, so click on the “Download and import file attachments” box.
WordPress will import each of the posts, comments, and categories into your blog.
The purpose of the demo content is to setup your homepage widgets and watch the theme come together like the demo site. In addition, if you look a little closer at the post and page content, you will see a wealth of information. They are basically short tutorials on how to use the built-in theme styling to achieve a variety of looks.
For Personal and Professional (Developer’s Edition)
Yipee! We’ve just announced a new update for Utility Pro! But the question is, now what? How do I apply the update without losing my changes? Excellent question and exactly what this post is meant to answer. We propose the best way to update a Genesis child theme is manually applying the changes you would like to implement.
First, please know that updating is NOT required — this is purely optional as the changes are largely cosmetic styling and added developer feature support . In the event there is ever a security-related update that we recommend for everyone, we would notify you via email with specific instructions on what and how to update.
If you’d like to proceed, download the latest version of Utility Pro by logging into your account and click the “View Details and Downloads” link on the product entry. You’ll notice the links have been updated to reflect the latest version.
For new files (if any), you can drop those into your site taking note of the location within the theme folder structure.
For changed files applicable to your theme, we suggest comparing a local copy of the file that currently exists on your live site to the new version, using the diff tool of your choice. A couple of free tools you can use for this:
Online: Diff Checker – is a website that offers the ability to drag and drop each file you’d like to compare on the screen then click the Find Difference! button. Manually cut and paste any differences from the new version to your existing copy then upload to your live site.
Application: DiffMerge – is a handy cross-platform tool from SourceGear that I’ve used for years that you can download for OS X or Windows. This app gives you the ability to compare two files (or folders), and merge the changes individually from one file to another while viewing. After saving your local copy, then upload to your live site.
For Developer’s Edition Only
There are a few new modules included with your developer’s edition that need to be installed, or you will receive errors the first time you launch “grunt” at the command line:
To correct this, run the following three commands, one at a time until each one completes, and then you can resume business as usual by running “grunt”:
sudo npm install -g composer
sudo npm install grunt-contrib-copy
sudo npm install grunt-rtlcss
That’s all there is to it! Of course if you have any questions, we’re available to help – just fire off a support request.
I really enjoyed Carrie and Mika on the WP Development Workflow webinar series. Unfortunately though, my Macbook Pro was not feeling the nerd love that I was. I had several bumps in the road attempting to set up Node.js, Bower, Grunt and SASS. That said, I did eventually get everything working and thought I’d share a step-by-step list that others might find helpful.
Node.js – I downloaded the latest version via an OS X install package from the web site . The first go-round I also installed Homebrew but realized I didn’t need both.
npm – Per the webinar instructions, in Terminal I navigated to the Utility Pro project folder and ran: npm install. (Remember, this is because it needs the content of that package.json file to know what to run.) This will take awhile as it’s going to load a LOT of files. You might get some warning messages about some version of this or that being deprecated and you should get a new version — I found you can ignore these. Since they are warnings, it will continue with the script and in the end I didn’t have to update anything to get this working.
Bower – Per the next instructions, I tried to run npm install -g bower and received many Permission Denied errors. FYI, the -g means you are installing for global access, meaning it can be accessed from any directory on your machine. To get that to work you need to execute the command as an administrator, or sudo. I re-ran the command but placed sudo in front: sudo npm install -g bower , it prompted for my password (for my Mac), I entered it and it completed successfully.
If you’ve never done this its a little weird in that while you’re typing your password, the cursor doesn’t move, but it is recording your keystrokes so never fear, press enter when done entering your password and it will continue.
Grunt – Now is the big moment! Time to finally run Grunt….I type it in and alas I get the error message -bash grunt: command not found Argh! I started Googling and some posts said to make sure everything is up-to-date and provided a command to do that: sudo npm update -g npm . This appeared to run OK but at the end it had several messages that started with npm WARN EBUNDLEOVERRIDE Replacing bundled npm > -some package- with new installed version. Well, this set of warning messages were not OK to ignore. So, bottom line: DO NOT DO THE UPDATE. So what now? I Google’d some more about my original command-not-found error and ended up at the Getting Started link for Grunt. This talked about installing the Grunt CLI (command line interface) globally (need to use sudo) which means it will put the grunt command in your system path, thus allowing it to be run from any location. Remember, Grunt is package/project specific so you may have that installed in any number of sites. NOW this was starting to make more sense. The command to enter is: sudo npm install -g grunt-cli
Sass – So after I installed the Grunt CLI, I typed grunt at the command line and it was doing something, yay! It said something about Bower components and that it re-created the file “style-rtl.css”. Then it said Running "sass:dist" (sass) and it aborted from warnings: Warning: You need to have Ruby and Sass installed and in your PATH for this task to work. More info: https//github.com/gruntjs/grunt-contrib-sass USE -- force to continue. Oh brother, more files missing 🙁 but never fear, you’re almost there! Next step, use the link in the error message which took me to a github README.md file. In there under the SASS heading it repeated — you have to have Ruby and SASS installed for this to run. Well since I’m on a fairly recent Mac, it’s going to have Ruby but I made sure by entering ruby -v in terminal and that checked out. You need that so you can do the next, and final (I promise) task to run which is installing SASS. Funny considering all this was to use that in first place 🙂 So back in terminal, with sudo (your password) enter sudo gem install sass and that to load SASS and you are done. Now go back and enter grunt it will list any partial files that changed, mention that its re-generating new style-rtl.css and style.css files, and it will end with “Waiting…” now you are golden!