| Previous · Next | |
| User | Message |
|
elnino
|
Date: 12/5/2006 12:28 pm · Subject: best practice for packages? · Rating: 5
Hello. I read about prototypes and packages. and experimented a little. If I create a page and call it a package, and delete the page, the package seems to be deleted as well. What do people do in this case? is there a way to make a package without making it in the site? --- (Edited on 12/ 5/2006 12:28 pm [GMT-0600] by elnino) --- --- (Edited on 12/ 5/2006 12:34 pm [GMT-0600] by elnino) --- |
| Back to Top |
Rate [ | ]
|
|
crythias
|
Date: 12/5/2006 2:11 pm · Subject: Re: best practice for packages? · Rating: 12
or simply not give "Everyone" access to your sandbox...
--- (Edited on 12/ 5/2006 3:11 pm [GMT-0500] by crythias) --- |
| Back to Top |
Rate [ | ]
|
|
elnino
|
Date: 12/5/2006 3:23 pm · Subject: Re: best practice for packages? · Rating: 1
Hmm. what I'm trying to do is prevent content managers to see or modify or delete the package. But they should be able to use it by selecting it via the package admin menu. The only way I can figure out how to make a package is to create a pagelayout within the site, and change the permissions so it's only seen by me. But even I have deleted packages by mistake when I found it in the navigation of the site. So what I want to know is, if there is a way to create a package without creating it from an exisiting page in the website? Hope that makes sense. Or maybe I should create a sandbox and put all my stuff there, like your response kinda of suggests. LN --- (Edited on 12/ 5/2006 3:23 pm [GMT-0600] by elnino) --- |
| Back to Top |
Rate [ | ]
|
