Fix incorrect start_date on exported subscriptions #246
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Exporting subscriptions that were previously imported is returning incorrect values for the
start_date
column, with the returned value being the date the subscriptions were imported rather than the start date of the subscription.This basic PR changes the call to
WC_Subscription::get_date()
to use'start'
as the$date_type
parameter instead of'date_created'
, which doesn't even appear to be a valid$date_type
.Does this perhaps need to fall back to
'date_created'
if the value of'start'
is empty?