You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the batch label creation mode and you want to create a new shipping label for an order that has previously created shipping labels, one of the old labels is being used to get merged into the merged pdf containing "all the shipping labels from this batch process".
The first shipping label in the image above is the one create by the batch process. It's a DHL shipping label. The other accordion that's open is the shipping label from UPS that was used to merge it into the merged pdf --> see b93db61c62d9becbf7fe1056db3a3375b040f67f.pdf.
The text was updated successfully, but these errors were encountered:
Within a bulk action each labels will be downloaded
and merged into one big PDF.
Some orders already have labels created manually (via edit screen),
so unfortunately a merge contains such "old" labels too.
Therefor the caching of already created labels needs a proper hash
to separate new and old ones even across API versions.
- Hash of URL covers more scenarios than the described one.
- Pay attention that this can lead to much obsolete files over time.
- see github #125 for more
I just added something that may solve this @andrecedik (directly to the 1.4 branch) .
Please keep this issue open as it is just a hotfix that produces much data from now on.
We need some garbage collection in upcoming versions.
When using the batch label creation mode and you want to create a new shipping label for an order that has previously created shipping labels, one of the old labels is being used to get merged into the merged pdf containing "all the shipping labels from this batch process".
The first shipping label in the image above is the one create by the batch process. It's a DHL shipping label. The other accordion that's open is the shipping label from UPS that was used to merge it into the merged pdf --> see b93db61c62d9becbf7fe1056db3a3375b040f67f.pdf.
The text was updated successfully, but these errors were encountered: