barcode should map to GTIN, part_number should map to MPN, _backorder_availability_date should map to the Availability Date field.
I’ve used the filter in your guide above (woocommerce_gla_attribute_mapping_sources_custom_attributes) to add the field keys to the mapping sources, so they do now appear in the dropdown list & I’ve created the mapping rules.
However, I’m not sure the mapping is working as expected. If i update one of my Barcode values, it doesn’t seem to correctly update the GTIN field. Same for the part_number field, it doesn’t update the MPN field.
i was expecting the target attribute to be updated in line with the data source but this doesn’t happen. do you have any ideas why? Am i missing something or misunderstanding how the mapping should work?
Also, why i can’t select Availability Date as a target attribute? It means i can’t add my mapping rule from the data source _backorder_availability_date.
Finally, does the mapping also work for variable products? My field keys for simple / variable products are the same but i don’t see any documentation about mapping variable products.
Thanks
I get the error listed in the title when trying to do the attribute mapping step listed here. This occurs despite having completed the test configuration step with the details of the test config appearing in a box to the right of the attribute mapping area.
Does anyone know why this is occurring?
]]>Automatic mode not working – https://prnt.sc/no1s0B4Px0xV
]]>System:Windows 10 64-bit
Opera is up to date
Version:94.0.4606.26
Update stream:Stable
Chromium version:108.0.5359.99
Google Chrome is up to date
Version 108.0.5359.125 (Official Build) (64-bit)
Many thanks in advance
]]>Woocommerce is a great plugin, BUT:
I am really surprised that woocommerce still doesn’t support attribute-set. This is a really important feature to any e-commerce plugin.
This feature, attribute-set, will allow you to pre-define the attributes for a specific product category, and while uploading a new product, once you mention the product category, all the attributes will come automatically.
This feature is supported in Magento.
can’t find any plugin which has this feature as well. If anyone knows, please update me. Product uploading will be more easier and fun with this feature.
As woocommerce fan, I would like this to be introduced soon to the woocommerce plugin. Please. Forward this message to the developers.
]]>Looking at the code, I see this query to populate the Value pulldown:
SELECT meta_key as name, meta_value as type FROM wp_postmeta group by meta_key
This will get ALL the custom postmeta rows in the entire wp_postmeta table which will give you all the specific postmeta variables that may have been setup for any product or even just regular post in the ENTIRE wordpress database.
Two questions:
1) CUSTOM WOOCOMMERCE PRODUCT ATTRIBUTES are actually stored in ONE row in that table called _product_attributes. In order to offer those as options you would have to traverse that array of product_attributes, which the plugin did at one time I think. I do see reference to it in the code in a few places, but it’s definitely not traversing it to offer as options in the dropdown. Was functionality changed with regards to the Value pulldown options?
2) Could the dropdown be limited to just custom attributes for PRODUCTS which are a specific post type instead of the entire range of posts that may have meta? That would make the dropdown smaller it seems but get everything that normally applies to the mapping process. Right now, it will include ANY post meta, even if it has no relation to a Woocommerce PRODUCT at all.
It doesn’t seem like this question needs me to submit a debug file but let me know if that would help. We are operating off of a manual feed right now so the dynamic is not fully configured.
Thanks, Karen
]]>In my case I have mapped attributes as follows:
Google Shopping Attribute –> VALUE
g:price –> Regular price excl. VAT
g:sale_price –> Sales price excl. VAT
PREFIX in both cases is AUD (which stands for Australian Dollar)
Regular price excl. VAT is always populated
Sales price excl. VAT does not always contain a value, depending on if a sale price is applicable or not, on a product-to-product basis.
Can you please clarify the plugin’s handling of Google Merchant’s g:sale_price?
]]>