Skip to content
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

Display Backend only rates in the backend #1743

Conversation

mamhoff
Copy link
Contributor

@mamhoff mamhoff commented Feb 24, 2017

Prior to the commit, shipping methods that had display_on set to
back_end or available_to_usersset to false would not be displayed
in the backend. This commit changes Spree::Order#refresh_shipment_rates
and Spree::Shipment#refresh_rates to accept an optional argument
frontend_only. If that is set to false, the estimator will also
take into account backend only rates.

Also, the places where @order.refresh_shipment_rates are called
in the backend now pass frontend_only: false to those methods.

This is the same as #1739, but for Solidus 1.4.

Prior to the commit, shipping methods that had `display_on` set to
`back_end` or `available_to_users`set to `false` would not be displayed
in the backend. This commit changes `Spree::Order#refresh_shipment_rates`
and `Spree::Shipment#refresh_rates` to accept an optional argument
`frontend_only`. If that is set to `false`, the estimator will also
take into account backend only rates.

Also, the places where `@order.refresh_shipment_rates` are called
in the backend now pass `frontend_only: false` to those methods.
@mamhoff mamhoff force-pushed the display-backend-rates-in-backend-on-1.4 branch from c0ec503 to e084404 Compare February 24, 2017 08:55
Copy link
Member

@tvdeyen tvdeyen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks

@mamhoff
Copy link
Contributor Author

mamhoff commented Feb 25, 2017

I'm waiting for the discussion on #1739.

@mamhoff mamhoff closed this Feb 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants