In this article, we’ll cover some key things that you need to be aware when updating to the following themes:

  1. Jump Start 2.2+
  2. Gnar 1.1+
  3. Denali 1.2+

This is a major upgrade. Use caution and update responsibly. Have questions? Find where to get customer support for your theme.

General Notes

For everyone, here are some general notes to be aware of when updating.

1. FontAwesome has been updated to v5.

FontAwesome 5 is a very major upgrade from the Fort Awesome team.

It’s important to note that many icon names have changed and support for older icon aliases have been removed. If an icon on your website is flashing a ?! symbol, it means FontAwesome is working properly, but that icon name is not supported in FontAwesome 5. But in most cases, there is probably an alternative name; you can see a full list here.

Also keep in mind if you’re using other third-party plugins that incorporate FontAwesome 4, this may (or may not) have effects on the icons on your website. So just be aware of this.

2. Your theme options page has more options.

There were quite a few changes made to your theme options. Depending on your theme and current theme base, this will be different for everyone. While there’s nothing there that needs immediate attention, it would still be a good idea to quickly skim through and re-save it.

For the die-hards, if you skim through your theme’s changelog, every change is documented there. You can make use some of cool, new minor features.

3. Make sure you’re not using the Theme Blvd Sliders plugin.

Back in 2015, this plugin was removed as a suggested plugin with the Framework 2.5 update, and support for it was deprecated at that point. This Framework 2.7 update officially stops supporting it, and it’s best to make sure you’ve completely disabled it, if you happen to still be using it.

4. You must update your Theme Blvd plugins.

Like with any major theme release, there’s a good chance that some of your Theme Blvd plugins also required updates, as well, to be compatible. So make sure all of your Theme Blvd plugins are on their latest versions.

Developer Notes

If you’re making child theme code customizations, also give the following points a quick skim.

1. Template part files have been moved to a “template-parts” directory.

If you have template part files in your child theme, they must be moved into a directory named template-parts in order for them to continue working.

So for example, if your child theme contains a template part file like content-blog.php, it now must be located here:

/your-child-theme/template-parts/content-blog.php

2. It is possible for FontAwesome 4 icon names to work.

We strongly suggest that you update all of the icon names across your website to be compatible with FontAwesome 5. But if you need a temporary fix, you can add the following to your child theme’s functions.php until you have a chance to get them all up-to-date; this will provide a backward-compatible shim, allowing FontAwesome 4 icon names to work.

add_filter( 'themeblvd_icon_shims', '__return_true' );

Note: This was added in the minor Framework 2.7.1 update — Jump Start 2.2.1, Gnar 1.1.1 and Denali 1.2.1.

3. Deprecated action themeblvd_header_above has been removed.

If you’ve hooked anything to themeblvd_header_above, it will no longer display. Hook this content to themeblvd_header_top or themeblvd_header_content instead.

4. Website logo CSS classes have been restructured.

Often when CSS classes need to be re-structured or updated on an element, we’ll keep the old ones attached. Over time, this can become a cluttered mess of CSS classes in different formats. In this case, the logo was one of the worst examples of this. So while a tough decision, the logo HTML and CSS affecting it has been re-structured to help with some other changes in this release and some future features.

For those making child theme customizations, there’s a high likelihood that you added CSS to your website’s logo, and because this affects the website header, immediately after updating this can give some of you a reaction like, “Oh dang, my website looks completely broken.” But fear not; just quickly review any CSS customization you’ve made to your logo and update it to use the classes that are now outputted with it.

5. You can disable rich-text editing.

This release added direct rich-text editing throughout the layout builder. Many users and clients love it, but as a developer, if you’re the primary person making edits, you may want to disable it. Simply add the following to your child theme’s functions.php.

add_filter( 'themeblvd_do_rich_editing', '__return_false' );

6. You can expand rich-text editing.

While rich-text editing in the layout builder was made more easily accessible, it was also simplified for ease of use. However, if you’d like to customize the plugins and buttons included with the TinyMCE toolbar, you can utilize filters themeblvd_editor_tinymce_plugins and themeblvd_editor_tinymce_toolbar.

For example, the following added to your child theme’s functions.php will get the Visual editors looking more like the default WordPress editor.

https://gist.github.com/themeblvd/29745ee2d0b583bac3398f0b019dce1a

Note: This was added in the minor Framework 2.7.2 update — Jump Start 2.2.2, Gnar 1.1.2 and Denali 1.2.2.

7. Here’s a complete list of all the significant code changes that were made, which could potentially affect child theme customization.

  • All PHP code now meets WordPress Coding Standards.
  • All function, action, and filter comments now meet WordPress’s PHP Documentation Standards.
  • All template part files were moved from the theme root to a template-parts directory; if using any template parts in your child theme, make sure you also move these into a template-parts directory!
  • New template parts added, that can be copied to your child theme:
    • /template-parts/content-head.php — Edit the website <head>.
    • /template-parts/content-header.php — Edit the desktop website header content.
    • /template-parts/content-mobile-header.php — Edit the mobile website header content.
    • /template-parts/content-sticky-header.php — Edit the sticky header content.
    • /template-parts/content-footer.php — Edit the website footer.
    • /template-parts/content-panel.php — Edit desktop side panel content.
    • /template-parts/content-mobile-panel.php — Edit the mobile menu panel content.
  • Template part files content-template_archives.php and content-template_sitemap.php were renamed to content-template-archives.php and content-template-sitemap.php.
  • Mobile header is now a completely separate component from the desktop header.
  • Sticky header and mobile panel content can now be edited through template parts and/or action hooks; they no longer rely solely on JavaScript to be built.
  • Use of themeblvd_get_part() now deprecated; all instances of get_template_part() replaced with new themeblvd_get_template_part() wrapper function; all previous, related filters have remained in place and work as before.
  • Re-structured all admin CSS and JavaScript for better organization and efficiency.
  • The “Agent” theme base’s footer has become the default website footer across all theme bases. This means there’s new CSS applied to the footer in all other theme bases. And for the “Agent” base, it means that it has default framework functions hooked for the footer content (only affects Jump Start).
  • Your custom layout builder elements are now hooked to an action themeblvd_element_{$type} instead of just themeblvd_{$type}, to not conflict with filtering standard output of elements.
  • Deprecated the function themeblvd_responsive_menu_toggle(); use function themeblvd_mobile_panel_trigger() instead.
  • Added various security improvements.
  • Added action hooks themeblvd_header and themeblvd_footer, giving you control over these entire sections at the top-level. All previous actions hooks still exist within (except themeblvd_header_above).
  • Added filter to remove frontend debug info from printing in source code; just filter themeblvd_do_debug_info to return false.
  • Added filter to remove admin framework welcome message; just filter themeblvd_do_welcome_message to false.
  • Added filter themeblvd_sidebar_args added, which is shared with Theme Blvd Widget Areas plugin; this filters arguments passed to register_sidebar() for custom and theme widget areas.
  • Added filter themeblvd_element_{$type}_options to modify options for any element being outputted from the layout builder.
  • Added filter themeblvd_element_{$type}_display to modify display options for any element being outputted from the layout builder.
  • Added additional CSS classes to contact buttons and social sharing buttons, for more complex styling possibilities.
  • Added improved script and stylesheet debugging, when WordPress’s SCRIPT_DEBUG constant is set to true.
  • Added alt tags to parallax background image HTML output from the layout builder; you must re-insert and save your background image for the alt tags to start outputting.
  • Removed all “fancy selects” styling on admin UI select menus; we’re now relying on default WordPress styling.
  • Removed overly complex stylesheet API; all framework CSS files now enqueued through simple, pluggable function themeblvd_include_styles().
  • Removed old html5shiv for HTML5 compatibility with IE8.
  • Removed themeblvd_featured_* action hooks, which were deprecated in framework 2.5.
  • Removed responsiveness from the global configuration; it’s now assumed that your site will always be responsive.
  • Removed themeblvd_viewport_default() function, that was hooked to wp_head; now you can just edit content-head.php instead.
  • Removed the deprecated action hook, themeblvd_header_above; use themeblvd_header_content or themeblvd_header_top instead.
  • Removed the filter themeblvd_featured_thumb_frame to add old Bootstrap thumbnail border to images; use CSS customization instead.
  • Optimized (minified) CSS file included on frontend for each theme base (only affects Jump Start and Denali).