Skip to content

Visibility filter not working #199

@hapoza

Description

@hapoza

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)

  1. Create a new route with a variable url /bug/:slug and implement it on blocks with the rich-text app
  2. Create a link somewhere on the page to be able to navigate to /bug/page1 and /blug/page2
  3. Go to /bug/page1 on StoreFront, create a configuration with Visibility set to This URL
  4. Go to /bug/page2 on storefront, create a configuration with Visibility set to This URL
  5. Visit /bug/page1 on the frontend, it appears that it's showing the right content. but...
  6. 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
  • Link to your project: https://parquedpedro.myvtex.com/

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions