{"id":1146,"date":"2022-07-09T22:51:33","date_gmt":"2022-07-10T03:51:33","guid":{"rendered":"https:\/\/easydigitaldownloads.com\/development\/?p=1146"},"modified":"2022-07-09T22:51:34","modified_gmt":"2022-07-10T03:51:34","slug":"easy-digital-downloads-3-0-release-update","status":"publish","type":"post","link":"https:\/\/easydigitaldownloads.com\/development\/2022\/07\/09\/easy-digital-downloads-3-0-release-update\/","title":{"rendered":"Easy Digital Downloads 3.0 – Release Update"},"content":{"rendered":"\n

Well the time has arrived! We are tagging our final release candidate for EDD 3.0. Many of you have been following along on our GitHub repository over the last several months, helping test and finding things that need to be addressed. We’re very thankful for your help getting to this point. <\/p>\n\n\n\n

As we approach the final release date of July 13th, 2022<\/strong> here are the changes since the last major tag we gave you all.<\/p>\n\n\n\n

There have been a significant number of bug fixes, but we wanted to call attention to some of the larger changes that might pose an issue for developers as they integrate with EDD.<\/p>\n\n\n\n

Reporting Changes<\/h2>\n\n\n\n

We’ve made a few changes related to the reports to help give store owners an actionable set of information on the ‘Dashboard’ of reports. Many of these changes came after we’ve had a chance to use Easy Digital Downloads 3.0 on our own site, for our daily business operations.<\/p>\n\n\n\n

The first thing you’ll notice is that we’ve consolidated some of the ’tiles’. We reduced the number of tiles in this Dashboard to make the overall view much more useful.<\/p>\n\n\n\n

\"\"
Updated Reports Dashboard tiles with improved styles for relational data.<\/em><\/figcaption><\/figure>\n\n\n\n

We’ve also been focused on fixing some issues around reporting with Timezones. As of EDD 3.0 all dates recorded in the database are in UTC. By doing this we gave ourselves a point of reference, so that we can always show the store’s reports based on the Timezone setting defined in the general WordPress settings.<\/p>\n\n\n\n

Order status helper functions<\/h2>\n\n\n\n

As we started focusing on not just reporting on Gross and Net stats, we also found it necessary to define some ‘grouped’ order status keys. The following functions are helper functions to get specific order status that should be grouped. Each of these functions also contains a similar filter to allow extensions and customizations to add their own statuses.<\/p>\n\n\n\n

edd_get_gross_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that should be used when wanting orders that should be considered part of a ‘gross’ report.<\/p>\n\n\n\n
\n\n\n\n
edd_get_net_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that should be used when wanting orders that should be considered part of a ‘net’ report.<\/p>\n\n\n\n
\n\n\n\n
edd_recoverable_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that can be used in the core payment recovery feature.<\/p>\n\n\n\n
\n\n\n\n
edd_get_complete_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that are considered ‘complete’. This means they have hit the end of any automated purchase process and no further action needs to be taken at this time.<\/p>\n\n\n\n
\n\n\n\n
edd_get_incomplete_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that are incomplete. This includes things like pending, abandoned, processing, failed or cancelled.<\/p>\n\n\n\n
\n\n\n\n
edd_get_refundable_order_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order status keys that can be refunded.<\/p>\n\n\n\n
\n\n\n\n
edd_get_deliverable_order_item_statuses()<\/code><\/pre>\n\n\n\n
Returns an array of order item status keys that should be considered when delivering files. Note that in EDD 3.0, deliverability should be handled at the individual order item level, since one order can contain multiple items with different statuses.<\/p>\n\n\n\n
Enabled block editor on Download post type<\/h2>\n\n\n\n
The download custom post type is now available in the REST API, so your product pages can now be edited with the block editor.<\/p>\n\n\n\n
Language files removed<\/h2>\n\n\n\n
We’ve removed all of our translation files from our package, in order to rely on the WordPress Translation community. We found a number of translation files that were out of date and causing fatal errors due to being incorrectly translated, so we felt it was best to remove them from our plugin entirely, and allow them to be downloaded from translate.wordpress.org.<\/p>\n\n\n\n
On-the-fly Backwards Compatibility<\/h2>\n\n\n\n
We know that keeping stores accepting payments is important, and from day one of EDD 3.0’s development, we wanted to allow new purchases to be able to be completed, while the site was migrating existing payment data.<\/p>\n\n\n\n
We’ve taken this a step further, so that when renewals are processed with Recurring Payments or licenses keys are interacted with (checking for updates, activating, deactivating, or checking), that these actions complete successfully with a ‘semi-backwards compatible’ layer of EDD that ensures critical functionality will still work.<\/p>\n\n\n\n
We’ve also added the edd_v3_migration_pending<\/code> option so that you can identify when a migration is either pending start or running. For instance, you may have seen this on our site a few weeks back while we were running this migration ourselves:
<\/p>\n\n\n\n
\"\"
We displayed this message to users during the migration, using the edd_v3_migration_pending<\/code> option.<\/figcaption><\/figure>\n\n\n\n
Other Bug Fixes and Changes<\/h2>\n\n\n\n