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.
- Next, identify the files that have changed.
- Before making any changes, BACK UP THAT SITE !
- 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.