-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Different shipment numbers after spree 2.0.7 upgrade #4063
Comments
the old I'm surprised that the number of digits is changed though. |
number of digits is changed because the method that now generates shipment number is https://github.com/spree/spree/blob/2-0-stable/core/lib/spree/core/permalinks.rb#L46 instead of https://github.com/spree/spree/blob/2-0-stable/core/app/models/spree/shipment.rb#L255 |
We could make this overridable (just like |
Sorry about that @alepore! I've added a fix for this to 2-0-stable, 2-1-stable and master now, along with a regression test. Permalinks can now have different lengths. |
Thanks! |
No, that's another bug. Will look tomorrow On Mon, Dec 9, 2013 at 6:24 PM, Alessandro Lepore
|
Ok thanks, my thought was to simply remove the |
@alepore I am unable to reproduce that issue on a 2-1-stable store or 2-0-stable store. Here's what I get:
|
@radar you are manually calling (clean spree
this is with
my point is: we are now generating shipment number with |
Wow, I am stupid. Sorry @alepore, and thank you for being patient with me. I've now got a proper fix in to my 2-0-stable, 2-1-stable and master which should fix this. Please check it and see if this does fix it. |
👍 thanks! |
Fixes #4063 (really) Conflicts: core/app/models/spree/shipment.rb core/spec/models/spree/shipment_spec.rb
Since the upgrade from spree 2.0.6 to 2.0.7 i see shipment number changed from "H(11 digits)" to "(9 digits)"
I think after this commit 1b51211 a permalink is generated by
make_permalink field: :number
before the call of
before_create :generate_shipment_number
Before, instead,
to_param
was called first of all, i guess, generating the correct number before the permalink.I think we have to rollback to the old behavior (make_permalink is really needed?)
The text was updated successfully, but these errors were encountered: