• Storefront 2.5.0 has just been tagged for release and uploaded to WordPress.org. That means it should be available to download very soon!

    While 2.5 is not a major release, you should not update live sites without adequate testing on a staging site. If you are using any additional Storefront products (child themes and/or extensions) be sure to check for updates for them before updating Storefront.

    What’s in the box

    In version 2.2 we introduced support for WordPress 4.7’s Starter Content feature, a feature that provides a much richer experience when installing Storefront.

    In 2.5 we are expanding this feature to include a custom editable homepage using WooCommerce 3.6 blocks, and also the updated cover block introduced in WordPress 5.2.

    For most of its existence Storefront has included a “Homepage” custom template. While this provided a solution to a problem, any kind of customizations to the configuration of this template were only possible via plugins or custom code.

    Now with Gutenberg and the new WooCommerce blocks, creating custom homepages couldn’t be easier.

    Here’s what’s changed pulled directly from the changelog:

    * Feature - Updated Starter Content to make use of WooCommerce 3.6 blocks, and also the new cover block introduced in WordPress 5.2, to create a custom editable homepage.
    * Tweak - Added edit link to post, pages, and products.
    * Fix - Prevent overlap of site title and handheld menu button when not using a logo image.
    * Fix - Added error styling to T&C checkbox and Country select in the Checkout page.
    * Fix - Ensure all inputs use accent color set in the Customizer.
    * Fix - Don't show sticky add to cart if product cannot be purchased.
    * Fix - Added margin to view cart link in the "Added to cart" notice.
    * Fix - Replaced CSS calc with Sass math when calculating block gallery column widths for better compatibility with IE11.
    * Fix - Change color and size of "remove" icon in the Cart page.
    * Fix - Change product pagination z-index for compatibility with PhotoSwipe.
    * Fix - Fix double scrollbar when original length of the mini cart surpasses the end of the page.
    * Fix - Move all Gutenberg assets to Gutenberg hooks.
    * Dev - Updated Composite Products integration for compatibility with version 4.0.
    * Dev - Updated FontAwesome to 5.8.1.

    You can download Storefront now from your dashboard or from WordPress.org.

    I found a bug

    If you find a bug then as always, please be sure to report it on GitHub. If you have any other problems with Storefront please post on the WordPress.org support forum, or contact us if you’re a WooCommerce customer.


  • Storefront 2.4.6 has been tagged for release and uploaded to WordPress.org.

    Here’s what’s changed pulled directly from the changelog:

    Fix - Sort homepage template categories by `menu_order` instead of `name`.
    Fix - Remove menu transition when no menu is assigned to primary location.
    

    Download the latest release of Storefront here or venture over to Dashboard → Updates to update your theme from WordPress.

    As usual, if you spot any other issues, please log them in detail on Github.


  • WooCommerce 3.6.2 is now available. This release fixes backwards compatibility with themes, a conflict with WooCommerce Blocks 1.4.0, and more.

    (more…)

  • Greetings all once again! While WooCommerce 3.6 was just launched less than a day ago, we received reports via GitHub and the Support Forums that some of the new functionality shipped in 3.6 was causing issues with some hosting environments.

    As such, we have opted to revert the code that was determined to be causing issues back to the version that exists in 3.5.x. We have taken that one revision, and packaged it up in version 3.6.1 to allow sites affected to easily apply the fix.

    3.6.1 Changelog

    With just one pull request shipped in this fix release, the changelog is quite short:

    * Fix - Remove calls to 'header_register_callback' to prevent conflicts with some hosting providers and PHP versions.

    This change will fix the issue users on WPEngine hosting were experiencing on logging in to wp-admin, and remedy the issues reported around add-to-cart URLs in 3.6.

    Download the latest release of WooCommerce here or venture over to Dashboard → Updates to update your plugins from WordPress.

    As usual, if you spot any other issues in WooCommerce core please log them in detail on Github, and to disclose a security issue to our team, please submit a report via HackerOne here. Comments on this post are closed.


  • Today we are excited to announce the availability of WooCommerce 3.6. The latest release of WooCommerce has been in development since November 2018, and during that time, 3.6 has had 2279 commits from 122 contributors.

    3.6 is a “minor” release; this version should be backwards compatible with sites running versions of WooCommerce greater than or equal to 3.0. We do of course recommend ensuring your extensions and themes are compatible before upgrading, and making backups for peace of mind —please see this guide for more details.

    (more…)

  • Greetings all! WooCommerce 3.6 RC2 was released last week, and since then a few small bugs have been discovered. Also with the security updates released in 3.5.8 today – we wanted to bundle up one last Release Candidate prior to the official planned launch of WooCommerce 3.6 tomorrow – April 17th.

    What’s New

    In addition to the security fixes in 3.5.8 – the following items have changed since RC2:

    • Fix: Product search may fail to return valid results when using the ‘include’ flag to search within a limited set. #23246 Props @franticpsyx
    • Dev: Update Action Scheduler library to 2.2.4 #23306 Props @JPry
    • Fix: Logic in link all variations #23304
    • Fix: Remove total revenue from usage tracking #23302
    • Fix: error in /wc/v2/system_status endpoint #23295
    • A11y: Change aria-labelledby to aria-label on quantity input #23186 Props @zacchaeusluke
    • A11y: Updates to labels in checkout #23303 Props @pojke
    • Fix: Replace update_woocommerce_term_meta with update_term_meta #23308 Props @webdados

    Testing

    To test WooCommerce 3.6 RC3, you can use our WooCommerce Beta Tester plugin or you can download the release candidate here (zip).

    Since 3.6 is now in release candidate stage, only bug fixes will be made. No other changes should take place.

    Think you’ve found a bug? Please post in detail to Github.

    Developers, 3.6 is a minor release, so it should be fully backwards compatible. Despite this, it’s still a good idea to test your plugins and themes and help us catch any issues we may have missed before the final release.


  • WooCommerce 3.5.8 is now available. Since this release contains fixes to harden security, we encourage you to update your stores as soon as possible.

    (more…)

  • On March 28th we announced the availability of the first Release Candidate for WooCommerce 3.6. During the RC1 testing period, a number of bugs were reported by RC testers in the community, and during additional internal testing. As such we just published a second release candidate for WooCommerce 3.6. To see all the new features being shipped in 3.6, please check out the Beta 1 post for all the details.

    Due to the addition of a second Release Candidate, we are anticipating the final release of WooCommerce 3.6 to happen on April 17th. We apologize for the added delay to this release cycle. Our number one priority is to ship a stable release, and we believe the extra time is needed to deliver on that priority.

    What’s New

    In addition to the changelog and feature list that was included in the Beta 1 Announcement – the following items have been fixed since RC1:

    • Fix BC break by allowing wc_product_gallery to be called without any arguments. props @superdav42 #23191
    • Fix strpos arguments order #23175 props @quasilyte #23175
    • Fix results from wp_term_counts when sorting by menu_order #23194
    • Fix: backwards compatibility issues for wc_get_template function #23197
    • Fix: Remove end date for Facebook in on-boarding wizard #23210
    • Fix: Usage tracking logic. #23231
    • Fix: Prevent removal of the wc- prefix from non core order statuses #23203
    • Fix: For conflicting webpack build processes #23244

    Marketplace Suggestions and Usage Tracking Feedback

    Beyond the fixes listed above, we also made some changes to the Marketplace Suggestions feature. It is often only when the release candidate actually comes out that we get certain kinds of feedback. Thanks to the many developers, end users, and the plugin review team for all their help.

    Now, with the 3.6 RC1 live, we have specific feedback from the community and plugin review team that we can take into consideration and act on:

    • Fix: Remove Product Listing suggestions. #23211
    • Fix: Add setting to turn off Marketplace Suggestions #23218
    • Fix: Add icon to Product Metabox Suggestions #23230
    • Fix: Add link to manage Suggestions #23229
    • Fix: Update text explaining opt-out and details of usage tracking. #23216

    Testing

    To test WooCommerce 3.6 RC2, you can use our WooCommerce Beta Tester plugin or you can download the release candidate here (zip).

    Since 3.6 is now in release candidate stage, only bug fixes will be made. No other changes should take place.

    Think you’ve found a bug? Please post in detail to Github.

    Developers, 3.6 is a minor release, so it should be fully backwards compatible. Despite this, it’s still a good idea to test your plugins and themes and help us catch any issues we may have missed before the final release.


  • We are happy to announce the availability of a new build of the WooCommerce Admin feature plugin! If this is the first time you have heard about WooCommerce Admin, it is a new JavaScript-driven interface for managing your WooCommerce stores that is focusing on creating new and improved reports, and a dashboard to monitor all the important key metrics of your site. You can read more about the background of the project in our Alpha announcement post – or watch the keynote from WooSesh.

    (more…)

  • The release candidate for WooCommerce 3.6 is now available! To see all the new features being shipped in 3.6, please check out the Beta 1 post for all the details.

    By publishing the release candidate ( RC ) – this signals that we feel 3.6 is ready for release – but we would love your help testing things out prior to the final release! We are still targeting to release WooCommerce 3.6 on Thursday, April 11th.

    What’s New

    In addition to the changelog and feature list that was included in the Beta 1 Announcement – the following items have been added since Beta 1:

    • Enhancement – Improved username generation and introduced wc_create_new_customer_username function. #23145
    • Dev – Update action scheduler to version 2.2.2. #23162
    • Fix – Download link URL in helper. #23146
    • Fix – Completed email wording update. #23128
    • Fix – REST API: Allow filtering by future status #23138
    • Fix – Update refund reason to make it clear process is manual. #23149
    • Fix – Hide stock status for variations when the parent is managing stock. #23069
    • Fix – Force variation product type in WC_Ajax::add_variation. #23131
    • Fix – WooCommerce writes current_theme_supports_woocommerce option on every regular page view. #23035
    • Fix – Update the rating request text in the footer to be friendlier for screen reader users. #23039
    • Fix – Null check variable before accessing its properties on checkout page. #23047
    • Fix – Recognize all input fields with ID for checkout fields. #23050
    • Fix – Avoid regenerating thumbnails on every page load. #21800
    • Fix – Changed ‘private’ methods on WC_Breadcrumb class to ‘protected’. #23057
    • Fix – Jumping to top of page when dismissing store notice. #23066

    Testing

    To test WooCommerce 3.6 RC1, you can use our WooCommerce Beta Tester plugin or you can download the release candidate here (zip).

    Since 3.6 is now in release candidate stage, only bug fixes will be made. No other changes should take place.

    Think you’ve found a bug? Please post in detail to Github.

    Developers, 3.6 is a minor release, so it should be fully backwards compatible. Despite this, it’s still a good idea to test your plugins and themes and help us catch any issues we may have missed before the final release.