09-15-2017, 08:40 PM
OK! I remember the discussion on this...
The annoyance is there on purpose. I think it makes a ton of sense to just mark a page private by default (although I would be down with the option in the admin panel).
But, I took the private page when securePage hit the page the first time, because I kept forgetting to go into the admin panel and set permissions on pages because they were all admin only by default.
I probably didn't explain that properly. There isn't a technical reason why someone needs to go into admin_pages to add a page. The reason that message is there is to force the developer to think through permissions a page at a time when they create them. Although, it definitely happens where I add a permission level so I forget to click the private button.
I went ahead and made it 1 by default and then you can feel free to add it as an option to the admin panel. I'll push soon.
The annoyance is there on purpose. I think it makes a ton of sense to just mark a page private by default (although I would be down with the option in the admin panel).
But, I took the private page when securePage hit the page the first time, because I kept forgetting to go into the admin panel and set permissions on pages because they were all admin only by default.
I probably didn't explain that properly. There isn't a technical reason why someone needs to go into admin_pages to add a page. The reason that message is there is to force the developer to think through permissions a page at a time when they create them. Although, it definitely happens where I add a permission level so I forget to click the private button.
I went ahead and made it 1 by default and then you can feel free to add it as an option to the admin panel. I'll push soon.