Version 1.0.0 (Release Candidate 3)

This is the third release candidate for version 1.0.0 of the WooCommerce Custom Orders Table plugin.

Changes since Version 1.0.0 (Release Candidate 2)

• Ensure the orders query is adjusted as late as possible (#126).
• Update the plugin license to GPLv3+ to match WooCommerce core (#123).
• Define the compatibility policy for the plugin with regards to WordPress, WooCommerce, and PHP versions (#120, #127).
• Introduce PHPStan for static code analysis (#116, #117, props @szepeviktor).
• Refresh and update Composer configuration and dependencies (#121, #124).

Version 1.0.0 (Release Candidate 2)

This is the second release candidate for version 1.0.0 of the WooCommerce Custom Orders Table plugin.

Upgrading

There have been breaking changes since the last release candidate. It's recommended that sites deactivate and reactivate the plugin after upgrading to ensure changes are reflected!

Additionally, the database schema version will be locked until 1.0.0, so you may need to delete the "wc_orders_table_version" option from your database:

$ wp option delete wc_orders_table_version

Changes since Version 1.0.0 (Release Candidate)

• Reduced overhead of PHP autoloader (#86, props @schlessera).
• Converted the customer_user_agent column from varchar(200) to text (#91).
• Fixed an issue where empty() was being called on a non-variable, which causes a fatal error in PHP < 5.5 (#94).
• Prevented empty strings from being saved to the order_key column, which causes issues with the column's uniqueness constraint (#101, props @crstauf).
• Fixed an issue where existing invalid emails in the system were causing migration errors as they were re-saved (#104).
• Updated Travis CI testing matrix to include WordPress 5.0 (#103).
• Repaired the generation of code coverage reports for Coveralls (#87, #88).

Version 1.0.0 (Release Candidate 1)

This is the first release candidate for version 1.0.0 of the WooCommerce Custom Orders Table plugin.

Upgrading

There have been breaking changes since the last release. It's recommended that sites deactivate and reactivate the plugin after upgrading to ensure changes are reflected!

Additionally, the database schema version will be locked until 1.0.0, so you may need to delete the "wc_orders_table_version" option from your database:

$ wp option delete wc_orders_table_version

Changes since Version 1.0.0 (Beta 3)

• Major refactoring of the WP-CLI migration commands (#61, #79, #81).
• Database table optimizations (#65, props @Raunak-Gupta).
• Prevent duplicate IDs when saving orders and refunds (#64).
• Ensure that order refunds are also stored in the custom orders table (#52).
• Ensure the custom orders table is registered within WooCommerce (#50).
• Resolve issue in CLI importer where a false value from wc_get_order() could cause a fatal error (#43 & #46, props @zacscott).
• Fix bug where orders with the same post date could be handled in the wrong order during migration (#84).
• Prevent customer notes from being deleted during migration (#82).
• Bump the "WC tested up to" version to 3.5.0 (#80).
• Major refactoring within the plugin test suite (#51, #53, #60, #72, #78).
• Prevent Travis CI from using PHPUnit 7.0 until the WordPress core test suite can support it, too.

This release also restores the repo development history prior to Version 1.0.0 (Beta 1), ensuring that the team @Mindsize is credited appropriately for their work.

Version 1.0.0 (Beta 3)

Please be aware that this software is in beta, and running the plugin on a production site may have adverse effects.

Changes since Version 1.0.0 (Beta 2)

Note: There have been breaking changes since the last release. It's recommended that sites deactivate and reactivate the plugin after upgrading to ensure changes are reflected!

• Plugin test suite now extends the WooCommerce core test suite, ensuring WooCommerce behaves as expected when the plugin is active (#26).
• The custom data store now extends the WC_Order_Data_Store_CPT class, eliminating a lot of code duplication in the process (#28).
  • Includes areas that were previously missing, including reporting.
  • Plugin should now have 100% compatibility with default WooCommerce functionality.
• Removed the dependency on a Composer-generated autoloader (#36).
• Revert database columns to use VARCHAR types for compatibility with WordPress post meta tables.
• Add table indexes on the order_key, customer_id, and order_total columns in the orders table (#15).
• Refactor the WP-CLI command, including some changes to accepted arguments (#35).
• Normalize the plugin name around "WooCommerce Custom Orders Table" (#38).
• Added changelog and contributing documents (#12).
• Massive improvements to test coverage and general WooCommerce compatibility.

Version 1.0.0 (Beta 2)

Note: This release was previously labeled as v1.0.1-beta.2 by mistake.

Please note that this software is in beta. It is not a very good idea to run this plugin on a production site without an idea of some of its current issues.

While this release of the plugin is active on a site:

• WooCommerce reports will not generate as they expect data to be in wp_postmeta instead of custom tables.
• Order totals may not display correctly in wp-admin.

Our development team is working on fixing both of these outstanding issues and will prepare further releases as they are resolved.

Changes since Version 1.0.0 (Beta 1)

• Clean up codebase to adhere to the WordPress coding standards, and introduce an .editorconfig to make this kind of change less likely in the future (#8)
• Introduced automated unit tests via the WordPress core test suite (#9)
• Fixed bug where custom database table was not being created upon plugin activation (#5, #9)
• General documentation updates (#2)

Version 1.0.0 (Beta 1)

Please note that this software is in beta. It is not a very good idea to run this plugin on a production site without an idea of some of its current issues.

While this release of the plugin is active on a site:

• WooCommerce reports will not generate as they expect data to be in wp_postmeta instead of custom tables.
• Order totals may not display correctly in wp-admin.

Our development team is working on fixing both of these outstanding issues and will prepare further releases as they are resolved.