WordPress Coding Standard 2.0 removed the sniff
WordPress.Security.NonceVerification.NoNonceVerification:
```
The WordPress.Security.NonceVerification sniff used the same error code for both an error as well as a warning.
The old error code NoNonceVerification is no longer used.
The error now uses the Missing error code, while the warning now uses the Recommended error code.
```
(from
d45f5e5cf3/CHANGELOG.md (200-rc1---2018-12-31))
This commit updates WooCommerce code and replaces all instances where WordPress.Security.NonceVerification.NoNonceVerification verification was used with either WordPress.Security.NonceVerification.Missing or
WordPress.Security.NonceVerification.Recommended. In a few cases WordPress.Security.NonceVerification.NoNonceVerification was used but was not needed, so instead of replacing the sniff, the line was removed. In two other cases, I removed other unrelated sniffs that were not needed.
While creating an order, if we remove an item after adding, `pre_post_update` hook gets called. Since the order is not created yet, `$order->get_date_created()` will be null, and this will cause a fatal in the event tracker which checks for and tracks edit in order created date.
We now return early when order status is `auto-draft` to prevent these kind of errors.
* Check if current step matches event before firing
* Move step check to switch statement
* Track when the OBW has started
* Rename Jetpack activation tracking method
* Remove duplicate tracking optin check
* Track when option to track is udpated in OBW
* Check if tracking is actively being opted into in is_tracking_enabled()
* Move tracking start check into WC_Admin_Setup_Wizard_Tracking
* Clean up tracking opt-in check logic
* Check if current step matches event before firing
* Move step check to switch statement
* Add ability to get steps from setup wizard
* Track last completed step in options
* Track skipped step name if bypassing the save process
* Track skipped step prior to current instead of step after last completed step
* Add tracking to store setup OBW
* Check if current step matches event before firing
* Move step check to switch statement
* Track selected plugins recommended for install
* Check if current step matches event before firing
* Move step check to switch statement
* Track payment gateways in OBW
* Combine arrays into comma separate strings
* Add tracking to store setup OBW
* Check if current step matches event before firing
* Move step check to switch statement
* Extract save events into separate method
Christopher Allford
Rodrigo Primo
Claudio Sanches
David Stone
vedanshujain
Gerhard Potgieter
Paul Sealock
Timmy Crawford
Jeff Stieler
Joshua Flowers