Hove over preview gives access to hidden pages

1

I don’t know if it is a bug or it is intended like this, but for me it is very illogical, so I thought I ask:

I have a table with a column where I reference another table which is hidden. But when in the published version of the doc I hover over of the chip (which comes from the hidden table) I can actually navigate to the hidden pages and so everyone else can. For me it is not really logical that in this way users can bypass the page hidden settings.

This is the published page: Blueprint · Egyesek - ProfessionalED
At the select control you can click on the select list items and then you land on the hidden page, where the referenced table exists.

1 click

image
image1106×621 62.6 KB

2 click
image
image1508×1299 95.3 KB

This page should be hidden and not accessible:
image
image870×1247 101 KB

This is the setting behind:
image
image684×1041 93.3 KB

Any suggestion how to block users to get into the hidden pages?

Thanks a lot!

2 Likes
2

Unfortunately, hidden pages in Coda do not fulfill their apparent role as described by the function’s name. When the feature is activated, Coda simply hides the pages from the sidebar list but does not conceal the page at the architectural level of the doc. This initially confused me as well. Moreover, a hidden page and any content within it can easily be found through the search function, which undermines the entire logic of the access control system the user might want to establish.

3 Likes
3

So it is a Coda bug? :slight_smile:

4

Not a bug, but a feature! :grin: I think the developers did it intentionally.

1 Like
6

Hidden pages are not an access control feature. It keeps the pages out of view only. It does not prevent access.

It works as designed, but access control is frequently requested on the forum. I think that with the full implementation of sync pages, access control will be possible.

7

Admit it, @Piet_Strydom. The ‘Hide’ function misleads users simply by its name.
Its current implementation contradicts basic user expectations: the page remains accessible through search and direct links, making the ‘hiding’ purely nominal until it’s discovered. Once it’s found, this ‘hiding’ loses all meaning, turning into a completely pointless feature.

It’s essentially like a ‘Delete File’ button that merely removes the icon from the desktop while leaving the file fully accessible through the file explorer. When a user sees the ‘hide’ option, they intuitively expect actual concealment of the information, not just a cosmetic adjustment in the interface. This is an example of poor UX/UI design.

4 Likes