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
This gem calculates the rates using the Easypost APIs removing the Solidus ones.
How to solve
Merging the custom rates with the Easypost rates, we can also use the custom shipping methods since Easypost doesn't support the in-store pickup and freight shipping.
Roadmap
Enable Solidus rates calculator
Distinguish the Solidus shipping method from the Easypost ones
Buy a rate only if the related shipping method is not easypost
Disable the admin_name shipping method field if it is generated using Easypost
Show Easypost errors on the admin panel when shipping is shipped
Show Easypost address validation errors on the frontend if occurs
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi @vassalloandrea, this of critical importance to us. We are stuck on Rails 5.1 because active_shipping does not support Rails 5.2. However, we cannot move from active_shipping to solidus_easypost because we have alternate shipping methods (subscription products that ship later, ebooks that don't ship at all, etc.).
How can I help? Would love to coordinate and get some PRs underway.
This issue has been automatically marked as stale because it has not had recent activity. It might be closed if no further activity occurs. Thank you for your contributions.
Problem
This gem calculates the rates using the Easypost APIs removing the Solidus ones.
How to solve
Merging the custom rates with the Easypost rates, we can also use the custom shipping methods since Easypost doesn't support the
in-store pickup
andfreight shipping
.Roadmap
easypost
admin_name
shipping method field if it is generated using EasypostThe text was updated successfully, but these errors were encountered: