You've read the benefits of Largo 0.6.1, and want to upgrade. We've tried to make the process as simple as possible.

Now is a good time to upgrade to WordPress 5.0, and to decide whether you want to enable the Gutenberg editor on your site. We have a post full of what you'll need to consider, and instructions for testing Gutenberg in our updated December 6 post: WordPress 5.0 and your news organization.

Whether or not you choose to update to WordPress 5.0, you should update your WordPress to the latest version in its release branch. Sites using 4.9, you should be on 4.9.9 already. And please, update your plugins.

If you're running Largo as your site's theme, your update process will be:

• Download Largo 0.6.1 from GitHub.
• Make a backup of your site.
• Upload it to your site's theme folder, replacing the current largo directory.
• Follow the instructions in your site's dashboard to run the database updates needed by the latest version of Largo.

If you're running Largo as a parent theme for your site's child theme, as many sites do, you should:

• Copy your site to a staging site (See instructions in the 5.0 blog post)
• Update the staging site's Largo, following the instructions above
• If your site has custom archive templates or custom template partials in the partials/ directory, check the changelog in Largo 0.6.1 to see what's changed since the last version of Largo your site used. You may also want to use GitHub to diff Largo 0.6.1 against your version of Largo; click the "Files changed" tab to see what changed from 0.5.5.4 to 0.6.1.
  • header.php
  • partials/archive-category-primary-feature.php
  • partials/archive-category-secondary-feature.php
  • partials/footer-widget-3col-default.php
  • partials/footer-widget-3col-equal.php
  • partials/footer-widget-4col.php
  • partials/nav-global.php
  • partials/nav-main.php
  • partials/sidebar-fallback.php
  • partials/widget-content.php
  • search.php
• If your child theme's custom templates use the largo_byline() function, you should read the upgrade notices in the Largo 0.6 release and ensure that you're passing a WP_Post or post ID as the third parameter.
• Remove any calls to the function largo_dashboard_member_news() and largo_fb_user_is_followable(); they're deprecated.
• Remove any <? short tag versions of the <?php tag; they're valid but discouraged and not all hosts support them.

If that sounds like a lot of things to check, we're happy to help you get updated. Send us an email at support@inn.org and we'll get back to you as soon as possible.

Note: The INN Labs team will be on break from December 21, 2018 to January 2, 2019. We'll be checking our inboxes for emergency support tickets, but may not get to other items until after New Year's Day.