WooCommerce 3.4.7 is now available. This is the last WooCommerce 3.4.x release, and it patches a couple issues introduced in WC 3.4.6 on certain site setups. ~9 commits made it into this release and the full changelog is below.
* Fix - Simplify importer file path check to cause less issues. #21573
* Fix - Better role checking for user editing capabilities. #21569 #21575
New and improved reports
Improved notification experience and improved store management tools
A brand new dashboard
While it isn’t ready for use on production sites, we are developing the new interface publicly so our developer community can comment and contribute, and are starting to make certain features available as a feature plugin.
Read on for why we’re working on the new interface, when to expect public beta (and inclusion in core), and what to look forward to from the new and improved WooCommerce experience.
Earlier this year, leveraging some of the power and potential of Gutenberg, we released a Product Block to make it easier to embed products within your WordPress site. It’s currently active on more than 40,000 sites with upwards of 100,000 downloads.
Whilst we plan the next blocks — for example, to help store builders to create landing and marketing pages more easily — we’ve also been working on a brand new interface enabled by the arrival of React in WordPress core.
New and Improved WooCommerce Reports
Our first step was to overhaul the existing reports. The existing reports are cumbersome to use and significantly less valuable to users than they could be with internal usage data showed that very few merchants even look at their reports.
Because the reports haven’t been extended much by our extension developers (partly because we didn’t make that easy for you and partly because we haven’t provided the right components to make reports valuable to merchants) they were a simple starting point, too.
There are nine reports we’ll be working on to help merchants better understand their stores. And, we’ll be introducing a new report for product variations – one of the most requested improvements we’ve had for our core product.
The new reports will be a huge improvement on the existing reports, merchants will be able to:
Quickly filter data.
Compare date periods, finally.
Have easy access to the data points that matter.
Download reports in CSV format.
Your Brand New WooCommerce Dashboard
We’re building a new dashboard that will be the default landing page when you visit WooCommerce. Merchants will be able to see at a glance how their store is performing and control what they see, and the dashboard will be extendable by developers.
For the dashboard, we’ll be using design patterns found in Gutenberg to allow merchants to add and remove blocks from their dashboard.
An Improved Notification Experience
Finally, we’re working on what we’re calling the Activity Panel that provides merchants with new store management tools, no matter where they are in their store.
Merchants will be able to:
Manage store notifications.
With regards to notifications: Within the Activity Panel, we’re working on an Inbox where our merchants will have an improved user experience when dealing with notifications – a widespread WordPress problem we’re attempting to solve for WooCommerce merchants.
There will be an API and new REST API endpoints for developers to add notifications from their extensions and, as with everything we take on, this will all be responsive.
How to Test The New WooCommerce Interface
We’d love our developer community to start putting the code through its paces. While you shouldn’t use the plugin on a production site, you can install it on a developer environment to see what we’ve created.
Read the installation instructions. We’ve also started documenting the new project here.
Report any issues or questions you might have on the public repository on Github.
What to look out for:
We’ve wrapped up the Revenue Report and Orders report – two new reports that will replace the existing Sales Report available in core. We’ve created a sample report so you can understand how you would create your own reports for your extensions or clients.
We have one block working that displays Top Selling Products in the new dashboard and the Activity Panel can be seen. We’re currently working on the APIs to power the Inbox that developers will be able to integrate with.
You’ll see wc-admin in action! We look forward to hearing what you think.
When to Expect Public Beta
The plugin is currently in alpha – meaning you shouldn’t use it on production sites – while we complete the feature set to take us to beta. At beta, we’ll be releasing the plugin on WordPress.org and WooCommerce.com for wider use amongst our community.
As of now, we expect beta to land early 2019 and aim to have the new features merged into core within Q1 of 2019.
We’re using a sprint system to build our plugin, and going forward you can expect a new post on this blog every two weeks with the latest developments of the plugin.
Have feedback for us? We’d love to hear your thoughts through comments or open an issue on the repository here.
We have delayed the release of WooCommerce 3.5 by one week in order to do extra testing and QA on the release. The testing regimen for WooCommerce releases is very thorough and covers a variety of servers, and themes, and running the prerelease version in staging and production on live sites. This will help ensure the upcoming release is a smooth upgrade for all stores before the busy holiday season.
The new release date for WooCommerce 3.5.0 is October 23rd.
* Fix - Fix warning when using logger instance in woocommerce_logging_class filter. #21448
* Fix - Use uppercase "ID" when sorting product queries by ID. #21461
* Fix - Consistently escape the gateway ID in the checkout payment method template. #21439
* Fix - Avoid treating HTTP 301 and 302 codes as failures for webhooks. #21491
* Fix - Add address_1 to shipping packages info in WC_Cart:: get_shipping_packages to make it work correctly in address formatting functions. #21493
* Fix - Don't fire two of the same action when saving shipping settings. #21494
* Fix - Remove double condition for address line 2 in `WC_Countries::get_default_address_fields`. #20629
* Fix - Correctly handle shorthand values for memory_limit in php.ini. #21557
* Fix - Product shortcode numeric term slug matching. #21560
* Fix - Remove the erasure tools links from the descriptions of the erasure settings for users without the manage_privacy_options capability. #21565
* Fix - Don't double urldecode posted variation attributes. #21570
* Fix - New helper functions wc_user_has_role and wc_current_user_has_role to correctly check user roles. #21569