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
dbNamePrefix ignored in order/PROCESS_QUEUE listener
Expected behavior
respect dbNamePrefix in order/PROCESS_QUEUE listener
Steps to reproduce the issue
Set not-empty storeView.storeCode, for example zulcom
See in developer tools name of shop storage equals shop instead of the expected zulcom-shop
Can you handle fixing this bug by yourself?
YES
NO
Which Release Cycle state this refers to? Info for developer.
Pick one option.
This is a bug report for test version on https://test.storefrontcloud.io - In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
This is a bug report for current Release Candidate version on https://next.storefrontcloud.io - In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
This is a bug report for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version hotfix - In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.
Current behavior
dbNamePrefix
ignored inorder/PROCESS_QUEUE
listenerExpected behavior
respect dbNamePrefix in
order/PROCESS_QUEUE
listenerSteps to reproduce the issue
Set not-empty
storeView.storeCode
, for examplezulcom
See in developer tools name of shop storage equals
shop
instead of the expectedzulcom-shop
Can you handle fixing this bug by yourself?
Which Release Cycle state this refers to? Info for developer.
Pick one option.
develop
branch and create Pull Request2. Feature / Improvement
back todevelop
.release
branch and create Pull Request3. Stabilisation fix
back torelease
.hotfix
ormaster
branch and create Pull Request4. Hotfix
back tohotfix
.Environment details
The text was updated successfully, but these errors were encountered: