Would it be possible to document how Commons implements "require user to log in" and how the exceptions by path are allowed?

Since several of Commons users have expressed an interest in hybrid private / public Commons sites, might it make sense to consider more flexible approaches going forward, using standard modules?

This is related to http://drupal.org/node/1438532, but is a more general question that I thought deserved its own issue.

Comments

lightsurge’s picture

lightsurge commented

This all happens in commons_core.module in the function commons_core_force_login()

I'm using Commons as a sort of public/private site so just turned this off.

jsibley’s picture

jsibley commented

@lightsurge, if you have force login turned off, how are you keeping the private part of your site private? Do you do this by path, by content type, and what modules do you use for this?

Thanks.

lightsurge’s picture

lightsurge commented

I don't know that you'd need modules, for each view you can set a permission to view it of 'authenticated', which would prevent access and remove the related menu items for anonymous users. You could disable access for anonymous to view the group content type, so that anonymous user can't get to group landing pages by path node/[nid].

You could probably use something like http://drupal.org/project/menu_access if you wanted to have some menu items just for anonymous users.

lsolesen’s picture

lsolesen commented
Issue summary: View changes
Status: Active » Fixed

Closing out old issues. Please reopen if still relevant.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.