Pages do not respond to changes to "Post Access", maybe because they are "Post" and not Page" access 馃槉
Hi @pateskinasy , I'm not sure what you mean by The page continues to be public. The page is supposed to stay accessible to the public, but it's contents should not be visible (just like for the posts). I've tested it quickly and seems to work as expected. I'll close this issue for now, but feel free to reopen in case I'm misunderstanding something :smiley:
Thanks for reverting @gargol.
My bad, I mistook the page "continuing to be public" with the lack of a CTA (subscribe / become paid-member banner) to either "subscribe" or "become a paid member".
Anyway, it seems there is still an issue here though. I've adjusted also the title of this issue to help others going through the same find this in future.
In other words, I do not get a CTA when a page is made "Members-only" or "Paid-members only"
To reproduce:
Public Pages --> it works
Members-only Pages --> issue
Below: Not logged-in member sees (no content but NO CTA to subscribe seen) <-- issue

Below: Logged-in member sees (sees content --> all OK)

Paid-members only Pages --> issue
Below: Not logged-in member sees (no content but NO CTA (banner) to subscribe seen) <-- issue

Below: Logged-in member sees (no content but sees no CTA (banner) to become a paid member) <-- issue

Might be related to https://github.com/TryGhost/Ghost/issues/11574
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
The Lyra theme is not set up to show CTAs in it's page.hbs. You can modify the theme to suit your needs if you require member-only pages with CTAs, perhaps taking some clues from the theme's post.hbs.
Closing as this is not a server-side bug but a specific theme issue.
Most helpful comment
The Lyra theme is not set up to show CTAs in it's page.hbs. You can modify the theme to suit your needs if you require member-only pages with CTAs, perhaps taking some clues from the theme's post.hbs.
Closing as this is not a server-side bug but a specific theme issue.