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
When listing available shipping modules in the backend via toOptionsArray, the shipping method "DPD Home Delivery" is identified as 'dpdclassic_classic', but when placing an order the same shipping method is identified as 'dpdclassic_dpdclassic'. This breaks compatibility with other modules that provide further options for specific shipping methods.
I'm talking about the backend function "toOptionsArray" of the full set of shipping methods, which creates a list of all available shipping methods and allows the user to select multiple shipping methods, similar to payment methods, shipping countries etc. This is not specific to this module, but a base function of magento.
But in the list created by that function the shipping methods receive an identification name apparently constructed by the carrier code ('dpdclassic' in this case) and the allowed methods provided by "getAllowedMethods()". So for each method in the return array of that function it will create a list item with 'dpdclassic_'.$arraykey as identifier, and right now the key is simply 'classic'.
My proposed fix changes the array key to 'dpdclassic', and this way the identifiers match up. We are still in the process of setting up everything, so I am still not sure this fix does not break some other functionality, but we have not found any problems yet.
When listing available shipping modules in the backend via toOptionsArray, the shipping method "DPD Home Delivery" is identified as 'dpdclassic_classic', but when placing an order the same shipping method is identified as 'dpdclassic_dpdclassic'. This breaks compatibility with other modules that provide further options for specific shipping methods.
A quick fix would be:
Replace
with
in Model/Carrier/Dpdclassic.php, but I'm not 100% certain this works without causing other issues.
The text was updated successfully, but these errors were encountered: