WooCommerce 3.4.2 is now available.~32 commits made it into this release and the full changelog is below.
* Fix - Flexslider gallery fixes for RTL sites, and for variation image switching. #20328 ##20321
* Fix - Allow forms to be submitted when the password strength library fails to load. #20362
* Fix - Personal data exporter: Do not export a customer data group containing no data. #20347
* Fix - Fix navigation notification in settings when clicking save. #20335
* Fix - Show discount amount for free shipping coupons. #20334
* Fix - Fixed cache clearing for category children for sites running object caching. #20308
* Fix - Use correct escaping on select2 placeholders. #20364
* Fix - Order by price clauses when searching within terms. #20391
* Fix - Clear needs_processing transient when adding a product to an order. #20390
* Enhancement - Permission_id constraint checks on install. #20366
* Dev - Added order to "woocommerce_order_is_vat_exempt" filter arguments. #20365
* Localization - Disable states for Bahrain. #20363
* Localization - Disable states for Luxemberg. #20389
WooCommerce 3.4.1 is available.~61 commits made it into this release and the full changelog is below.
* Fix - Fix webhook admin filtering URLs. #20236
* Fix - Add missing wp_unslash calls to product data meta box to prevent quote characters being escaped on save. #20235
* Fix - Display price filter widget in LTR mode on RTL sites. #20221
* Fix - Refactor WC_Coupon constructor to allow for passing in coupon objects. #20193
* Fix - Path field in advanced CSV importer was broken due to an esc_url call. #20191
* Fix - Prevent shipping method instances trying to save settings on non-instance screens. #20217
* Fix - Wrapper function to get full mysql version string with mariadb handling. #20231
* Fix - woocommerce_pagination had some extra white space. #20214
* Fix - If a file size cannot be read, ignore range headers to prevent offsite downloads being 0kb. #20205
* Fix - Allow HTML when using `wc_attribute_label()`. #20202
* Fix - Update address-i18n.js to prevent appending multiple "(optional)" labels. #20195
* Fix - Check plugin properties exist when listening to auto_update_plugin hook. #20234
* Fix - Add extra checks in `get_canonical_package_rate_ids` to prevent notices. #20237
* Fix - Fix infinite loop with importing tax rates. #20253
* Fix - Echo attribute label for "empty" default option. #20256
* Fix - Fix download sample tax rates URL format. #20272
* Fix - Product properties should not be accessed directly PHP notice when calling `wc_get_product_attachment_props`. #20282
* Fix - If flexslider is disabled, gallery images also need to trigger photoswipe on click. #20290
* Fix - Product import file uploads on windows servers. #20273
* Fix - Fix variation attribute selection via the cart page/query string. #20293
* Fix - Add greater specificity to required styling in 2017 theme. #20296
* Enhancement - Export legacy paypal meta data in personal data exporter. #20200
* Enhancement - Improve performance of `wc_update_340_states` update routine to help prevent timeouts. #20241
* Dev - Remove red styling for PHP notice if using > 5.6. #20294
* Dev - Add an action hook after printing the cart item name. #20190
* Localization - Use "payment tokens" terminology in exports. #20197
Fixed terms and conditions preview when the terms and conditions option is unset.
Change token export format to match WordPress 4.9.
Updated some missing template file versions.
Use GET in external product form so query strings are preserved.
Escape and decode ampersands correctly for external products.
Preview checkout without a dummy product to prevent conflicts.
Remove . from strings for checkbox settings.
Data erasers; target shop_order only and added filters for 3rd parties.
Remove legacy PayPal meta data from orders.
When cleaning up CSV import, only remove product taxonomies. #20094
And we’ve added the following to the changelog as it affects older versions also:
* Tweak - In CSV exports, wrap cell in ' rather than just prepending to escape values. #20041
* Tweak - Add JS listeners for reloading/reinitializing order items in edit-order page. #20082
* Fix - When duplicating variation, set the date to null. #20083
* Fix - Fix rounding of line items for orders to match cart. #20086
* Fix - Remove hardcoded border in email template. #20090
* Fix - Prevent autofocus on checkout. #20123
* Fix - Recalc taxes if address changes in API. #20137
* Dev - Made wc_query_string_form_fields handle strings. #20162
* Localization - Fix missing Bahrain country code. #20061
This post summarises the changes and features you’ll find in our 3.4 release scheduled to drop May 23rd.
Personal data exporter
WordPress 4.9.6 includes both the ability to export personal data associated with an email address to a HTML file. WooCommerce 3.4 will add to the generated export file, exporting the following data:
Customer address/account information
Orders associated with the given email address
Download permissions and logs associated with the given email address
To ensure requests are genuine, 4.9.6 includes a requests table and confirmation email to verify the request. The verification flow consists of the following steps:
Add an email address or username.
The user is notified via email with a confirmation link.
The confirmation link is used and the request is marked “confirmed”.
Admin triggers an email to the user which contains a link to download their personal data.
Personal data files can also be manually generated by the admin and downloaded. The file itself is a simple HTML file, zipped.
WordPress exports it’s own data in the same way, so things such as media files, posts, and comments/reviews are also taken care of!
Personal data eraser
Like the exporter, the eraser allows you to verify requests are legitimate before fulfilling them. It uses the same verification/email/requests system as the exporter.
We understand this can be slightly more complicated with stores because you may need to keep data for other reasons, such as tax compliance or compliance with other laws.
With that in mind, we have made some of our erasure routines optional:
These settings are off by default.
Additionally, if you ever delete a user manually, we’ve improved our cleanup functions so that the following data is removed along with the user:
Orders (are converted into guest orders)
And if you need to manually anonymise orders in bulk for a user you can search for them in admin and use the new “remove personal data” bulk action:
This keeps the order around, but removes all personal data and converts the order into a guest order.
Data retention settings
To help reduce the amount of personal data that’s stored, WooCommerce 3.4 allows you to define how long you want to retain data that is no longer needed for order processing:
These settings are found in WooCommerce > Settings > Accounts and privacy.
Failed, pending, and canceled orders which get cleaned up will be moved to the trash.
Completed orders which get cleaned up will be anonymized so sales stats are unaffected.
Inactive accounts will be deleted. An inactive account is one which has not been logged in to, or which has not placed orders, for the specified time.
If enabled, cleanup will run via a daily cron job. Inactive accounts are tracked using meta data, and only subscribers/customer accounts are removed. An upgrade routine will set all account last active times to the time you updated to 3.4.
Checkout page display options
To reduce the amount of personal data stored you can turn off some optional fields you may not require for processing.
Additionally, you can now change the terms and conditions checkbox text to meet your needs:
Both of these options can be found in the Customiser (Appearance > Customizer > WooCommerce > Checkout) and the preview is live so you can see what effects these changes will have on your checkout before hitting publish.
WordPress 4.9.6 includes a privacy page setting as well as a mechanism for plugins to suggest content. WooCommerce adds some suggested content of it’s own.
Other plugins can do the same which should allow you to piece together a policy which applies to your users.
Account registration form
The notice in the case of the checkout is shown above the place order button automatically:
Both notices can be customised in WooCommerce > Settings > Accounts and privacy or the Customiser.
Changes to log files
We’ve made some changes to our logging system in core, as well as revised what data gets logged.
We’ve done an audit of our usage of logs in WooCommerce and removed any unnecessary personal information from the logs. Notably:
Webhook logs no longer log the webhook body and response unless WP_DEBUG mode is turned on. This avoids personal information sent with webhooks being logged to the server.
PayPal debug logging no longer logs the personal data sent to PayPal and masks it out. The setting itself now includes a disclaimer that it should be used for debug purposes only and should be disabled when complete.
For PayPal specifically, payer email/name is no longer logged within order meta – this information can be found using the transaction ID and visiting the PayPal website instead.
When PayPal debugging logging is turned off, the logs are purged.
Logs will now rotate daily, and log files will be deleted after 30 days by default. A filter can be used (woocommerce_logger_days_to_retain_logs) to extend this if needed. The cleanup is performed using a cron job.
These changes apply to both file based logging, and database based logging, which are both options within WooCommerce core.
The above features will require both WooCommerce 3.4 and WordPress 4.9.6. Both will be released before the May 25th GDPR deadline. If you’re interested in testing WooCommerce 3.4, see our beta announcement here.
It’s important to note that this new law doesn’t just apply to stores in the EU – this applies globally to stores that sell products to EU residents.
We’re currently building new tools into our upcoming 3.4 release to help store owners deal with GDPR requests and surface things such as privacy policies on the checkout. Some of the tools are built already, or are in progress, notably:
Better formatting for inline descriptions should someone which to include just in time privacy text next to fields, and some simple tools to toggle non-critical fields off to avoid unnecessary data collection.
Custom terms and conditions text, and control over the checkbox + label itself.
We’ve cleared up wording around the tracker in the Wizard to ensure it’s compliant.
Open GDPR issues can be tracked here. One thing not yet completed is personal data export, which is arguably the most important thing we need to assist store owners with. To solve this, we’re working to bring these tools to WordPress core. Read on for the details.
The road to WordPress core compliance
Rather than create something proprietary, or specific to WooCommerce, our team is focussing on WordPress core contributions so that all users and plugins can benefit from a single, unified system in WordPress itself. We feel this is the most effective use of everybody’s time.
To that end, we’ve started on several new screens and functions for WP core which (if approved) will facilitate user requests and create export files of personal data.
Here are a few of the tickets we’re actively contributing to:
Way for users (and guests) to request personal data and/or removal
Managing requests, for example requests for personal data, needs some kind of UI or system to track who did the request, the status of the request, and the date of the request. GDPR requires that requests are responded to within 30 days.
To help with this, we’re creating a requests system within WordPress to deal with this.
The UI shown above has been submitted as a patch in #43481. The basic flow in the v1 is as follows:
User makes request via contact form or some other method of contact.
Admin adds the request via the WordPress dashboard.
User verifies the request.
Admin triggers a response to the request e.g. by sending the data they requested.
Request is either kept for tracking purposes, or removed.
To ensure the user is really who they say they are (remember emails can be spoofed!) we created a mechanism whereby WordPress will send a confirmation email to the user with a link they can click to confirm any action. This is similar to the “change password” flow in WordPress, but more general. This has been submitted via #43443.
Requests can be tracked and can have the following statuses:
Thats it! If merged, we’ll move on to the ‘next steps’ column which will include buttons and links to send export files and so on to the requester.
The personal data export system
The next part to this is the actual export file generation. This will export all personal data tied to a specific email address in a human readable format.
How this works technically is:
A WordPress endpoint is hit, and a filter is ran to gather a list of data exporters from various plugins and core itself.
Each data exporter is called and the exporter from each plugin returns personal data based on a given email address.
Exporters support pagination, and each call is done in a separate request to prevent timeouts.
All of the data is appended to an export file. This is then served to the admin.
The main trac ticket for this is #43438. This fires the actions and filters for plugins to use. This prototype works with our in progress implementation in WooCommerce here.
Another related ticket is #43440 which puts WordPress comment data into the export.
Finally, #43551 improves how the export is served to the admin; as a HTML file within a zip file which is portable and human readable!
What else is being worked on in WordPress core?
Some other tools being made inside WordPress include: