Needs review
Project:
Ubercart
Version:
7.x-3.x-dev
Component:
Fulfillment
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Nov 2013 at 17:09 UTC
Updated:
30 Jan 2016 at 03:12 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
DrCord commentedTokens made available by patch:
Comment #2
longwaveThanks for this, although are you duplicating work that has already been done - uc_shipping.tokens.inc already provides a tracking-number token? This patch should at least be moved into that file, because it depends on uc_shipping to be enabled for any of these tokens to work.
Comment #3
tr commentedPatch needs to be against HEAD for the testbot to work.
Also, the markup should be removed from the text in the token. If you want to style the text in your email or any other context the token is used then it can be marked up at that point.
Comment #4
DrCord commentedNot sure what you mean against HEAD if I didn't do it, I thought I was generating the patch against the HEAD...
I will look at moving the code into uc_shipping.tokens.inc
Comment #5
DrCord commentedComment #6
tr commentedHEAD refers to the most recent development version.
When you post a patch, change the status to "Needs review" so the testbot will look at it.
Comment #8
tr commentedThere appears to be a problem with the testbot. The test passed, but the system message in #7 reports the wrong thing.
Issue opened at #2140329: Testbot autofollowups should only change status for the last patch in an issue.
Comment #9
tr commentedComment #10
tr commented5: tokens-shipment-tracking-2139337-2.patch queued for re-testing.
Comment #11
DrCord commentedThis has been re-queued for awhile do I need to do something?
Comment #12
philsward commentedBump
Would love to see this committed. Tested against 3.8 and appears to work ok.
Comment #13
tr commented@philsward: You're the first to test this.
Comment #15
philsward commented@TR thx for re-queuing it, but after some more extensive testing, It seems this is only partially working. I spoke too soon :-/ a million apologies.
The following is a list of my findings. I do not have the knowledge to fix and suggest a patch, so if @DrCord or someone else can provide a fix, I am willing to test.
On a side note, I have only tested this against "Manual Shipment". As stated before, tested against D7 UC 3.8
---
[order:shipment-carrier] only works for the very last shipment. In a drop ship environment or multi-shipment environment, there is usually more than one carrier. Each carrier should be separated with the respective tracking numbers below them.
[order:tracking-number] Listing all tracking numbers (good; needs to be separated by carrier though)
[order:tracking-package] Only works for the very last shipment.
[order:tracking-shipment] Only works for the very last shipment. (by design?)
Output Example for 6 separate "shipments"
Order Shipping:
Carrier6: 1-12345, 2-12345, 3-12345, 4-12345, 5-12345, 6-12345
Carrier6: 6-12345P
Carrier6: 6-12345
Tested Token Format
Order Shipping:
[order:shipment-carrier]: [order:tracking-number]
[order:shipment-carrier]: [order:tracking-package]
[order:shipment-carrier]: [order:tracking-shipment]
Comment #16
DrCord commentedI no longer have an installation of Ubercart to test this against.
Comment #17
tr commentedComment #18
philsward commentedI might have my programmer look at this and issue an updated patch. Not sure if I'll end up with this direction or not, but I do like where it was going. We'll see. I'll post back if I come up with anything in the next few weeks.
Comment #19
tr commentedThanks. It would be useful.
Comment #20
philsward commentedAttached an updated version that should have some of the bugs worked out from #5
Comment #22
tr commentedThe patch in #20 failed for the same reason as your patch in the other issue - you used DOS line endings instead of Unix. I converted this one to the correct format for you.
Comment #23
philsward commentedThanks @TR
Sorry for making you do that, but glad it passed.
Comment #24
tr commentedComment #25
tr commented