We have a gated community but some pages appear to be public. Plese help!

Hi Jan,

Have you removed the "Read Site" permission from the Everyone role? this will prevent non-registered users from seeing site pages.

If that doesn't resolve it, which pages specifically are being accessed? member pages? specific group?

Thanks, I tried that and after saving the settings (Membership > Roles > Everyone > Permission > Read site - disabled), and opening a new anonymous browser tab, the pages were still accessible (not the rest of pages though).

They are all Custom Pages, the Platform defined pages are well gated behind the login form.

But not the Custom Pages.

I can provide momentary links if necessary.

Thanks for any help!

Thanks, I tried that and after saving the settings (Membership > Roles > Everyone > Permission > Read site - disabled), and opening a new anonymous browser tab, the pages were still accessible (not the rest of pages though).

They are all Custom Pages, the Platform defined pages are well gated behind the login form.

But not the Custom Pages.

I can provide momentary links if necessary.

Thanks for any help!

I may add that the site's URL changed recently. I don't remember we had this problem before.

I found this thread: community.telligent.com/.../custom-page-require-login not sure if related, it seems Custom Pages are visible for anyone by default? Thanks for any help.

It does look like there is not validation for custom pages OOTB. I'm logging this as we should at least tie it to a permission such as Read Site. As suggested in the other thread, the workaround requires some custom code, either a custom dll or a custom widget with logic to redirect the user to login page.

Thanks a lot Steven.

I'm new to the Velocity syntax, could you suggest some simple conditional check to redirect to login - if user is not logged in?

Many thanks,

#set($accessingUser = $core_v2_user.Accessing)
#if(!$core_v2_user.IsRegistered($accessingUser.Id))
	$core_v2_page.Redirect($core_v2_urls.LogIn("%{ReturnToCurrentUrl = true}"))
#end

Thank you!

It actually looks like we already have some plans to take a more holistic look at scenarios like yours, where the requirement is to "gate" the site completely from anonymous users. So the above work item may not stay valid, but there is still related work being planned.