David
Guest
|
 Posted:
Mon Oct 24, 2005 12:51 pm Post subject:
Restricting access to template |
|
|
Hi Stefan,
Here is the scenario...
Our site has a general template that any of our authors can access. I
created an application template based on the general template that can host
usercontrols that our development team write. This works perfectly. It
allows our dev team to create the controls on their own machine, test
however they want before transferring it to the dev server.
This allows our site to have interactivety that our developers create, as
against the static stuff that our users author.
Now, I have a slight problem. I have an item that crosses the boundary
between the two templates. I need to use the application template for some
dynamic items but also the user to be able to edit the HTML and Image
placeholders.
The application template knows which usercontrol to host, based on a custom
property.
So, here is what I need to do, but I don't know how to manage it.
I need to create 73 pages based on the application template.
The author cannot then change any of the page properties, only the content
of the placeholders.
Also, the author must not have general access to the application template
(i.e. cannot select it when creating a new page.)
How would I do this?
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available |
|
Stefan [MSFT]
Guest
|
| Posted:
Mon Oct 24, 2005 12:51 pm Post subject:
Re: Restricting access to template |
|
|
Hi David,
MCMS does not help you with this you would need to implement this on your
own.
E.g. implement a workflow event that prevents properties from being set.
To ensure that the template cannot be used by your authors to create new
postings you could add some logic to the Page_Load event that verifies if
the user is one of the allowed users and if the web author context mode is
AuthoringNew.
If a wrong user choosed the template and the mode is authoring new redirect
to an error page.
Cheers,
Stefan
--
This posting is provided "AS IS" with no warranties, and confers no rights
New to MCMS?
Check out this book: Building Websites Using MCMS: http://tinyurl.com/6zj44
----------------------
"David" <david.colliver.NEWS@revilloc.REMOVETHIS.com> wrote in message
news:%23RReuHJ2FHA.3568@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi Stefan,
Here is the scenario...
Our site has a general template that any of our authors can access. I
created an application template based on the general template that can
host usercontrols that our development team write. This works perfectly.
It allows our dev team to create the controls on their own machine, test
however they want before transferring it to the dev server.
This allows our site to have interactivety that our developers create, as
against the static stuff that our users author.
Now, I have a slight problem. I have an item that crosses the boundary
between the two templates. I need to use the application template for some
dynamic items but also the user to be able to edit the HTML and Image
placeholders.
The application template knows which usercontrol to host, based on a
custom property.
So, here is what I need to do, but I don't know how to manage it.
I need to create 73 pages based on the application template.
The author cannot then change any of the page properties, only the content
of the placeholders.
Also, the author must not have general access to the application template
(i.e. cannot select it when creating a new page.)
How would I do this?
Best regards,
Dave Colliver.
http://www.AshfieldFOCUS.com
~~
http://www.FOCUSPortals.com - Local franchises available
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in