Welcome back from the holidays, and as we stated before our holiday break we’re back with a bi-weekly Easy Digital Downloads 3.0 progress update. Over the holidays and last few weeks we’ve been working through to get some of the UI bugs fixed. Here are the highlights of the changes since our last update.<\/p>\n
Easy Digital Downloads uses AJAX to make for a better user and administrative experience. They are collectively called “EDD Actions” when we use them via AJAX. In our pre-3.0 EDD Actions, we’ve always done our best to do as much error handling as we can. When presented with an error response we have always written the response to be In 3.0, we’ve added some new EDD Actions, but these will respond with a full JSON response when they are presented with an error, instead of the View the issue on GitHub<\/a>.<\/p>\n A number of UI improvements and fixes were corrected, mostly centered around the administrative sections of Easy Digital Downloads. Here are some of those fixes:<\/p>\n In the past, orders (previously called payments) were stored in the same table as Posts and Pages. Therefore, we made the decision to take a ‘completed’ order and mark it with a status of ‘publish’ in the database. On the front end, this was output as ‘Completed’, but all of the code and database records referenced ‘publish’ as the end state of an order that was in good standing. In Easy Digital Downloads 3.0 we’re changing this. Thanks to our new database tables we no longer feel the need to adhere to this status and have switched a ‘completed’ order to have a status of ‘complete’ in the database. This just brings our code and visual output into a more cohesive state, which makes Easy Digital Downloads easier to work with from a development perspective.<\/p>\n While not yet<\/em> merged into the Welcome back from the holidays, and as we stated before our holiday break we’re back with a bi-weekly Easy Digital Downloads 3.0 progress update. Over the holidays and last few weeks we’ve been working through…<\/p>\n-1<\/code>. While this functions as a way for us to know that the AJAX response had an error, it doesn’t quite provide us with enough information to provide a better user experience to inform the user of an action that ends in error.<\/p>\n-1<\/code>, as with our existing actions. These new actions are all centered around the new ‘Add Order’ process. If all works as expected, we’ll investigate on making all our AJAX responses have full JSON responses, which should allow people customizing their EDD Shops to better serve their customers error messages when there is a problem.<\/p>\nUI Fixes and improvements<\/h2>\n
\n
Status change for ‘completed’ orders<\/h2>\n
release\/3.0<\/code> branch, the changes are code-complete and ready for testing. If you want to follow along, you can view this issue on GitHub<\/a>.<\/p>\nOther improvements and bug fixes<\/h2>\n
\n
[downloads]<\/code> shortcode to not fatal error when it is used on a single download page. (#6072<\/a>)<\/li>\n