cf includes

[benhollis]

Can someone please help me on this!?

Contribute 3.11 claims to protect CF scripts and includes, but users can very
easily select and delete the CF 'shield icons' representing include scripts in
my pages. Deleting a shield icon would catastrophically remove navigation from
the page. Since Contribute claims to protect CF scripts and includes, I
elected not to use DW Templates and only use include files. Besides, DW
templates are hard-coded into the page, which is bad news for global changes in
my very large site.

Is there a secret method to coding the include path? Right now, I'm trying
this code, rendering an easily removable "shield icon", which users can click
and delete in Contribute:

<div id="tabs"><cfinclude template="/tabs_hr.cfm"</div>

[Dominic Michael]

You protect the shield icon being removed by the following settings.
1) Administer the site.
2) Edit the role, for the user you want to protect the cf scripts.
3) Edit Role setting dialog opens, select the Editing option listed in the
category.
4) Under General editing restrictions, check the option "Protect scripts and
forms".
5) Click OK to the opened dialogs and try the same scenario again.

Hope this helps you.

[benhollis]

Thank you for the reply.

Unfortunately, I enabled/checked the "protect scripts and forms" option
without any luck. I even tried version CS3, and some of my includes or "shield
icons" are deletable, others are not. I found a tech note today from Adobe,
which talks about dynamic content not being protected.

I think I may fall into this unfixable category:

"In some cases, the dynamic content will still be editable even with
correct protective options set. This is a known issue in Contribute and there
is no work-around at this time. It does not happen in all cases and Adobe
Technical Support has been unable to the reproduce this issue."

[url]http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16651&sliceId=2[/url]

[ThinkInk]

You could also combine templates in Dreamweaver with include files. This way
you get the benefits of both temlate editable regions (content and design
seperated) and includes. The includes are placed outside editable regions and
this way you users won't be able to get to the includes. I realise that maybe
this is not possible to accomplish this in this case, since the website is
already there and not using templates, but maybe it's something to consider in
future projects

[benhollis]

Thank you for the template/include combination idea. I explored this option
early on, but I really wanted to avoid templates entirely.

My "fix" for now is only allowing users to edit text only, which is what 95%
of the users change anyways (text, links, documents).

[benhollis]

Eureka! I upgraded to CS3 and found things to work better. I then found that
Contribute only protects includes to .htm files. I inlcuded a .cfm file in my
code, and Contribute made it completely removable. I'm not certain if the
upgrade to CS3 fixed the include problem, but it difinately solve tons of CSS
mis-rendering issues that were show stoppers in v3.

Now I just have to do a global find and replace, rather than going down the
dark path of DW templates.