Forum OpenACS Improvement Proposals (TIPs): Re: Tip #77: (Approved) Package parameter scope and permissioning

Would it be useful to have parameters that are not visible through the web UI at all? Right now XCMS, and BCMS set the content folder, template folder etc as parameters. These should be set when the folder is created in an install callback. It probably doesn't make sense to allow changing it through the web interface.

I think using parameters for this is handy because they are stored in RAM and the cache is updated when they are changed or added, so its easy to write code that works as you expect.
This would require another permissioning context "none" or another way to control the ability to change the parameter through the web UI.