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
Implemented in PR #9833. This implementation will work only with new or fresh databases. Existing databases will continue to function as before, meaning url_key will remain non-locale based because all the product attribute values and the attribute itself are non-locale based.
If you want url_key to be locale-based in the existing database, follow these manual steps:
Update the value_per_locale column to 1 for the attribute with id = 3 or code = url_key in the attributes table. This step will convert the url_key attribute to be locale-based.
Convert the url_key attribute saved in product_attribute_values to be locale-based by running the following query on the database:
UPDATE product_attribute_values
SET locale ='en',
unique_id = CONCAT_WS('|', channel, 'en', product_id, attribute_id)
WHERE attribute_id =3;
Ensure you update your default locale accordingly in the above query.
Terms
Bagisto Version(s) affected
2.0.
Issue Description
Add a product in the default language.
Assume you have at least 2 locales enabled.
Edit the product.
switch on not default locale and alter url_key.
The url_key saved is equal to the default locale.
So the new url_key is not saved in the product_attribute_values table
Preconditions
assume you have at least 2 locales enabled.
Steps to reproduce
Add a product and assume you have at least 2 locales enabled.
switch on not default locale and alter url_key.
The url_key saved is equal to the default locales.
So the new url_key is not saved in the product_attribute_values table
Expected Result
new url key for the current locales is saved on the product_attribute_values table
Actual Result
the url_key submitted is not saved
Screenshots
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: