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
For "About Us" and similar types of pages (that have mostly text content), we created a new route similar to "store.bug": { "path": "/bug/:slug" }, and we are implementing it on blocks with the menu and rich-text apps.
We should be able to access /bug/whatever on StoreFront and be able to input content that's specific to that URL, or I'm misunderstanding the use of the Visibility: This URL option.
Current Behavior
When I browse storefront on different URLs, create a configuration and select the Visibility option for This URL, the Visibility seems to be ignored and visiting the front end for each page only loads the first configuration.
And when there are multiple configurations for different URLs, the list shows as if they are all for the same URL.
Possible Solution
¯\(ツ)/¯
Steps to Reproduce (for bugs)
Create a new route with a variable url /bug/:slug and implement it on blocks with the rich-text app
Create a link somewhere on the page to be able to navigate to /bug/page1 and /blug/page2
Go to /bug/page1 on StoreFront, create a configuration with Visibility set to This URL
Go to /bug/page2 on storefront, create a configuration with Visibility set to This URL
Visit /bug/page1 on the frontend, it appears that it's showing the right content. but...
Visit /bug/page2 on the frontend, it shows the content of page1, because it was the first one created
Your Environment
Version used: 3.x
Environment name and version (e.g. Chrome 39, node.js 5.4): all
Operating System and version (desktop or mobile): all
Expected Behavior
For "About Us" and similar types of pages (that have mostly text content), we created a new route similar to
"store.bug": { "path": "/bug/:slug" }
, and we are implementing it on blocks with the menu and rich-text apps.We should be able to access /bug/whatever on StoreFront and be able to input content that's specific to that URL, or I'm misunderstanding the use of the
Visibility: This URL
option.Current Behavior
When I browse storefront on different URLs, create a configuration and select the Visibility option for This URL, the Visibility seems to be ignored and visiting the front end for each page only loads the first configuration.
And when there are multiple configurations for different URLs, the list shows as if they are all for the same URL.
Possible Solution
¯\(ツ)/¯
Steps to Reproduce (for bugs)
/bug/:slug
and implement it on blocks with the rich-text appYour Environment
The text was updated successfully, but these errors were encountered: