Needs review
Project:
e-Commerce
Version:
5.x-3.3
Component:
store
Priority:
Critical
Category:
Bug report
Assigned:
Reporter:
Created:
2 Aug 2007 at 08:51 UTC
Updated:
11 Apr 2008 at 15:58 UTC
Jump to comment: Most recent file
I'm using flexicharge instead of any shipping calc providers.
it is immpossible to send the shipping notify mail because shipping API is disabled, so transaction status also does not change to shipped.
PS. if I activate shipping API without any providers- then there are some problems with checkout: "Asked for empty shipping methods and does not allow to place the order"
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | shipping.module-checkout.patch | 1.02 KB | mrf |
Comments
Comment #1
mariuss commentedSimilar issue here, need to use flexcharge and had to disable shipping api because shipping charges will show twice otherwise ($0 from the shipping api and the right amount from flexcharge).
Flexcharge should register as a shipping module and work properly with the shpping api, or a similar shipping module should be created (shipcalc works only with postal companies, there is need for flat rate shipping or percent based ones).
Comment #2
brmassa commentedGuys,
lets see:
1* on eC4, emails will be handled by the new workflow scheme and actions module integration.
2* payment statuses and transaction statuses can be changed on eC4 (so you can add a shipped by your own)
regards,
massa
Comment #3
(not verified) commentedComment #4
Phillip Mc commentedopening back up this thread to see if anyone has found a solution for the issue
I have the same problem using ecommerce 5.x-3.3, which, if I'm not mistaken is the current stable version of ecommerce.
Any tips of guidance appreciated.
Phil
Comment #5
mrf commentedHere's a small patch I used for 5.x-3.4's shipping.module that will allow you to keep shipping api enabled (and send shipped e-mails) but still use the flexicharge.
The patch just hides the duplicate shipping message from shipping api if the the field is empty.
I'm guessing that this patch might cause problems with other parts of the shipping api, so it should really only be used as a temporary fix for this particular issue.