Deanna, this is very helpful. I'm glad to see that you have quite a few users of Contribute. I can't imagine we will have more than 15-20 at any one time. We also tend to "share" content administrators. If there is a dept that doesn't change their content often, but they still have a need for a separate site, we may just offload the content administration to another person.
We will keep the "full page" tips in mind when building a trial of our site. We really don't care how much work it creates for us, up front, we mainly want to give our users the best solution for posting simple content to our intranet. If we have to do a massive search and replace, to change some templates, later on, then we can live with that. We have seen the shields that appear with scripting languages and have also wondered about the users deleting them. Thanks for the tip for that issue as well. M!ke -----Original Message----- From: Deanna Schneider [mailto:[EMAIL PROTECTED] Sent: Monday, January 09, 2006 8:29 AM To: CF-Talk Subject: Re: Intranet Based on CF7 and Contribute We do this on a pretty extensive basis. We have something on the order of 300+ Contribute users working on around 150 sites. Some of those are 300+ purely static content. Many incorporate some mixing of CF and static content. There are a lot of gotchas. First off, Contribute doesn't "not touch" all the CF code. What it does is put a little yellow shield where the code goes. If that happens to be in an editable region, it's perfectly possible for a user to delete the entire code block. There are two work-arounds that we've come up with. The first is that all your cf code that actually does anything important should be in CFC's or custom tags. That way, all you're including within a contribute page is a call to the actual code. So, should someone delete it accidentally, it's an easy fix. The other is to have pages that include contribute-editable pages. So, for example, your index.cfm might look like this (abbreviated): <html> <head> <title>My Page</title> <body> <cfinclude template="editablecontent1.html"> <cf_mycustomtag code="complex" protected="definitely"> </body> </html> Then, editablecontent1.html is what the user would be able to edit (see the lack of any editable region in this page?). Of course, in this scenario, you need to create an index page to all the pages that they can edit, because if they actually go to index.cfm, they're not going to be able to edit " editablecontent1.html". Does that make sense? Secondly, Contribute has issues if you don't have the html/head/body tags in each page. So, if you've grown accustomed to doing the very common <cfinclude template="head.cfm"> approach - where the head.cfm includes html and head tags, you'lll need to rethink that approach. You'll still want to "templatize" as much as you can. But, carefully. Here's an example barebones template of how we're doing it in one site: <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <html><!-- InstanceBegin template="/Templates/allpages.dwt.cfm" codeOutsideHTMLIsLocked="false" --> <head> <!-- InstanceBeginEditable name="doctitle" --> <title>4-H Youth Development UW-Extension</title> <!-- InstanceEndEditable --> <!-- InstanceBeginEditable name="head" --> <cfset pageSection = "home"><!-- InstanceEndEditable --> </head> <body> <div class="header"><cfinclude template="#fourhrootpath#/cfincludes/header.cfm"></div> <cfinclude template="#fourhrootpath#/cfincludes/nav.cfm"> <cfinclude template="#cffourhrootpath#/cfincludes/breadcrumbs.cfm"> <!-- InstanceBeginEditable name="Content" --> <!--- Content goes here ---> <cfmodule template="#fourhrootpath#/customtags/displayhighlight.cfm"> <!-- InstanceEndEditable --> <cfinclude template="#fourhrootpath#/cfincludes/footer.cfm"> </body> <!-- InstanceEnd --></html> In terms of security, contribute plays reasonably well with CF security models. And, you can get relatively granular with your contribute security models, as well. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:4:228859 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
