Hi Edward,
Thank you for bringing this to my attention. Yes, I am planning to update the location endpoints to API v3, and I will release an updated version soon.
I understand this is important for your Ongoing WMS integration, and I appreciate your patience. I will keep you updated once the new version is available.
Best regards,
Fahad
Hello,
I’m experiencing a PHP warning in the Stock Locations for WooCommerce plugin.
The warning appears in:
wp-content/plugins/stock-locations-for-woocommerce/views/settings-api.php — line 41
The affected code is:
<tr title="<?php echo (isset($param_data['tooltip'])?$param_data['tooltip']:''); ?>" class="scope-<?php echo $param_data['scope']; ?>">
The warning is:
Warning: Undefined array key “scope”
It appears that $param_data['scope'] is not always defined for every parameter.
A possible fix would be to check whether the key exists before accessing it:
<tr title="<?php echo isset($param_data['tooltip']) ? esc_attr($param_data['tooltip']) : ''; ?>" class="scope-<?php echo isset($param_data['scope']) ? esc_attr($param_data['scope']) : ''; ?>">
Alternatively, a default value such as 'default' could be used if the plugin requires a specific scope.
Could you please review this and consider including a fix in a future update?
Thank you for your work on the plugin.
Hello Jani,
Thank you for bringing this to my attention. It is only a warning, but I appreciate you taking the time to report it and suggest a possible fix.
I’ll review the issue and include the necessary change in an upcoming version of Stock Locations for WooCommerce.
Thank you again for your help and support.
Hi Edward,
Thank you for reporting this. I can look into adding the location endpoints needed for the Ongoing WMS integration.
Could you please share the expected v3 endpoint format and the fields/methods your integration requires for locations (GET/PUT)? For example, whether you expect /wp-json/wc/v3/locations/ or another endpoint structure.
Once I have those details, I can make sure the implementation matches your integration requirements without breaking the existing location endpoints.
Thank you!
