Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable route to hidden pages #1250

Open
buschhardtt opened this issue Aug 31, 2024 · 4 comments
Open

Disable route to hidden pages #1250

buschhardtt opened this issue Aug 31, 2024 · 4 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details size:XS - 1 Sizing estimation point

Comments

@buschhardtt
Copy link

Description

Hello,

When I hide a page using UI-CONTROL or the settings, it is removed from the menu. However, if someone navigates directly to the URL of the hidden page, its content is still displayed on the screen. Is it possible to completely disable the page so that users cannot access or see it, even if they enter the URL directly?

The approach using the UI-CONTROL "change" event (i.e., redirecting the user to a different page) still briefly displays the entered page.

Thank You

Have you provided an initial effort estimate for this issue?

I am no FlowFuse team member

@buschhardtt buschhardtt added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do labels Aug 31, 2024
@joepavitt
Copy link
Collaborator

Chatting with @sumitshinde-84 about this and just wanted to document some thoughts. We currently have two states which drives the Page visibility/interactivity

  • Disabled: Shows the page in the menu item, but prevents interaction with it
  • Visibility: Doesn't show the page at all in the side-menu

In each case though, there is still value/reason to want to navigate directly to that UI. There is an argument that just because it's not shown in the left-navigation, that it should still be possible to navigate to the page. However, I agree that if a page is "disabled", then routing should be prevented, which could be handled at the vue-router level

So, for an admin style use-case, if the page is both disabled and made not visible, that would prevent "member" users seeing it in hte left-side menu, and prevent them from navigating directly to the page too.

@Mika97400
Copy link

Hello,

Yes but just adding the good url let the user navigate to page. Maybe it should be useful to redirect to another url when the page is disable and prevent the user to display the page. Even if we know that using Client Data could help to remove data.

@joepavitt
Copy link
Collaborator

Thanks @Mika97400 - this had slipped through the net, so I'm happy to up this in priority

@joepavitt joepavitt moved this from Backlog to Up Next in Dashboard Backlog Dec 4, 2024
@joepavitt joepavitt added size:XS - 1 Sizing estimation point and removed needs-triage Needs looking at to decide what to do labels Dec 4, 2024
@Mika97400
Copy link

Mika97400 commented Dec 5, 2024

Thanks to you, and by the way use the direct URL seems to reveal other links that was disable/not visible.
Maybe it's my personnal flow process but maybe you should take a look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details size:XS - 1 Sizing estimation point
Projects
Status: Up Next
Development

No branches or pull requests

3 participants