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
If you use a relative images.baseUrl like /img/ the path won't be build using the api.url config value like in the other endpoint, which forces you to use an absolute url at this point again.
Expected behavior
Make image proxy url work with a relative base url using the processURLAddress() method.
Steps to reproduce the issue
You can see it with each visible product image.
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.
Environment details
Browser: all
OS: all
Node: default
Code Version: Known in master and develop
Additional information
Nope
The text was updated successfully, but these errors were encountered:
Current behavior
If you use a relative
images.baseUrl
like/img/
the path won't be build using theapi.url
config value like in the other endpoint, which forces you to use an absolute url at this point again.Expected behavior
Make image proxy url work with a relative base url using the
processURLAddress()
method.Steps to reproduce the issue
You can see it with each visible product image.
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
develop
Additional information
Nope
The text was updated successfully, but these errors were encountered: