i am using version 4. was it difficult to make the customization? ideally i'd like to have a whole set of permissions like adding pages, modules etc. that can be turned off. in real world situations i find giving to much control to clients can be detrimental. it not only over-complicates things for them but they end up ruining the design and navigation. i'd rather just see them be able to edit whats already been set up for them. Do you think such customizations would be very difficult?

No, the customizations weren't difficult. If you send me an email (ocsowebmaster AT ocfl.net), I will send you the spreadsheet I made to track where I made changes, and the code base, so you can see what changes I made.

I agree, ideally I would like to have a wider set of permissions that I could turn off and on, but for our purposes, it wasn't practical to put that kind of effort into it. Instead, I hard-coded a Content Managers role that would have permission to add/remove modules from pages. When I first made the changes to the Core, I dd it for 3.0.12, and I allowed Content Managers to add/remove pages, but made some changes to keep them from adding their pages to the site menu, and to not permit them to set a page to be editable by All Users. I decided to get less elaborate when we moved to 3.2.2, and simply turned off allowing Content Managers the ability to add pages.