Zone:Site & Page Permissions - (Vanished)

This is very strange to start having things disappear on me?


MISSING in Edit zone: "site"


Missing "Zone:Site" in Permissions Tree Editor



This is what is currently in my "Permissions Tree Editor" There is no "Zone:Site" !



MIssing: Admin Zone>Structure>Permissions
Therefore I don't have the choice to choose "Page Permissions".

 

Ok, I think I might understand why.

From the explination found here:  Composr Tutorial: Composr site structure - Composr

Site: this is your main website; it includes primary content viewing, and permission based submission, editing, and deleting features. The contents of this zone may automatically be merged into the Welcome Zone via the 'Single public zone' option, which will simplify things for you

During installation I think I did elect to have a 'Single public zone'  there fore "this zone may automatically be merged into the Welcome Zone".

but now I don't have the abiltiy to view and edit "Page Permissions" . Which kind of sucks because I have gotton acustomed to this.

Can I revert the site back to multiple zone to get my "Zone:Site" back with out any repercussions?
 

PARTLY SOLVED

I would probably leave this topic up for new Composr users just in case they run into the same situation.

I simply rectified my problem and got my "Zone:edit" back by going to;

→ Home > Admin Zone > Setup > Configuration > Site options

Under Structure section I unticked "Single Public Zone".

PAGE PERMISSIONS <- Did not come back
 

I don't understand why you have 2 screenshots that are looking so different:

1. "Missing "Zoneite" in Permissions Tree Editor"
2. "This is what is currently in my "Permissions Tree Editor" There is no "Zoneite" !"

Are these different websites? I suspect '1' is a different website and an old pre-release version, because it should not be possible for this to start at 'Zone: Welcome' (it should start at 'Root' like in the second screenshot).

Anyway, all the site zone modules can be found under 'Zone: Welcome' if the single public zone option is on.

1."Missing "Zoneite" in Permissions Tree Editor"

This image is from the tutorail page. Illustraing were "zone:site" was suppose to be.  But now I am assuming the tutorial's page was not in "single public zone".

2. "This is what is currently in my "Permissions Tree Editor" There is no "Zoneite" !"

This is my permissions tree editor showing that "zone:site" is gone. And no, I expanded the Welcome zone and the zone site module "zone:site" was not there either.  While looking for my "zone:site" my website was in "single public zone".

So, since I couldn't find the zone:site I took it out of "single public zone" and then I got it back.  But what didn't come back was my
"Page Permssions" page? It is no were to be found.

You are missing a lot more than just your zone:site. Something whacky going on. Wondering if you disabled an addon that needs to be running.

Here is what mine looks like.

Thanks for that important info Paul.  I will check into this deeper later this afternoon. I really appreciate it.

I'm pretty confused about this because some sites seem to be starting from "Zone: Welcome" and other from "Root". There's nothing missing actually, just a different arrangement. I'm investigating it.

Ok, it's all fine, I'd just forgotten how we do it myself .

I'm adding this to our docs:

Note that the Sitemap shown in the Permission Tree Editor depends on the "Single public zone" configuration option.
If this option is on then the default content pages will be under the Welcome zone, and no Site zone will be shown. The Sitemap will start from Root.
If this option is off then the default content pages will be under the Site zone. Because the Welcome zone is almost empty the Sitemap will start from the Welcome zone.

I've always wondered if having Guest content in a Guest zone and member content at the root would make more sense. At least from a user perspective. Probably not though, for reasons I haven't thought of. The idea that it's an easier way to keep member content away from guests is still valid, but with all the options that exists now maybe not so much. Probably missing the point here though, I often do.

KingBast said

I've always wondered if having Guest content in a Guest zone and member content at the root would make more sense. At least from a user perspective. Probably not though, for reasons I haven't thought of. The idea that it's an easier way to keep member content away from guests is still valid, but with all the options that exists now maybe not so much. Probably missing the point here though, I often do.

From “Post #2,347”, 14th April 2017, 8:41 pm

Just that you'd need to somehow redirect guest traffic reaching the root of the domain if guests couldn't access that, extra complexity.

Yeah, I used the code Malatesa once posted which made it work a bit like facebook. I would imagine all their stuff is in the root (so to speak). Just seems weird that Members have to access a zone to me, or that it relies on a zone if they do not. A lot of stuff seems weird to me though, so not complaining