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
The column updated_in in the table catalog_category_entity of the root node (ID 1) is not updated correctly.
Never touch the root node, but when you have an active B2B module-staging and you schedule a catalog price rule, the category view in adminhtml is broken.
This is because the root node gets skipped out of the select statement when the category tree is loaded.
We temporary fixed this issue by manipulating the value of updated_in for the Category entities 1 and 2 to a very high level.
The text was updated successfully, but these errors were encountered:
The column updated_in in the table catalog_category_entity of the root node (ID 1) is not updated correctly.
Never touch the root node, but when you have an active B2B module-staging and you schedule a catalog price rule, the category view in adminhtml is broken.
This is because the root node gets skipped out of the select statement when the category tree is loaded.
We temporary fixed this issue by manipulating the value of updated_in for the Category entities 1 and 2 to a very high level.
The text was updated successfully, but these errors were encountered: