Our beta3 release is fairly small compared to the other two, but it contains some pretty important bug fixes, which is why we wanted to make it available to anyone testing 3.0.
Important Note: This beta release is NOT production ready. It should only be tested on development sites. Do not install it on your live site.
We discovered that migrated order totals could be incorrect if the order had a fee applied that affected the entire order (as opposed to being linked to an individual item). This has now been resolved.
While fixing the fee issue, we also found a few problems when migrating data from very old versions of Easy Digital Downloads — we’re talking back to 2013. Back then, individual payments didn’t even store things like the subtotal or exact discount amount, and that led to unexpected results when the data was migrated to the 3.0 format.
Orders with discounts from that period still may not be perfect, but we’re confident we’ve done the best we can given the limited data from that era. It won’t be any worse than EDD 2.10, it’s just that EDD 3.0 exposes the problems that exist in 2.10 and are simply hidden. For example: if a discount amount wasn’t saved with an old EDD order, EDD 3.0 will show the discount amount as $0.00. That’s not technically correct; there was a discount amount, but because EDD never stored it we don’t know what it is.
Other migration fixes include:
- Undefined index errors when migrating some order addresses.
- When migrating tax rates via the CLI we now show the before and after count.
- Some very old PayPal orders didn’t have their transaction IDs migrated. This is because old orders didn’t store transaction IDs the way we do now, and they only existed in order notes. These are now migrated over.
- Some currency codes were saved (and thus also migrated) in lowercase, which caused unexpected results in our UIs. We now ensure all currency codes are uppercase when migrated.
The sales log has been removed
The sales log has historically existed because it was too difficult for us to query on payments directly, due to storing data in post meta. EDD 3.0 has made the sales log no longer necessary, as we can now very easily query order data. However, the UI still existed.
We made the decision to remove it when we found a bug: refund records were being included in the sales log incorrectly. Fixing that issue actually proved to be more complicated than expected, to the point where it would take less time to just remove the sales log and instead add the one missing feature to the main orders page: the ability to filter by download (product).
So there’s a shiny new feature for you!
Other bug fixes
EDD_Payments_Statsmethods returning unexpected results.
edd_store_discount()had the default value for its second parameter changed from
0, which broke backwards compatibility. This has now been reverted.
edd_post_insert_discounthook wasn’t firing after adding a discount code from the admin UI. This caused at least one add-on to stop working with EDD 3.0.
- The Discount API endpoint wasn’t 3.0-ready.
- Negative fees were showing as positive on the admin orders UI.
- Adding a manual order now supports inclusive taxes.
- Several methods in the
EDD_Discountclass were missing compared to 2.x. (Such as the
- The tool for re-counting download stats was incorrectly including refunds. It now counts gross earnings, and the label has been updated to better clarify that.
- Reports: Manually adding an invalid date to the custom range field could cause a fatal error.
- A few discount note functions that were introduced in 3.0 and ultimately never used (due to later refactoring) have been removed. Those functions are:
edd_ajax_delete_discount_note(). These were all AJAX callback functions and were never designed for public use.
- Order item meta arrays were incorrectly being double serialized.
Installing and testing 3.0-beta3
The 3.0-beta3 release can be downloaded from GitHub and installed as normal. If you encounter any bugs, please search through our existing issues. If there’s not already an open issue, you may create a new one (after reading our Contributor Guidelines).