Some of the contexts here are using paths like 'Student Life' which I'm not sure will last... I think it's highly likely different schools will want to vary the language here, depending on their geographic location and type of school. For example 'School' instead of 'Academics' and 'Activities' instead of 'Athletics'.

Seems to me that we have 4 pages here, Student Life/Academics/Admissions/Athletics that should be relatively ambiguous as to their content, so that different schools can use them as they see fit. Currently we're able to change the node titles which I think is good, but if we do so the contexts break.

Comments

jgraham’s picture

jgraham commented
Assigned: Unassigned » jgraham

Yes this is a good point. We went with the node approach to avoid having overridden features if users changed the corresponding nodes as that is quite likely. However, the path based approach for triggering the contexts is a bit short-sighted and we need to come up with a more reliable way to trigger these contexts.

lightsurge’s picture

lightsurge commented

Perhaps just simply using 'node/' paths instead of aliases? I suppose these nodes would then need protecting, perhaps by binding them to a content type that only user 1 has access to delete (which might be a good thing anyway as currently user 2 has access to delete these nodes).

Edit: actually, I see that these pages are already the 'page' content type which presumably isn't a content type that needs to be open for creation/deletion by any of the roles, so these permissions might be able to be removed?

jgraham’s picture

jgraham commented
Status: Active » Fixed

Fixed the path issue.

Remaining details around deleting the top-level nodes is in #1530266: Block users from deleting the top-level nodes created in our feature-sets

Status: Fixed » Closed (fixed)

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