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
Describe the bug
Product creation fails via new product page or import when MYSQL_USER and MYSQL_PWD are set.
The error is: SQLSTATE[HY000]: General error: 1449 The user specified as a definer ('root'@'%') does not exist
This seems to be related to this line where root access is restricted to localhost once a MYSQL_USER is set.
Unfortunately Shopware defines database triggers that still reference 'root@%' as definer:
product_purchase_prices_insert
product_purchase_prices_update
product_listing_price_update
This can be easily seen when running 'show triggers' via mysql shell.
I eventually changed the definer manually to 'root@localhost' for all triggers like outlined here.
Afterwards product creation does not yield a 500 error anymore. Also import worked like a charm.
To Reproduce
Start dockware/dev with a MYSQL_USER and MYSQL_PWD.
Happy Christmas bug report!
Describe the bug
Product creation fails via new product page or import when MYSQL_USER and MYSQL_PWD are set.
The error is:
SQLSTATE[HY000]: General error: 1449 The user specified as a definer ('root'@'%') does not exist
This seems to be related to this line where root access is restricted to localhost once a MYSQL_USER is set.
Unfortunately Shopware defines database triggers that still reference 'root@%' as definer:
This can be easily seen when running 'show triggers' via mysql shell.
I eventually changed the definer manually to 'root@localhost' for all triggers like outlined here.
Afterwards product creation does not yield a 500 error anymore. Also import worked like a charm.
To Reproduce
Start dockware/dev with a MYSQL_USER and MYSQL_PWD.
Afterwards try to create a product either by the new product page or by import.
Expected behavior
Product creation succeeds without errors.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: