Error adding editable region in nested template Header

I have a base template for the website (establishing basic
menus), and a secondary template using that base template, which
establishes a common table layout for one part of the site. Having
created the PHP to drive the page, I need to lock down that
secondary nested region - otherwise any edit I make to my secondary
"table-defining" template is not passed through
to the final pages using the secondary template. I have
successfully created a secondary editable region in each part of
the <body> area, and sure enough, it locks down text
outside the secondary editable region just as DW help says it
should. So far so good.
Now the problem - I cannot create a region inside the
<head> editable region to lock down that region too.
Normally one would want keywords and so on to be variable from page
to page, but as I am filling variable keywords from a database, it
makes sense to lock down the <head> too. Does anyone
know why that generates an error "cannot create an
optional region here"? Is there anything that can be done
about it?

Posts are hard to read when they are all crammed together
like yours. Try
making some paragraphs!
Nevertheless, I think I understand what you are saying., but
honestly, I
just wouldn't do it that way. Anymore, my templates are just
one editable
region in the body, and a bunch of server-side includes. I
find nested
templates much too complex, and troublesome to work with, and
have really
never found a scenario where I could do things with them that
I could not do
more easily with other methods.
> However, I have an Editable
> region with the HTML Head area, and DW does not permit
me to add a
> 'secondary-template Editable Region' within it to lock
it down.
Is it only you working on the site? Who are you trying to
'lock down'? If
it's only you, I'd forget about this. Invariably the things
like this that
you think are a good idea come back later to bite you.
Murray --- ICQ 71997575
Adobe Community Expert
(If you *MUST* email me, don't LAUGH when you do so!)
==================
http://www.projectseven.com/go
- DW FAQs, Tutorials & Resources
http://www.dwfaq.com - DW FAQs,
Tutorials & Resources
==================
"suddensurprise" <[email protected]> wrote
in message
news:[email protected]...
> Murray 'ACE' wanted to understand why I am using nested
templates.
>
Primary
> Template or 'base layout' I have a primary template
which establishes
> the
> top, left and bottom borders for the site. These contain
Spry menus - if
> I
> change the menu on the primary template, all pages will
be updated. The
> primary template has a 'work area box' which is where
the page content
> goes for
> each different page.
Secondary or 'nested' template Next I have a
> secondary template, or nested template. It starts with
the primary
> template
> but this time the 'work area box' is set up with a
product table and
> various
> fixed column headings. The table is filled from
different database
> records
> using PHP and MySQL. Therefore the secondary or 'nested'
template
> establishes
> a common format for the product table. For example, a
change to a heading
> in
> the secondary template is updated into all pages using
it. And to
> reiterate, a
> change to the Spry menu bar on the primary template will
update the
> secondary
> template and all pages created from that template.
Similarly, I have
> several
> other secondary templates, all created from the primary
template, all
> setting
> standard sections of the website so that multiple pages
can be updated at
> once
> via a single template change.
Note: the code in the secondary
> template
> needs to be 'locked' so that edits within it are passed
on to its slave
> pages.
> This is done by creating an empty Editable region at the
beginning of the
> 'work
> area box' I talked about.
Other Approaches? If anyone knows a
> better
> way of enabling site edits to be passed consistently
down into different
> standard-section blocks of the website, I would welcome
your input.
>
The
> Problem Now to reiterate the problem with which I
started this thread.
> In
> a secondary template it works fine creating a second
Editable Region
> within the
> Body of the HTML document - the rest of the code in that
'primary template
> editable region' is now locked out as is required.
However, I have an
> Editable
> region with the HTML Head area, and DW does not permit
me to add a
> 'secondary-template Editable Region' within it to lock
it down. I am
> wondering
> if anyone in the Community knows why or can suggest a
solution. Regards
> Richard
>

Similar Messages

  • How to remove Editable region from nested template?

    I'm trying to remove an editable region from a nested
    template while retaining it in the parent template. DW doesn't want
    to let me do this.
    Example:
    - I've created an overall template call ALLPAGES.DWT
    - In it, there's an editable region called "related links".
    - The "related links" will stay the same for all my main
    pages (welcome, news, info, etc), so I'd like to create a nested
    template called MAINPAGES.DWT where the field is locked.
    So here's what I did; I started a new page from ALLPAGES.DWT
    and then I created a template MAINPAGES.DWT from it. Now I want to
    remove the editable region "related links". According to the DW
    manual, I should be able to highlight the region and go to
    Modify > Templates > Remove Template Markup, but that
    option is greyed out!
    Apparenlty the only way of removing the editable region is to
    create a smaller editable region within it. But that's unnecessary
    and sloppy. How can I remove the region entirely?

    > This use of nested templates is very useful and very
    simple and
    > straightforward.
    > It involves no additional overheads, and introduces no
    reliability
    > problems.
    I really disagree with this.
    > I cannot understand why Murray has such a bad attitude
    to nested
    > templates.
    I spent quite a bit of time using them, tweaking them,
    understanding them,
    and watching the problems that others have had here on the
    forum. My
    compelling conclusion is that there is nothing you can do
    with nested
    templates that you cannot do more simply and with far less
    trouble by using
    other methods, some involving other kinds of template
    regions, and some
    involving simple use of Library items, or better, server-side
    includes.
    > I can only assume either that he had a bad experience on
    the road to
    > Damascus,
    > after writing his definitive book on templates
    I assure you, it's based on much more study and experience
    than you have put
    into it.
    > "Templates are wicked and sinful! Don't play with them,
    or you will go
    > blind!"
    This is not only unkind, it's completely erroneous. Far and
    away, I am the
    single most enthusiastic proponent for the use of templates
    on these boards.
    Perhaps a read of my book would help you rid yourself of your
    attitude, too.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.dreamweavermx-templates.com
    - Template Triage!
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    http://www.macromedia.com/support/search/
    - Macromedia (MM) Technotes
    ==================
    "Clancy" <[email protected]> wrote in message
    news:[email protected]...
    > "Dodgeit" <[email protected]> wrote:
    >
    >>I'm trying to remove an editable region from a nested
    template while
    >>retaining
    >>it in the parent template. DW doesn't want to let me
    do this.
    >>
    >> Example:
    >> - I've created an overall template call ALLPAGES.DWT
    >> - In it, there's an editable region called "related
    links".
    >> - The "related links" will stay the same for all my
    main pages (welcome,
    >> news,
    >>info, etc), so I'd like to create a nested template
    called MAINPAGES.DWT
    >>where
    >>the field is locked.
    >
    > Very simple:
    >
    > Open allpages.dwt.
    > Save as template, with name mainpages.dwt (I always do
    this immediately so
    > that
    > if I do something stupid I don't corrupt the original
    template).
    > Insert the desired content into "related links".
    > At the beginning of the content area of "related links"
    insert the magic
    > code
    > @@("")@@
    > This turns off the editable region, and there will be no
    reference to it
    > in
    > pages derived from this template.
    > Save the changes to mainpages.dwt
    > Done!
    >
    > Have a look at
    >
    >
    http://www.corybas.com/Technical/Nested.htm
    > This is derived from my template techpage.dwt, which in
    turn is ultimately
    > derived from my template basicpage.dwt.
    >
    > Basicpage.dwt defines two editable regions 'title' and
    'subtitle' at the
    > top of
    > the page. Techpage.dwt sets a fixed title for all my
    technical pages, as
    > follows:
    >
    > <p class="hdgtn" ><!-- InstanceBeginEditable
    name="Title" -->@@("")@@Roger
    > Riordan: Technical notes<!-- InstanceEndEditable
    --></p>
    > <p class="hdgstn"><!-- InstanceBeginEditable
    name="Subtitle" -->Notes<!--
    > InstanceEndEditable --></p>
    >
    > In the page Nested.htm the references to 'title'
    disappear, and the two
    > lines
    > appear as
    >
    > <p class="hdgtn" >Roger Riordan: Technical
    notes</p>
    > <p class="hdgstn"><!-- InstanceBeginEditable
    name="Subtitle" -->Nested
    > Templates<!-- InstanceEndEditable --></p>
    >
    > This use of nested templates is very useful and very
    simple and
    > straightforward.
    > It involves no additional overheads, and introduces no
    reliability
    > problems.
    >
    > I cannot understand why Murray has such a bad attitude
    to nested
    > templates. I
    > can only assume either that he had a bad experience on
    the road to
    > Damascus,
    > after writing his definitive book on templates, or that
    it says simply:
    >
    > "Templates are wicked and sinful! Don't play with them,
    or you will go
    > blind!"
    >
    >
    > Clancy

  • How to make metatags "Editable" region in my template?

    How can I make my metatags "editable" regions in my template?
    I tried doing it as shown below . . . but when trying to update the individual pages from the template, I get an error message that looks like its trying to tell me something is missing from the <!-- TemplateBeginEditable -->  instruction.
    Can anyone help?
    I appreciate it!
    <head>
    <!-- TemplateBeginEditable -->
    <meta name="keywords" content="cat, dog, apple, banana">
    <meta name="description" content="My Description will go here.">
    <title>My Title will go here</title>
    <!-- TemplateEndEditable --><!-- InstanceBeginEditable -->
    <title>undefined</title>
    <!-- InstanceEndEditable -->

    Thanks for your response, David
    Well, I've tried to implement your instructions on the template (see below for EXACT code).   But on all the "child" pages, I am ONLY still allowed to edit the "Title" tag.  Everything else is still GRAYED-OUT (unable to edit).
    What did I do wrong?
    - Jim
    <html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns="http://www.w3.org/TR/REC-html40">
    <head>
    <!-- TemplateBeginEditable name="head" -->
    <meta name="keywords" content="resume,resume service,resume writer,resume assistance,resume assistant">
    <meta name="description" content="Professionally-written Resumes ready in 60 minutes! Great quality & friendly service.  Just $49.95. Lowest prices! Our 19th year. Work with a real person on the phone. Hassle-free (no forms to fill out like our competition). Guaranteed Job-Winning Resumes. Open 7 days til 12 Midnight.">
    <title>Best c Resumes - Ready in 1 Hour!</title>
    <style>
    <!--
    a            {
    color: #0000FF
    -->
    </style>
    <link rel="File-List" href="../u4/17YUvRBD_files/filelist.xml">
    <meta name="Microsoft Theme" content="blends 011">
    <!-- TemplateEndEditable -->
    </head>

  • I have an Editable Region in a template and want to remove it

    When I have an Editable Region in a template and want to
    remove it, and from all child-pages, what to do[mx 2004] ? The
    below code if is in logout.php how is get included in a file ?
    I use:
    <!--#include file="../customeradmin/logout_links.php"
    -->
    but isset($_SESSION["email"] does not working .... well ?
    [code]<?php
    if (isset($_SESSION["email"])) {
    ?>
    <link href="/css-styles.css" rel="stylesheet"
    type="text/css"><body class="text_normal">
    <span class="text_normal">LOGGED IN(<a
    class="text_normal"
    href="/php_files/logout.php">Customer-LogOut</a>)</span>  
    <?php
    ?><br />
    <?php
    if (isset($_SESSION["email-affiliates"])) {
    ?>
    LOGGED IN(<a class="text_normal"
    href="/php_files/affout.php">Affiliate-LogOut</a>)
    <?php
    ?>
    [/code]

    Click in the editable region in the Template file. Right
    click on the
    mmeditable tag you see on the tag selection and choose Remove
    Tag from the
    menu. Save the Template.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "123polis123" <[email protected]> wrote in
    message
    news:gf7pu8$p69$[email protected]..
    > When I have an Editable Region in a template and want to
    remove it, and
    > from
    > all child-pages, what to do[mx 2004] ? The below code if
    is in logout.php
    > how
    > is get included in a file ?
    >
    > I use:
    > <!--#include file="../customeradmin/logout_links.php"
    -->
    > but isset($_SESSION["email"] does not working .... well
    >
    > [code]<?php
    > if (isset($_SESSION["email"])) {
    > ?>
    > <link href="/css-styles.css" rel="stylesheet"
    type="text/css"><body
    > class="text_normal">
    > <span class="text_normal">LOGGED IN(<a
    class="text_normal"
    >
    href="/php_files/logout.php">Customer-LogOut</a>)</span>  
    > <?php
    > }
    > ?><br />
    > <?php
    > if (isset($_SESSION["email-affiliates"])) {
    > ?>
    > LOGGED IN(<a class="text_normal"
    >
    href="/php_files/affout.php">Affiliate-LogOut</a>)
    > <?php
    > }
    > ?>
    > [/code]
    >
    >
    >

  • Making DW CS4 Nested Template Head Region Update to Pages

    Using DW CS4...
    So I made a template, called main_template, and obviously it has an editable region named head. Now from main_template I made the nested template locations_template. Now I have code that I put in the head region of locations_template. This code does not propagate out to pages created from locations_template. I can't place an editable region within the head section in the nested template. How do I solve this problem?

    > 1st: "Error accessing file "...here appears the file
    name/path..." bad
    > file
    > path (error code 3) OKAY
    This usually means you have other files open that may belong
    to templates
    not in the current site. Make sure that you have other such
    files closed
    and you won't get this error.
    > 2nd: When I click the OKAY button I get: "There is an
    error at line 5,
    > Column
    > 35 (absolute position 54) of "...here appears the file
    name/path..." :
    > Nested
    > edible regions.
    This usually means you have an error in the template file -
    we would need to
    see its code to diagnose further.
    > When I check the code at line 5 or 54 I find nothing
    relevant to "Nested
    > edible regions".
    It could be referring to code errors like a missing
    </head>, or <body> tag,
    too.
    Murray --- ICQ 71997575
    Adobe Community Expert
    (If you *MUST* email me, don't LAUGH when you do so!)
    ==================
    http://www.projectseven.com/go
    - DW FAQs, Tutorials & Resources
    http://www.dwfaq.com - DW FAQs,
    Tutorials & Resources
    ==================
    "Roy E" <[email protected]> wrote in message
    news:fppie5$ikg$[email protected]..
    >I am using one template in my website. Upon making
    changes it would
    > automatically update associate pages as it should. Then
    it quit and now
    > when I
    > try to do a manual update (Modify > Template . Update
    Pages) I get the
    > following error messages.
    >
    > 1st: "Error accessing file "...here appears the file
    name/path..." bad
    > file
    > path (error code 3) OKAY
    >
    > 2nd: When I click the OKAY button I get: "There is an
    error at line 5,
    > Column
    > 35 (absolute position 54) of "...here appears the file
    name/path..." :
    > Nested
    > edible regions.
    >
    > When I check the code at line 5 or 54 I find nothing
    relevant to "Nested
    > edible regions".
    >
    > Am I reading the error message incorrectly re:
    line/location of the error?
    > (I
    > do not want to have to recreate the template .)
    >
    > Help!
    >
    > Thomas
    >

  • How to insert a widget in a editable region from a template

    Hi there,
    ok so basically I am trying to create a HTML page from a template i have already designed.
    when I try to insert a widget (Lightbox Gallery) in the editable region I get the following error.
    "the widget requires code that must be inserted into the head of the document. insertion cannot happen because this document is read only"
    I saw a previous thread (http://forums.adobe.com/thread/901299) that had the same problem with a solution but cant seem to make sense of it.
    Not exactly sure where and what to paste in the header of the HTML page.
    Any help will be much appreciated.
    Thanks

    Hi Murray,
    ha funny you would say that is the exact answer you would give me seeing you posted it
    I understand the logic behind it though not sure what i need to copy and where.
    Basically i craeted a "dummy page" and inserted the widget-no problem there.
    next step- what code do i copy from the dummy page and where do i paste it? in the template or HTML page.
    Dummy HTML with widget code
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
    <title>Untitled Document</title>
    <script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/jquery.js" type="text/javascript"></script>
    <script src="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/scripts/lightbox.js" type="text/javascript"></script>
    <link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/lightbox.css" rel="stylesheet" type="text/css" />
    <link href="file:///C|/Users/Ashley/AppData/Roaming/Adobe/Dreamweaver CS5/en_US/Configuration/Temp/Assets/eamA1E8.tmp/css/sample_lightbox_layout.css" rel="stylesheet" type="text/css" />
    <style type="text/css">
    /* BeginOAWidget_Instance_2127022: #gallery */
                        .lbGallery {
                                  /*gallery container settings*/
                                  background-color: #CCC;
                                  padding-left: 20px; 
                                  padding-top: 20px; 
                                  padding-right: 20px; 
                                  padding-bottom: 20px; 
                                  width: 540px;
                                  height: auto;
                                  text-align:left;
                        .lbGallery ul { list-style: none; margin:0;padding:0; }
                        .lbGallery ul li { display: inline;margin:0;padding:0; }
                        .lbGallery ul li a{text-decoration:none;}
                        .lbGallery ul li a img {
                                  /*border color, width and margin for the images*/
                                  border-color: #3e3e3e;
                                  border-left-width: 10px;
                                  border-top-width: 10px;
                                  border-right-width: 10px;
                                  border-bottom-width: 20px;
                                  margin-left:5px;
                                  margin-right:5px;
                                  margin-top:5px;
                                  margin-bottom:5px:
                        .lbGallery ul li a:hover img {
                                  /*background color on hover*/
                                  border-color: #ffffff;
                                  border-left-width: 10px;
                                  border-top-width: 10px;
                                  border-right-width: 10px;
                                  border-bottom-width: 20px;
                        #lightbox-container-image-box {
                                  border-top: 0px none #ffffff;
                                  border-right: 0px none #ffffff;
                                  border-bottom: 0px none #ffffff;
                                  border-left: 0px none #ffffff;
                        #lightbox-container-image-data-box {
                                  border-top: 0px;
                                  border-right: 0px none #ffffff;
                                  border-bottom: 0px none #ffffff;
                                  border-left: 0px none #ffffff;
    /* EndOAWidget_Instance_2127022 */
    </style>
    <script type="text/xml">
    <!--
    <oa:widgets>
      <oa:widget wid="2127022" binding="#gallery" />
    </oa:widgets>
    -->
    </script>
    </head>
    <body>
    <div id="gallery" class="lbGallery">
      <ul>
        <li> <a href="/images/lightboxdemo1.jpg" title=""><img src="/images/lightboxdemo_thumb1.jpg" width="72" height="72" alt="Flower" /></a> </li>
        <li> <a href="/images/lightboxdemo2.jpg" title=""><img src="/images/lightboxdemo_thumb2.jpg" width="72" height="72" alt="Tree" /></a> </li>
        <li> <a href="/images/lightboxdemo3.jpg" title=""><img src="/images/lightboxdemo_thumb3.jpg" width="72" height="72" alt="" /></a> </li>
        <li> <a href="/images/lightboxdemo4.jpg" title=""><img src="/images/lightboxdemo_thumb4.jpg" width="72" height="72" alt="" /></a> </li>
        <li> <a href="/images/lightboxdemo5.jpg" title=""><img src="/images/lightboxdemo_thumb5.jpg" width="72" height="72" alt="" /></a> </li>
      </ul>
    </div>
    <script type="text/javascript">
    // BeginOAWidget_Instance_2127022: #gallery
                        $(function(){
                                  $('#gallery a').lightBox({
                                            imageLoading:                              '/images/lightbox/lightbox-ico-loading.gif',                    // (string) Path and the name of the loading icon
                                            imageBtnPrev:                              '/images/lightbox/lightbox-btn-prev.gif',                              // (string) Path and the name of the prev button image
                                            imageBtnNext:                              '/images/lightbox/lightbox-btn-next.gif',                              // (string) Path and the name of the next button image
                                            imageBtnClose:                              '/images/lightbox/lightbox-btn-close.gif',                    // (string) Path and the name of the close btn
                                            imageBlank:                                        '/images/lightbox/lightbox-blank.gif',                              // (string) Path and the name of a blank image (one pixel)
                                            fixedNavigation:                    false,                    // (boolean) Boolean that informs if the navigation (next and prev button) will be fixed or not in the interface.
                                            containerResizeSpeed:          400,                               // Specify the resize duration of container image. These number are miliseconds. 400 is default.
                                            overlayBgColor:                     "#999999",                    // (string) Background color to overlay; inform a hexadecimal value like: #RRGGBB. Where RR, GG, and BB are the hexadecimal values for the red, green, and blue values of the color.
                                            overlayOpacity:                              .6,                    // (integer) Opacity value to overlay; inform: 0.X. Where X are number from 0 to 9
                                            txtImage:                                        'Image',                                        //Default text of image
                                            txtOf:                                                  'of'
    // EndOAWidget_Instance_2127022
    </script>
    </body>
    </html>
    thanks again

  • Inputting a list into an alternative to inputting it into an editable region in a template

    Hello all,
    I did ask this question yesterday but only got partial feedback so I'm hoping someone can help as I can't find the answer anywhere.
    I'm hoping you can help me.
    I am creating an online clothing shop website and am having trouble.
    I have created a main template from scratch that reflects in the mens and womens pages, and the contact, about etc pages with all headers, logos, footer, a spry menu etc. I made these pages from the main template via new - Page from template etc so any changes I made to the header, logo etc will easily reflect in all of these pages.
    This part is all fine.
    This is my issue - in the main template I have an editable region so that I can input different content ie. 'about' info on the 'about' page, and product info on the mens / womens pages etc.
    Basically in each page Mens / Womens I need category pages - tops, shirts etc. These are all in the drop down spry menu but I also want them as a list in the mens and womens pages.
    From the template I created the mens and womens pages and have now saved these as a template as there will be around 10 categories for each mens and womens (tops, shirts etc) that I want to be able to replect any changes, ie. in the 'mens template' instead of having to do it in each category page - as this will take a long time.
    The problem is that I put the list in the editable region in the mens template, but I now know any changes I make wont be relfected in the category pages I have made from the mens template as this is an editable region.
    How can I make a category list in the mens template page that will be reflected in each category page?
    I'm really stuck and have no idea how to do this, I'd appreciate any help.
    Thankyou in advance

    I don't recommend using multiple or nested Templates.  There are much better ways to do what you want without going down this very slippery slope.
    Use Server-Side Includes alone or with your main Template.
    Build a Dynamic Site with databases and server-side programming.
    E-commerce Solutions:
    Cartweaver (extension for Dreamweaver)
    http://www.cartweaver.com/
    Web Assist
    http://www.webassist.com/support/ecommerce-options.php
    Building an e-comm site with DW & PHP (video training) 
    http://www.lynda.com/Web-Interactive-Web-Design-Projects-tutorials/Building-eCommerce-Web- Site-Using-Dreamweaver-PHP/83091-2.html?utm_medium=affiliate&utm_source=ldc_affiliate&utm_ content=524&utm_campaign=CD4386&bid=524&aid=CD4386&opt=
    Nancy O.

  • Quick Question regarding an error with editable regions

    Hello,
    I am a co-op student and I work with other students as well, on our large company website. I have always been considered the cheif coder, and nobody knew the wesite layout and file directory as well as me. However, something terrible has happened while somebody was updating some information on one of your HTML pages.
    I logged in to Dreamweaver CS3 on afternoon to make a very simple text error change on our website. As soon as I hit "synchronize sitewide", it stated that there was no synchronization necessary, although I had already made a change. So then, on the template (.DWT) page, I thought I would backspace any character, and then retype it again in order for the "save" option to appear, so that I could save the template, and have it update all HTML pages, as well as the page that had just said "no synchronization necessary". I thought that I had to update the template first, which was strange, as I never had to do this before.
    When I clicked update, the error message that I got was that I have placed an editable region inside of a block tag. I checked the HTML pages as well as our template (.DWT) pages, and indeed, the <!--TemplateBeginEditable-->"Page Header"<!--TemplateEndEditable--> was embedded in a <h1></h1> pair. The pair appears black and delete-able in the template files, and grey in the HTML files, which is expected. However, I have been working at this institution for four months, and I recall that the <h1> tag pair had always been there since I remember. (How badly did this other person mess up?! =S)
    I tried to delete it from the .DWT file (the small editable region, and the <h1> tags), and now, what happens is that if I try to save a template so it updates all other HTML pages before synchronization, the template simply does not update anything, and I get no message whatsoever after clicking Save.
    Any help would be greatly appreciated. Thank you in advance for coping with these many details. I simply want to be able to update HTML pages again, because my boss really needs it, and I have never had such a problem before (having made much larger changes to this same website in the past)
    Thanks again,
    Mr. V

    How many child pages are you supporting with this DWT?   Hopefully less than 50 pages.
    Is your code valid?  HTML Validator - http://validator.w3.org
    Can you post a link to your DWT page, or copy and paste your code here?
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    www.alt-web.com/
    www.twitter.com/altweb
    www.alt-web.blogspot.com

  • Adding editable region tags moves my content in non-editable regions

    I have a template based on a template (the first with my navigation, and the second is based on the first with a sidebar added). When I add an editable region to the second template, it moves my sidebar down to leave a gap between the nav bar and the top of the sidebar. On the second template I want to add editable regions to the content area and to the sidebar. Even if I don't add any content to the editable reagions and just place the editable regions tags, my sidebar still moves down. I have tried adding two seperate editable regions and also adding one large editable region covering the content area and sidebar and the sidebar moved both times. My content area is a div floated left and the sidebar is a div floated right.
    I don't understand why anything is moving when I am only adding tags to make an area editable

    Do you have a container that the two divs are in and if so, are you clearing the floats? It's hard to give an answer without seeing the problem page.
    Jim

  • Can a div be an editable region in a template?

    This is my first attempt to work with templates. I have a main area in the center of the page where I want to be able to adjust font-size, and perhaps other text properties. I use a div called "textbox" I set it up as an editable region, but every time I try to change font-size, I am told that this is an uneditable region and the change will be discarded. Here is the code in my program:
    <!-- InstanceBeginEditable name="textbox" -->
        <div id ="textbox">
          <p>Here is some text in the box</p>
          <p> </p>
        </div>
        <!-- InstanceEndEditable -->
    Any suggestions?

    Okay - all is well.  Yet again I find myself spend as much or more time in Code view, than Design view. With the cursor inbetween a couple of divs, I could make it editable.  I found in a couple of cases the editable region was stuck in an odd random place in the page - Code view helped me figure it out.
    <div id="mainContent">
      <!-- InstanceBeginEditable name="mainContent" -->
    /* all the below is editable */
    <div id="featureBox1"><h3>Feature box one</h3>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
        </div><div id="featureBox2"><h3>Feature box two</h3>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
        </div>
    /* all the above is editable */
    <!-- InstanceEndEditable --> 
      </div><!-- end #mainContent -->

  • Open a QT movie in editable region of page (template)

    I am using templates for my site.  I'd like a movie link to open in a dependent page in the editable region of the page if possible.  Can't seem to make it happen.  The movie always opens in its own blank page.

    Did you embed a QT Player on the page? 
    http://www.mediacollege.com/video/format/quicktime/streaming/
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists 
    http://alt-web.com/
    http://twitter.com/altweb

  • Added editable regions in order to insert meta tags, but get code error. What did I do wrong?

    Hi,
    Made a website based on a template, and as so many people, was afterwards struggling with optimizing my titles, descriptions and keywords for SEO. These were/are locked in the head section of the template. I found lots of useful information on the forum to unlock this section, but apparently I am doing something wrong and I can't figure out what. The code error I get is that there is a syntaxis error in the template comment. Also I do see that the color of the code is maybe not the way it should be.
    This is the code I pasted in:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8" >
    <!-- TemplateBeginEditable name=”basisontwerp” -->
    <title>untitled document</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <meta name=”keywords” content=”keywords go here” >
    <meta name=”description” content=”description goes here” >
    <!-- TemplateEndEditable -->
    <link rel="icon" type="rel/icon" href="images/neroli_logo_mini.png" />
    <link rel="shortcut icon" href="images/neroli_logo_mini.png" />
    <style type="text/css">
    After that there is a whole bunch of stuff regarding two.Col.Elst.Lt.Hdr and style sheets etc. but there is a closing </head> tag just before my header and side bar section.
    Does anybody know what is wrong with my code? I just don't see it ...
    Thanks so much!!!

    He gek; probeer het opnieuw, nu rechtstreeks vanaf de site ipv als reply via de mail:
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">
    <head>
    <meta http_equiv="Content_Type" content="text/html" charset=utf-8" />
    <!-- TemplateBeginEditable name=”basisontwerp” -->
    <title>untitled document</title>
    <!-- TemplateEndEditable -->
    <!-- TemplateBeginEditable name="head" -->
    <meta name=”keywords” content=”keywords go here” >
    <meta name=”description” content=”description goes here” >
    <!-- TemplateEndEditable -->
    <link rel="icon" type="rel/icon" href="images/neroli_logo_mini.png" />
    <link rel="shortcut icon" href="images/neroli_logo_mini.png" />
    <style type="text/css">
    <!--
    body  {
    font: 100% Verdana, Arial, Helvetica, sans-serif;
    background: #666666;
    margin: 0; /* het is een goede gewoonte om de instellingen voor margin (marge) en padding (opvulling) van het element body op nul in te stellen en daarmee op de standaardinstellingen van de verschillende browsers */
    padding: 0;
    text-align: center; /* hiermee centreert u de container (het hoofdobject) in IE 5*-browsers Vervolgens wordt de tekst ingesteld op de standaardinstelling van links uitlijnen in de kiezer #container */
    color: #000000;
    /* Tips voor Elastic-lay-outs
    1. Aangezien de algehele grootte van de elastic-lay-outs is gebaseerd op de standaard lettertypegrootte van de gebruiker, hebben deze lay-outs een grotere mate van onvoorspelbaarheid. Bij een juist gebruik zijn ze echter wel toegankelijker voor diegenen die een groter lettertype behoeven omdat de lengte van de regel proportioneel blijft.
    2. De grootte van de div-elementen in deze lay-out is gebaseerd op een lettertypegrootte van 100% in het element body. Als u de tekstgrootte algeheel reduceert door middel van font-size: 80% voor het element body of voor #container, dient u niet te vergeten dat de complete lay-out proportioneel kleiner zal worden. Wellicht wilt u de breedtes van de verschillende div-elementen vergroten om dit te compenseren.
    3. Als de lettertypegrootte wordt gewijzigd d.m.v. verschillende waarden voor elk element div in plaats van voor het algehele ontwerp (bijv. #sidebar1 krijgt een lettertypegrootte van 70% en #mainContent krijgt een lettertypegrootte van 85%), leidt dit tot proportionele wijziging van de algehele grootte van elk van de div-elementen. Mogelijk wilt u dit aanpassen op basis van uw uiteindelijke lettertypegrootte.
    .twoColElsLtHdr #container {
    width: 46em;  /* deze breedte maakt een container (hoofdobject) die past een browservenster van 800 pixels, als de tekst wordt gehandhaafd in de standaard lettertypegroottes van de browser */
    background: #FFFFFF;
    margin: 0 auto; /* de automatische marges (d.m.v. auto), in combinatie met een breedte, centreren de pagina */
    border: 1px solid #000000;
    text-align: left; /* hiermee wordt de instelling text-align: center voor het element body genegeerd. */
    .twoColElsLtHdr #header {
    padding: 0 10px;  /* deze instelling voor padding (opvulling) komt overeen met de uitlijning links van de elementen binnen de div-elementen, die volgen op deze padding. Als een afbeelding wordt gebruikt in de #header in plaats van tekst, wilt u wellicht de padding (opvulling) verwijderen. */
    background-color: #DDDDDD;
    background-image: url(../images/achtergrond_kleur_buttons_mouse_over.png);
    border-top-color: #693;
    border-right-color: #693;
    border-bottom-color: #693;
    border-left-color: #693;
    border-top-width: thin;
    border-right-width: thin;
    border-bottom-width: thin;
    border-left-width: thin;
    .twoColElsLtHdr #header h1 {
    margin: 0; /* door de marge van het laatste element in het element div voor #header op 0 in te stellen voorkomt u het wegvallen van marges – een onverklaarbare ruimte tussen div-elementen. Als om het element div een rand loopt, is dit niet nodig aangezien dit tevens het wegvallen van de marge voorkomt */
    padding: 10px 0; /* door het gebruik van padding (opvulling) in plaats van een marge (via het element margin) kunt u het element van de randen van het element div vandaan houden */
    /* Tips voor sidebar1:
    1. Vergeet niet dat als u een waarde voor lettertypegrootte voor dit element div instelt, de algehele breedte van het element div dienovereenkomstig wordt aangepast.
    2. Aangezien we hier werken met em-waarden, verdient het de voorkeur om voor de zijbalk zelf geen padding (opvulling) te gebruiken. Deze wordt dan voor op standaards gebaseerde browsers toegevoegd aan de breedte, waardoor een nog onbekende daadwerkelijke breedte wordt gemaakt.
    3. De ruimte tussen de zijkant van het element div en de elementen erbinnen kan worden gemaakt door het aanbrengen van een linker- en rechtermarge voor dergelijke elementen, zoals wordt aangetoond door de regel ".thrColHybHdr #sidebar1 p".
    .twoColElsLtHdr #sidebar1 {
    float: left;
    width: 12em; /* de achtergrondkleur wordt weergegeven over de lengte van de inhoud in de kolom, maar niet verder */
    padding: 15px 0; /* binnen dit element div maakt de padding (opvulling) aan de onder- en bovenkant de visuele ruimte */
    background-image: none;
    background-color: #FFF;
    .twoColElsLtHdr #sidebar1 h3, .twoColElsLtHdr #sidebar1 p {
    margin-left: 10px; /* de linker- en rechtermarge moeten aan elk element worden gegeven dat in de kolommen aan de zijkant wordt geplaatst */
    margin-right: 10px;
    /* Tips voor mainContent:
    1. Als u dit element div voor #mainContent een andere waarde voor lettergrootte geeft dan het element div voor #sidebar1, worden de marges van het element div voor #mainContent gebaseerd op de lettergrootte ervan, terwijl de breedte van het element div voor #sidebar1 zal zijn gebaseerd op de lettergrootte daarvan. Mogelijk wilt u de waarden van deze div-elementen aanpassen.
    2. De ruimte tussen mainContent en sidebar1 wordt gemaakt met de linkermarge van het element div voor mainContent. De kolomruimte blijft gehandhaafd, ongeacht de hoeveelheid inhoud die het element div voor sidebar1 bevat. U kunt deze linkermarge verwijderen als u de tekst van het element div voor #mainContent de ruimte van #sidebar1 wilt laten opvullen wanneer de inhoud van #sidebar1 eindigt.
    3. Om het wegvallen van het zwevende element te voorkomen, zult u wellicht via uitproberen een schatting van de maximale grootte van de afbeelding of het element moeten bepalen, aangezien deze lay-out is gebaseerd op de lettertypegrootte van de gebruiker in combinatie met de door u ingestelde waarden. Maar als de gebruiker de lettertypegrootte van diens browser echter op kleiner dan normaal heeft ingesteld, is er in het element div voor #mainContent minder ruimte beschikbaar dan u tijdens het uitproberen ziet.
    4. In de onderstaande voorwaardelijke opmerking van Internet Explorer wordt de eigenschap zoom gebruikt om "hasLayout" mee te geven aan mainContent. Hierdoor wordt voorkomen dat zich diverse IE-specifieke bugs voordoen.
    .twoColElsLtHdr #mainContent {
    margin: 0 1.5em 0 13em; /* de rechtermarge kan worden opgegeven in em- of pixelwaarden. Deze marge maakt de ruimte langs de rechterzijde van de pagina. */
    .twoColElsLtHdr #footer {
    padding: 0 10px;
    background-color: #FFF;
    .twoColElsLtHdr #footer p {
    margin: 0; /* door de marges van het eerste element in de footer (voettekst) in te stellen op 0 vermijdt u het risico dat de marge wegvalt – een ruimte tussen div-elementen */
    padding: 10px 0; /* door het gebruik van padding (opvulling) voor dit element maakt u ruimte (op dezelfde manier als door middel van een marge), zonder het probleem van wegvallende marges */
    /* Miscellaneous classes for reuse */
    .fltrt { /* dit exemplaar van class kan worden gebruikt om een element aan de rechterzijde van uw pagina te laten zweven. Het zwevende element moet voorafgaan aan het element dat, op de pagina, naast het zwevende element moet staan. */
    float: right;
    margin-left: 8px;
    .fltlft { /* dit exemplaar van class kan worden gebruikt om een element aan de linkerzijde van uw pagina te laten zweven. */
    float: left;
    margin-right: 8px;
    .clearfloat { /* dit exemplaar van class moet op een element div of break zijn geplaatst en dient het laatste element te zijn vóór de afsluiting van een container (hoofdobject) die op zijn beurt een zwevend object volledig dient te bevatten */
    clear:both;
        height:0;
        font-size: 1px;
        line-height: 0px;
    .navigatie {
    color: #9F3;
    .twoColElsLtHdr #container #footer table tr td {
    font-family: Arial, Helvetica, sans-serif;
    -->
    </style><!--[if IE]>
    <style type="text/css">
    /* plaats in deze voorwaardelijke opmerking css-correcties voor alle versies van IE */
    .twoColElsLtHdr #sidebar1 { padding-top: 30px; }
    .twoColElsLtHdr #mainContent { zoom: 1; padding-top: 15px; }
    /* de bovenstaande softwaregebonden eigenschap zoom geeft IE de hasLayout die IE nodig heeft om verschillende bugs te vermijden */
    </style>
    <![endif]-->
    <script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>
    <script type="text/javascript">
    <!--
    function MM_preloadImages() { //v3.0
      var d=document; if(d.images){ if(!d.MM_p) d.MM_p=new Array();
        var i,j=d.MM_p.length,a=MM_preloadImages.arguments; for(i=0; i<a.length; i++)
        if (a[i].indexOf("#")!=0){ d.MM_p[j]=new Image; d.MM_p[j++].src=a[i];}}
    //-->
    </script>
    <link href="../personoil.css" rel="stylesheet" type="text/css" />
    <link href="../SpryAssets/SpryMenuBarVertical.css" rel="stylesheet" type="text/css" />
    <link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css" />
    </head>
    <body class="twoColElsLtHdr">
    <div id="container">
      <div id="header">
        <table width="100%" border="0">
          <tr>
            <td width="25%" height="130"><img src="../images/neroli logo kleiner.gif" alt="" width="97" height="130" align="left" /></td>
            <td width="49%"><img src="../images/copy heading.png" width="344" height="35" vspace="0" align="middle" /></td>
            <td width="26%"><img src="../images/neroli logo kleiner.gif" alt="" width="97" height="130" align="right" /></td>
          </tr>
        </table>
      <!-- end #header --></div>
      <div id="sidebar1">
        <ul id="MenuBar1" class="MenuBarVertical">
          <li><a href="../index.html">Personoil</a></li>
          <li><a href="../waaromolie2.html">Waarom olie van Personoil?</a></li>
          <li><a class="MenuBarItemSubmenu" href="../ingredienten.html">De natuurlijke ingrediënten</a>
            <ul>
              <li><a href="../basisolien.html">De basisoliën</a></li>
              <li><a href="../essentieleolien.html">De essentiële oliën</a></li>
    </ul>
          </li>
          <li><a href="../huidtypes.html">Jouw huidtype</a></li>
          <li><a href="../gezichtsmassage.html">Gezichtsmassage en andere tips</a></li>
          <li><a href="../bestellen.php">Advies en bestellen</a></li>
        </ul>
    <h3> </h3>
      <!-- end #sidebar1 --></div>
      <div id="mainContent">
        <ul id="MenuBar2" class="MenuBarHorizontal">
          <li><a href="../contact.html">Contact</a>      </li>
          <li><a href="../betalen.html">Veilig betalen</a></li>
          <li><a href="../verzenden.html">Verzending</a>      </li>
          <li><a href="../voorwaarden.html">Algemene voorwaarden</a></li>
        </ul>
        <!-- TemplateBeginEditable name="editregion" -->
        <&nbsp>
        <h1> Hoofdinhoud </h1>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. </p>
        <p>Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at,  odio. Donec et ipsum et sapien vehicula nonummy. Suspendisse potenti. Fusce  varius urna id quam. Sed neque mi, varius eget, tincidunt nec, suscipit id,  libero. In eget purus. Vestibulum ut nisl. Donec eu mi sed turpis feugiat  feugiat. Integer turpis arcu, pellentesque eget, cursus et, fermentum ut,  sapien. Fusce metus mi, eleifend sollicitudin, molestie id, varius et, nibh.  Donec nec libero.</p>
        <h2>Kop niveau H2 </h2>
        <p>Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Praesent aliquam,  justo convallis luctus rutrum, erat nulla fermentum diam, at nonummy quam  ante ac quam. Maecenas urna purus, fermentum id, molestie in, commodo  porttitor, felis. Nam blandit quam ut lacus. Quisque ornare risus quis  ligula. Phasellus tristique purus a augue condimentum adipiscing. Aenean  sagittis. Etiam leo pede, rhoncus venenatis, tristique in, vulputate at, odio.</p>
      <!-- TemplateEndEditable -->
      <!-- end #mainContent --></div>
    <!-- Dit wiselement dient onmiddellijk te volgen op het element div voor #mainContent om het element div voor #container te dwingen om alle zwevende elementen van een lager niveau te bevatten --><br class="clearfloat" />
       <div id="footer">
         <p> </p>
      <!-- end #footer --></div>
    <!-- end #container --></div>
    <script type="text/javascript">
    <!--
    var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgRight:"SpryAssets/SpryMenuBarRightHover.gif"});
    var MenuBar2 = new Spry.Widget.MenuBar("MenuBar2", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
    //-->
    </script>
    <script type="text/javascript">
    var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
    document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
    </script>
    <script type="text/javascript">
    try {
    var pageTracker = _gat._getTracker("UA-6508405-2");
    pageTracker._trackPageview();
    } catch(err) {}</script>
    </body>
    </html>

  • Error when editing region of the placeholder

    I defined a placeholder using the following documentation
    http://www.oracle.com/technology/products/content-management/ucm/sitestudio10gr4tutorials/AddingContent/addingcontent_viewlet_swf.html
    To summarize, following are the steps that I followed
    1. Created following site assets
         a. One element definition with name BodyContent of wysiwyg
         b. One region definition of name SampleRegionDef. Then added the above element to this region definition
         c. One region template by choosing SampleRegionDef as region def with name SampleRegionTemp. Then inserted the BodyContent element in the region template page. there is no other content in the region template
         d. One Placeholder definition with name SamplePlaceHolderDef and selected the SampleRegionDef as the region and SampleRegionTemp as the template.
    2. Next I have created a place holder with name SamplePlaceHolder and selected the SamplePlaceHolderDef for primary and secondary pages.
    3. I placed the SamplePlaceHolder on the home page.
    4. I assigned a new contributor data file to the place holder (region template)
    After doing this I launched the site in contributor mode. I noticed edit icon apperaing for the placeholder. I cliked on edit icon and I see the below error message
    ==========================================================================================
    Error
    Unable to perform the action due to the following reasons:
    [+] The Region Definition could not be loaded. The required parameter 'regionDefinition' could not be found.
    =========================================================================================
    What could be the problem? Ithere anything more needed to be done here?
    Regards,
    Pratap

    Hi Pratap,
    Double click on the placeholder that is on you template page
    Click on the check box optionally specify place holder definition
    Select your place holder definition file from the drop down.
    Save template page open in browser go to contribution mode.
    Have already done this?
    regards,
    deepak

  • Error adding new function in order template

    Hi,
    When i am trying to add a new function to order Template under /contolData/Functions/ form data dictonary
    I am getting error :
    Element with same name exist.The following nodes can not be added to the order.
    (no namespace):/ControlData/Functions/MyNewFunction
    (no namespace):/ControlData/Functions/MyNewFunction/componentKey
    Thanks
    Harman

    Hi Harman,
    You might need to be more specific before I can help you. What have you done, and which step you run into the error? I supopse you have created a new "function" Order Component, and created the required Control Data nodes in Data Dictionary (what have you added?), right? So, when you go into the Order Template tab of the new Order Component (which would be empty since it was newly created), and you try to "select from Dictionary" the corresponding ControlData for the function (e.g. /ControlData/Functions/MyNewFunction), that such an error occurs?
    Have you assigned a process for this Order Component? Studio does not allow adding control data to it unless a process is assigned.
    Btw, you should define a namespace for your Order Components (and other orchestration entities). The OSM server uses namespace to locate these entities among cartridges.
    Cheers,
    Daniel Ho
    Product Management -- OSM

  • Can't manually add editable regions to head in template

    When I created my main template in Dreamweaver CS6 for my website, I had copied most of the page code from another layout I already had, including the head code.  I did not realize there were already editable regions built into the head section of the Dreamweaver template and deleted them when I pasted my previous code without adding new ones.  I then added an editable region to the body and started created pages using the template.
    Everything works well and updates properly when I make changes to the template but now that I am trying to add those editable regions back to the head section so I can change the page title (and possibly add more responsive code), it doesn't work.  I copied and pasted the following code into my template file in Dreamweaver and it saves in the template telling me it's updating the related pages, but when I open those individual pages in Dreamweaver, the code isn't there and those regions are not editable; only the original editable region I created in the body exists and works properly.  Everything else continues to work perfectly.
    Here is the code I pasted into the head around the <title> tag:
    <!-- TemplateBeginEditable name="doctitle" -->
    <title>Collings Document Database</title>
    <!-- TemplateEndEditable -->
    And here is the code I pasted into the head just before the </head> tag:
    <!-- TemplateBeginEditable name="head" -->
    <!-- TemplateEndEditable -->
    </head>
    Any help would be appreciated.  From everything I've read on these forums after searching, it sounds like pasting that code should work but I continue to get the results mentioned.  Thank you.

    Thanks for the response.  I've run the template code through the validator and the following two errors are the only ones that showed up.  I don't see how either of these would cause this issue.  Thoughts?
    Line 5, Column 53: Bad value X-UA-Compatible for attribute http-equiv on element meta.
    <meta http-equiv="X-UA-Compatible" content="IE=Edge">

    Line 27, Column 127: An img element must have an alt attribute, except under certain conditions. For details, consult guidance on providing text alternatives for images. …gs_guitars_stroke_clear.png" width="184" height="81" class="scalable">  </div>

Maybe you are looking for

  • TS3276 My mail wont delete emails

    Okay so in Mail on my new iMac I go to delete an email. At first it appears to go to the trash, I go check the trash sometimes its there sometimes its not. I go back to my mail and the email I deleted re appears in my inbox. Why is this? And how can

  • Cisco Desktop Administrator is not synch with CRS 5.0(2)

    I am trying to add a new staff as supervisor in Cisco Desktop Administrator. CRS 5.0(2) is configured and showing him as supervisor. In Destop Admin I have selected Call Centre1 and setup > Sync Directory service the message appears as"At least one e

  • Error "the notification doesn't exists" when use BAPI_ALM_ORDER_MAINTAIN

    Hi gurus, I have a problem with a BAPI_ALM_ORDER_MAINTAIN. My order has 3 notifications on the tab "Objects" and I want to remove one. But when i called the BAPI, i get the error message "Notification 100047495 does not exist". The content of the tab

  • I-tunes will not launch

    I can not get my i-tunes to launch in normal mode or safe mode, I have uninstalled, reinstalled & rebooted, as well as repairing apple support 32 and 64 bit in programs My OS is windows 7 I get the error: Problem signature:   Problem Event Name: APPC

  • Former itunes installation from external hdd syncing with new installation.

    Hello, i need some help! My laptop has a severe mainbord damage, it's not economical to repair it. so, i'm going to mount the 2,5" hdd in an external hdd case with usb. in addition, i get a new iphone due to fluid damage. so my itunes with the iphone