Issue description: The customer renewing their subscription. For some of the subscriptions, the renewed order showed that the invoice had been generated, but with the wrong invoice number (usually the parent order of the subscription).
It was discovered that the subscription post contained some meta data that was being copied to the renewed order, including the invoice number and date. The reason for this meta data being there is not clear, but we had a method developed to prevent such meta data from being copied to the renewed order, to prevent such issues.
However, we encountered a problem with this method as there was a typo in the hook name, which prevented it from working correctly. Additionally, the old deprecated hook used to send the $meta argument with a different data structure than the new hook, so it needs to be updated to be compatible with the new data structure.
The old deprecated hook had this data structure for the $meta argument:
close #688
This is related to this ticket.
Issue description: The customer renewing their subscription. For some of the subscriptions, the renewed order showed that the invoice had been generated, but with the wrong invoice number (usually the parent order of the subscription).
It was discovered that the subscription post contained some meta data that was being copied to the renewed order, including the invoice number and date. The reason for this meta data being there is not clear, but we had a method developed to prevent such meta data from being copied to the renewed order, to prevent such issues.
However, we encountered a problem with this method as there was a typo in the hook name, which prevented it from working correctly. Additionally, the old deprecated hook used to send the
$meta
argument with a different data structure than the new hook, so it needs to be updated to be compatible with the new data structure.The old deprecated hook had this data structure for the
$meta
argument:And this is for the new hook: