-
Notifications
You must be signed in to change notification settings - Fork 0
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
Carriers are not being initialized when editing shipping method #200
Comments
Same here! But I face this issue, when initially enter API key on new install. |
Yes I know. We previously had this update upon entering and saving the form. Unfortunately Wordpress always loads the shipping method (multiple times), resulting in multiple calls to the API, which is unnecessary and can get people to reach their request limits. Therefore you currently have to save your settings one more time after entering the API key for them to be loaded. |
Unfortunately this "...save your settings one more time after entering the API key..." doesn't work either. |
For me, the carriers do display in settings, but not when editing shipping methods, which is because
Given that shipping methods are not edited on the shipcloud settings screen, |
Hmm, ok interesting. Will have to have a look at that. |
When editing shipping methods, there are none shown:
The problem seems to be one of the following two, not sure which one:
WC_Shipcloud_Shipping::carriers
is only initialized for the settings screen ininit_settings_screen
and thus is not available ininit_settings_fields
to in turn initialize$carriers_options
for use ininstance_form_fields
'allowed_carriers
field:The text was updated successfully, but these errors were encountered: