Page includes in html templates

I see <% include file="header.html" %> in html template working for 'HTML' gallery type web engines.
<br />
<br />But, it doesn't work if the gallery type is 'Flash'. It seems the only supported directive includes are %variablename% format.
<br />
<br />Why LR is restricting lots of features for Flash based galleries? Is this by design or restricted for some other reasons or a bug?
<br />
<br />I wish if there is some flag somewhere that can be turned on so that Flash gallery type will have all the features of html. Currently I don't think it'll encourage any developer to write/adapt flash based web plugin for LR.
<br />
<br />Chris

Sean, Thanks for your reply. SlideShowPro is no different. Please check any of the html pages in the SlideShowPro plugin. It doesn't use <% %> directives. Only %var% is used.
<br />
<br />Yes, I'm aware of what include does. That's exactly the reason why I need it in Flash gallery type. Keep the header and footer outside the template for easy user editing.
<br />
<br />To explain the issue in easier terms, lua coding is allowed in the template files only if you set gallery type as 'Html'. If you change it to 'Flash', it won't work.
<br />
<br />Even simpler,
<br />You can use <% %> only in html gallery types.
<br />
<br />It's not just 'include'. If <% ... %> is allowed for Flash gallery type, you can do a lot of lua scripting in your html templates. All spoiled by LR limitation :-)

Similar Messages

  • Cannot publish 1 page in CS4. Other pages including index.html ok. Error message results.

    After many months of no difficulty, I suddenly cannot publish changes to one of my pages (all others work) without getting the error message 'Another instance of Contribute is doing a workflow operation. Do you want to break the workflow and continue.....?' Whether I say yes or no and follow the prompts, it doesn't work. One way lets me exit, the other locks up my computer and I have to 'end task' to get control back. I hoped that the answer to the 'cannot publish index page' thread would help, but I didn't understand because most of this stuff is over my head. The only thing unusual I can dectect is the page name has an # sign after html as in 'name.html#tuition.' The word tuition refers to a pointer on the page. When I switch to edit mode, an asteric * appears after 'html' on the page name. I do not see that on any other page when I edit. I have CS4 version 5. Can anyone help? I don't know how many people there are in India, but I talked to half of them in a 2.5 hour 'session' in which I was transferred in a least 3 complete loops to every department and passing 'go' 3 times before some techie finally said I should email my question in and will get a reply within 3 days. Yeah, right. Worst tech support experience I have had in 10 years.

    Hi,
         Can you try deleting the Preferences and the Contribute's User Configuration folder. You will lose your website connections, you can recreate them again after relaunching Contribute.
    If you have installed Contribute in Mac, go to <Username>/Library/Application Support/Adobe folder and delete Contribute CS4 folder there. Also, go to <Username>/Library/Preferences/ folder and delete the 'Adobe Contribute 5 Preferences' file.
    If you have installed Contribute in Windows XP, the Contribute's Configuration folder will be in C:\Documents and Settings\<your username>\Local Settings\Application Data\Adobe\. Delete the Contribute CS4 folder there. To clear the registry for Contribute, type 'regedit' in the Run window.(Click Start, and click Run, and then type 'regedit' in the text field.) Select HKEY_CURRENT_USER, then Software, then Adobe, then Contribute CS4. Click Delete button. Close the Registry Editor window.
    The <username>, I have mentioned above is the name with which you will have logged into the machine.
    Now, Relaunch Contribute and connect to your website and try editing the web pages from your website. Can you try this?

  • How to bind Context elements to a HTML template

    Hi,
    I want to display all the context elements in my webDynpro application in a html page, I have html template my requirement is to bind all the context elements to fields in the html template.please provide me the solution.
    thanks,
    kishore.

    Hi Kishor,
    I do not think there is some straight forward solution for this scenario.
    You need to create two applications 1 webdynpro application and one portal application.
    What you can do is Pass the context values from webdynpro application to a flat file and store then in that(every time create a new flat file). Now after successfully creation of flat file call the portal application which reads the flat file and get the context values and set them.
    If you require more info, i can help you.
    Regards
    Narendra

  • Include HTML page in an HTML page

    I know how to do an include of an HTML page inside an ASP
    page, but I am basically trying to do the same thing with an HTML
    page - that is include HTML within HTML - but it doesn't seem to be
    working when I test in a browser. It displays fine in DW though!
    The only way to successfully create an include in HTML pages
    seems to be to use the library method.
    Here is my include code:
    <!--#include file="../_includes/footer.html" -->
    Is this wrong for an HTML page?
    Thanks
    Mat

    Is the parent file named with an *.shtm(l) extension?
    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
    ==================
    "matthew stuart" <[email protected]> wrote
    in message
    news:g7hd6v$e53$[email protected]..
    >I know how to do an include of an HTML page inside an ASP
    page, but I am
    > basically trying to do the same thing with an HTML page
    - that is include
    > HTML
    > within HTML - but it doesn't seem to be working when I
    test in a browser.
    > It
    > displays fine in DW though!
    >
    > The only way to successfully create an include in HTML
    pages seems to be
    > to
    > use the library method.
    >
    > Here is my include code:
    >
    > <!--#include file="../_includes/footer.html" -->
    >
    > Is this wrong for an HTML page?
    >
    > Thanks
    >
    > Mat
    >

  • How to embed a HTML Page in a Web Template and display it

    Hi All
    Can you please share ideas how I can embed a HTML page in a web template and how I can make it displayed as a popup when a button is pressed.
    Also, how do I call a HTML page stored in Portal KM from the press of a button in the web template.
    Your help is greatly appreciated.
    Thanks
    Karen

    Using C# or javascript to authenticate the user to AD to read the property directly will be very difficult. Creating a custom user profile property and adding a sync from AD to that property is definitely the easiest way to do what you are describing.
     Once its in User Profiles there are lots of samples on how to add it to the page.  
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Include a html page in another html page

    How do I include a html page in another html page? I have 7
    separate page making up a website. I made a separate page for the
    bottom navigation which I want to include for each page. Instead of
    making up a separate nav bar for each page.
    Thanks for your time.
    Todd Dignan

    Just remember that the file being included CANNOT be a
    stand-alone HTML
    page - it must not contain <html>, <head>, or
    <body> tags if you want to
    continue working within DW.
    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
    ==================
    "nX07" <[email protected]> wrote in message
    news:fm9pvr$rn6$[email protected]..
    > Hey Todd,
    >
    > Depending on your web site's server environment, you can
    do it a few ways.
    >
    > First, and most convenient is if the server you are on
    has PHP, the simple
    > php
    > include function will do the trick.
    >
    > Just place this in where the HTML would actually go for
    the footer
    >
    > <?php include("fileofthebottom.html"); ?>
    >
    > If you don't have PHP, you should be able to use SSI
    (Server Side
    > Includes).
    > same principle applies as above, and is simple to
    understand:
    >
    > <!--#include file="fileofthebottom.html" -->
    >
    > If for some reason you can't do SSI, the other option
    would to be using a
    > frame or iframe, which is not recommended for several
    reasons; mainly
    > accessibility.
    >
    > The simple code is:
    > <iframe src ="fileofthebottom.html"width="whatever"
    > height="whatever"></iframe>
    >
    > Hope this helps :)
    >
    >
    >

  • Problems Uploading a Pages file in html format including pictures to web pa

    I have problems uploading a Pages file in html format to a web page.
    The files itself is downloaded but the images are not. How can I upload a page file in html including the pictures or illustrations?

    I just bought a macbook as well as the iwork software. I am having a few problems. I am a student and when I try to print out documents (originally word documents) it puts them automatically into textedit instead of pages. Also, the pages get all screwed up, things are missing, etc. How do I make pages my default and do i need to export? import? or do something so that these documents show up perfectly in pages?
    A second questions- When i try to print out slideshows in keynote (originally from powerpoint) the handouts print on the little edge of the paper horizontally rather than the long way. I am hoping these are easy adjustments.
    I would appreciate any help anyone can give me.
    Thank you!

  • [svn:fx-trunk] 9707: Our stock html template now propagates ${bgcolor} to the page body' s background-color.

    Revision: 9707
    Author:   [email protected]
    Date:     2009-08-27 13:15:29 -0700 (Thu, 27 Aug 2009)
    Log Message:
    Our stock html template now propagates $ to the page body's background-color.
    QE notes: Requires documentation of new behavior (relative to Flex 3).
    Doc notes: None.
    Bugs: SDK-22723
    Reviewer: Peter F.
    Tests run: Manual Flash Builder tests.
    Is noteworthy for integration: Yes, new html template.
    Ticket Links:
        http://bugs.adobe.com/jira/browse/SDK-22723
    Modified Paths:
        flex/sdk/trunk/templates/swfobject/index.template.html

    Horgykitkat wrote:
    What I found after taking out the heights from the text areas is that I was left with uneven text column lengths (alternating beige areas). So I created a repeatable jpg with the same alternating beiges and put it as the background of the bodyArea tag. Again, if there is a better way, please let me know!
    A repeating background image to 'fake' equal height columns is perfectly ok.
    It won't work IF your page is responsive but it isn't so no problem. If it were responsive a better solution would be to take advantage of the css property display: table; and display: table-cell;
    In reference to your footer background color not showing I would assume you have floated items within the footer container. If so then you need to clear those floated items which allows the footer container to wrap itself around the floated items inside it.
    You would do this by using css - overflow: hidden; - on the parent container which has the floats inside it.

  • Need to Open Another jspx page as popup from template

    Hi everyone,
    I have one more question about popups and template. I'm working on JDev 11gU2 ADFRC
    I have one template for my all pages, and there is a link on my template to show user information. for that i need to fetch the info of logged in user from database. so i must have to make a page definition of my user info page.
    But problem is when i click the info link from my template to open user info page. it is not opening and giving page refresh error.
    actually in my template the page source is -
    <f:subview id="userInfo">
                <jsp:include page="/popUps/UserInfo.jspx"/>
    </f:subview>
    <af:commandNavigationItem text="UserInfo"
                                                  immediate="true">
    <af:showPopupBehavior popupId="::userInfo:popup1"
                                                triggerType="action"/>
    </af:commandNavigationItem>and in My Account Info page source is -
    <?xml version='1.0' encoding='windows-1252'?>
    <jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" version="2.1"
              xmlns:f="http://java.sun.com/jsf/core"
              xmlns:h="http://java.sun.com/jsf/html"
              xmlns:af="http://xmlns.oracle.com/adf/faces/rich">
      <jsp:directive.page contentType="text/html;charset=windows-1252"/>
      <!--oracle-jdev-comment:auto-binding-backing-bean-name:backing_popUps_AccountDetailsPopUp-->
      <af:popup binding="#{backing_popUps_AccountDetailsPopUp.popup1}"
                      id="popup1">
              <af:dialog title="Account Detail" type="none"
                         inlineStyle="margin:0.5px,0,0,0.5px;"
                         closeIconVisible="#{!backing_popUps_AccountDetailsPopUp.editMode}"
                         partialTriggers="panelBox1 panelBox2 panelBox3"
                         binding="#{backing_popUps_AccountDetailsPopUp.dialog1}"
                         id="dialog1">
                <af:decorativeBox topHeight="25px"
                                  inlineStyle="margin:0.5px; height:460px;"
                                  theme="dark"
                                  binding="#{backing_popUps_AccountDetailsPopUp.decorativeBox1}"
                                  id="decorativeBox1">
                  <f:facet name="center">
                    <af:panelStretchLayout startWidth="5px" endWidth="0px"
                                           topHeight="0px" bottomHeight="0px"
                                           binding="#{backing_popUps_AccountDetailsPopUp.panelStretchLayout1}"
                                           id="panelStretchLayout1">
                      <f:facet name="center">
                        <af:decorativeBox theme="light"
                                          inlineStyle="height:430px; width:482px;"
                                          binding="#{backing_popUps_AccountDetailsPopUp.decorativeBox2}"
                                          id="decorativeBox2">
                          <f:facet name="center">
                            <af:panelGroupLayout xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
                                                 inlineStyle="padding:1%;"
                                                 partialTriggers="commandLink1 commandLink2 commandLink3 commandLink4 commandLink5 commandLink6 commandLink8 commandLink9 commandLink10"
                                                 binding="#{backing_popUps_AccountDetailsPopUp.panelGroupLayout1}"
                                                 id="panelGroupLayout1">
                              <af:panelBox text="Employee Information"
                                           partialTriggers="commandLink1 commandLink2 commandLink3"
                                           binding="#{backing_popUps_AccountDetailsPopUp.panelBox1}"
                                           binding="#{backing_popUps_AccountDetailsPopUp.spacer2}"
                                           id="spacer2"/>
                              </f:facet>
                            </af:panelGroupLayout>
                          </f:facet>
                        </af:decorativeBox>
                      </f:facet>
                      <f:facet name="start">
                        <af:spacer width="10" height="10"
                                   binding="#{backing_popUps_AccountDetailsPopUp.spacer3}"
                                   id="spacer3"/>
                      </f:facet>
                    </af:panelStretchLayout>
                  </f:facet>
                  <f:facet name="top">
                    <af:panelGroupLayout binding="#{backing_popUps_AccountDetailsPopUp.panelGroupLayout8}"
                                         id="panelGroupLayout8">
                      <af:outputText value="Account Detail : 900101"
                                     inlineStyle="font-weight:bold; font-size:14px;"
                                     binding="#{backing_popUps_AccountDetailsPopUp.outputText10}"
                                     id="outputText10"/>
                    </af:panelGroupLayout>
                  </f:facet>
                </af:decorativeBox>
                <f:facet name="buttonBar">
                  <af:commandLink text="Close"
                                  inlineStyle="font-weight:bold; color:Blue;"
                                  disabled="#{backing_popUps_AccountDetailsPopUp.editMode}"
                                  partialTriggers="panelBox1 panelBox2 panelBox3"
                                  shortDesc="#{backing_popUps_AccountDetailsPopUp.editMode ? 'Can not close in edit mode...' : 'Close Window'}"
                                  binding="#{backing_popUps_AccountDetailsPopUp.commandLink11}"
                                  id="commandLink11">
                    <af:resetActionListener/>
                  </af:commandLink>
                </f:facet>
              </af:dialog>
            </af:popup>
    </jsp:root>Actually i need to open a page globally and i can't put this link to each page. so that i put this on Template.
    I made a popup page too to log out from application in the same way, it is working file, but the difference is that page does not have any page def.
    But account info page has.
    I want to use it without adding dialog: in ADF-CONFIG.xml page
    Any help to solve this?
    Thanks
    Fizzz...

    hey guys,
    I have 2 pages test1 and test2(.jspx).In test2 page I have defined an popup and i want that in that pop-up test1.jspx should get loaded.
    Can any body help me on this.???Will really appreciate this..............

  • How do I create a master page when using Project7 templates?

    Hi,
    I am using P7 templates to easily create a nice website. However, I would like to create for example the main menu only once and have it re-used on every page or at least every page I want to. I think this is a called a masterpage (?) where you can tag parts to be re-used on other pages.
    Can somebody please tell me where I can find support, examples, tutorials on this? Or can somebody tell me how to do this in a P7 template?
    Thanks in advance!!
    Robert (Netherlands)

    You want to save your project page as a DW Template from which your other site pages will be spawned.  Or, you want to use Server-Side Includes (SSIs).
    Guidance  on when to use DW Templates and SSIs  -
    http://www.adobe.com/devnet/dreamweaver/articles/ssi_lbi_template.html
    More on DWTemplates -
    http://forums.adobe.com/message/2032104#2032104
    More on SSI -
    http://forums.adobe.com/message/2112460#2112460
    Nancy O.
    Alt-Web Design & Publishing
    Web | Graphics | Print | Media  Specialists
    http://alt-web.com/
    http://twitter.com/altweb
    http://alt-web.blogspot.com

  • Deciphering Aperture Web Themes: the html templates v3

    version 3 of my Aperture Web Theme html template reference. enjoy
    the html templates.
    rkid attributes:
    Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
      <ul id="nav" rkid="navbar">
    These are the rkid values that I've identified so far:
      "navbar"
        a <ul> element containing all of the navigation elements.
      "active" and "inactive"
        rkid attributes to enable the coder to place different formatting on
        current and non-current page numbers in the navbar.
        eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
          <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
      "content"
        a <div> containing all of the album images and their metadata.
      "pictureblock"
        a mandatory <table> in which the images are placed, one image per <td>.
        the <table> must even be used on the Detail page where only one image is
        displayed.
        the metadata will be within the "pictureblock" table if more than one
        image is displayed so that the metadata can be tied to the image. if
        only one image is displayed; i.e., the Detail page; the metadata may be
        in a <td> outside of the table that the image is in but still within the
        "content" div, usually in the following format:
          <div rkid="content">
            <table>
              <td>metadata
              <td><table rkid="pictureblock">
      "image"
        the rkid for the <img> elements containing the album images, frequently
        placed in <dt> elements within the table's cells.
      "metadata" (added in Decipher v3)
        all metadata for the respective image is specified within this element.
        everything within the element is repeated for every metadata value.
        the Aperture themes use the <ul> element but <div> also works:
          <div rkid="metadata"><p>metaname: metavalue</p></div>
      "titleblock"
        a <div> containing the title text; usually <h3>; for Journals. the <h3>
        element within this element must be given the attribute rkid="text" or
        Aperture will ignore it.
      "textblock"
        a <div> containing the description text for Journals. as with the
        titleblock, the <p> element/s within this div must be given the
        attribute rkid="text".
      "text"
        the rkid given to the text data within the titleblock and textblock
        elements.
    Place holders:
      PageTitle
        used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
      IndexPageURL
        the gallery page/s URLs; may be more than one.
      ThumbImageURL
        the href links for the images, whether thumbnails or detail full size.
      DetailPageURL
      used within navbar:
        PageCount
        PageNumber
        PreviousPageNumber
        PreviousPageURL
        NextPageNumber
        NextPageURL
        PageCount the total number of pages
        PageNumber includes all of the page numbers listed in the navbar, one
          occurrence for each page.
        _Previous and _Next are more specific and are currently used to draw the
          prev/next arrows in the navbar.
      ImageName
      ImageNameSpace
      PlateNameSpace
      PlateNumberSpaceSlash
        *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
          chosen.
        used to represent an index of the image in the album. the first image
          shown gets the index 1, the second 2 and so on.
        for the Image placeholders, the word 'Image' is used.
        for the Plate placeholders, the word 'Plate' is used.
        space indicates an extra space after the index, probably for html
          formatting purposes because it's only used within <dt> elements.
        slash indicates an extra / character after the index.
        examples:
          ImageName > 'Image 1'.
          ImageNameSpace > 'Image 1 '.
          PlateNameSpace > 'Plate 1 '.
          PlateNumberSpaceSlash > '1 / '.
      metaname
      metavalue
        the placeholders for all of the metadata names/values in the selected
        metadata set.
      PageWidth
        not sure if Aperture calculates it based on the width and number of
        images being displayed in both gallery and detail pages.
        don't know why it's only used in the Special Occasion theme.
      CellWidth
        the width of the table cells containing the album images. not
        necessarily the width of the images. may include margins as specified in
        the albuminfo.plist files.
      ImageWidth
        the width of the image.
      TableWidth
        the width of the pictureblock table. it can probably be applied to other
        elements too but it's length is almost certainly calculated from the
        pictureblock table.
    Operative attributes:
      removeonfirstpage="yes"
        used in the navbar to remove the Prev link from the first page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonlastpage="yes"
        used in the navbar to remove the Next link from the last page.
        because it's applied to the <a> element, the <a> element is removed
          while leaving an empty <li> in place.
      removeonsinglepage="yes"
        used in the navbar to remove elements when there's only one page.
        used in a <div> in the Art Collection to remove the whole navbar on
        single pages.
      contenteditable="yes"
        used in text elements to indicate that the user can customise the text.
        not necessary in titleblock and textblock rkid="text" elements.
        in elements outside of the titleblock and textblock elements, content
        will not be truly editable unless a textid is assigned to the text
        elements. unfortunately, all text elements with textids are always
        'common' and can not be specific to any one image.
      common="yes"
        the element is seen on all pages.
    Other attributes:
      metaseparator="|"
        used in metadata formatting, within the metadata lists.
        you can add additional characters. for example, the metaseparator
        in the Stock Black theme is " | "; ie, a | bar with a space on both
        sides. (Decipher v3)
        if the metaseparator is specified and the html template places the
        metadata into <li> elements as it does in most of the current themes,
        then it produces non-standard html code with the metaseparator between
        concurrent <li> elements.
      metalayout="paragraph"
        used in metadata formatting, within the metadata lists.
        if not specified, the metadata will not be exported. (Decipher v3)
      singlenesting="yes"
        used in metadata formatting. not sure what it does yet.
      textid="x"
        used to id text elements outside of the titleblock and textblock
        elements.
        possibly no limit to the number and id names used.
        examples used:
          textid="copyright"
          textid="header1"
      picturename="x"
      pictureimage="true"
        picturename gives the image an id.
        pictureimage="true" tells Aperture that the image is a static image
        which can be designated by the user during setup of the album. they show
        up in Aperture as grey blank rectangles with cross-eyes in the middle.
        they do not need to be inside the "content" element
        with picturename and pictureimage, we can place as many static images on
        the page as we wish.
    Assertions:
      Aperture uses the rkid values to identify the areas of the html to be
      repeated for the respective objects.
      standard id and class attributes are only used by the css for formatting and
      not by Aperture to write the html data.
    Notes:
      Aperture is hardcoded to expect and require that the album images are always
      within a <table rkid="pictureblock"> element. it is not possible to place
      album images outside of the table. all album images must be placed within
      <td> cells within the table. the <td> code is repeated for each image.
      image metadata is also normally within the rkid="content" element although
      it can be outside of the rkid="pictureblock" element.
      by default, the textblock rkid="text" element is added when the T+ button is
      pressed within Aperture. the textblock element is switched with the
      titleblock element when the Title/Text toggle button is clicked.
      width and height attributes of <img> elements are rewritten by Aperture
      based on the inserted images. placeholders aren't necessary within <img>
      elements.
      comments are stripped from the html before export some but some
      Aperture-proprietary attributes are forgotten and left behind.
      some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
      doctype.
      all markup is converted and exported in UPPER-CASE. personally, I prefer
      lower-case.
      high-ascii characters entered by the user are not converted to their html
      entities when available. eg, the © character.
      multiple <p> elements can be inserted into the titleblock and textblock
      <div> elements but each of them must have the rkid="text" attribute. any
      element without this attribute will be ommitted by Aperture.
      the reason there are Smart Galleries but no Smart Journals is because you
      need to write text between each row of images.
      titleblock and textblock elements will not be applied to Galleries or Detail
      templates; only to Journals.
      if there are more than one titleblock or more than one textblock, only the
      first will be used by Aperture.
      upon export, Aperture will remove everything from within the rkid="content"
      element which is not the pictureblock, titleblock or textblock elements.
      (Decipher v3)
      some of the Aperture templates have xhtml doctypes but are exported from
      Aperture with html 4.0 loose doctypes. weird! worthy of note is the fact
      that UPPER-CASE element names is not permitted with xhtml which is
      case-sensitive. (Decipher v3)
    Questions:
      are there variable scopes with each rkid? eg, within the "content" rkid, can
      every variable/placeholder be accessed?
      why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
      the images and related metadata in the table? easier css formatting?
    JavaScript: (Decipher v3)
      you can include JavaScript in the html code but cannot wrap it in html
      comments because Aperture will remove everything within comments.
      Aperture variables such as PageNumber will not be replaced within
      attributes such as <body onload="dialog(PageNumber);">.
      it is very difficult to use document.write anywhere within the html <body>.
      Aperture seems to be using JavaScript to export the html and its code is not
      able to cope with more than one instance of document.write in the html
      templates. after hours of trial and error, I found that the most stable way
      to use JavaScript within the html <body> was to only use one <script>
      element and place everything within it. using document.write within a second
      <script> element would almost certainly lead to unpredictable exported html,
      and instability and crashes in Aperture.
    iMac Duo Core 2GHz 2GB   Mac OS X (10.4.6)  

    It worked. I still have a few tweaks to do on my final template, but the method I described above works. I've set up my templates like this:
    1) one large image per thumbnail page (like a photo essay or photo blog style)
    2) same size image on detail page, but with paypal buttons directly below in their own table (I have several different paypal buttons - for different print sizes and a couple other things like postcards, etc.)
    The neatest thing about this setup is that since it's all controlled by flat html and css, it looks almost like javascript the way the paypal buttons pop up - the image stays in exactly the same place and the buttons just appear below it (haven't tried it on a slow connection, though, probably a slight delay).
    This is great because I hate javascript but sometimes like the immediate visual effects it allows.
    This template makes it trivial to create a reverse chronological gallery/journal - kind of like a photoblog - and allows visitors to view the large images without the extra clutter of the buttons, but then they can just click on the image to reveal the buttons and click the image again to hide them.
    The benefit of putting these buttons directly into the Aperture templates rather than using a find-replace script to add them to iWeb pages after processing? Well, using Aperture, I can add the PageTitle tag to the Paypal button - it doesn't work in hidden form fields or anything that needs to go inside an attribute, but it does parse using a textarea field, which I hid with CSS - This alleviates the problem many photographer sites have where they ask the buyer to email them with the image name/number they want - this way, the shopping cart automatically knows which image they're ordering.
    PageTitle uses the following format: Gallery/Journal Name - Image/Version Name
    So using this tag in the Paypal button tells me which image the buyer wants and which gallery they were viewing when they ordered - simple but effective.
    Anyway, I know it's been a few weeks since I last replied, but I thought I would post this for others who might be interested in doing something similar - entirely through Aperture. Sorry about the run-on sentences; I'm a bit pre-occupied to proofread today.

  • Deciphering web themes: the html templates; expanded reference.

    the html templates.
    RKID attributes:
    Aperture uses proprietary ids within the html documents to identify the parts it needs to play with. These ids are 'rkid' ids. for example,
       <ul id="nav" rkid="navbar">
    These are the rkid values that I've identified so far:
       "navbar"
          a <ul> element containing all of the navigation elements.
       "active" and "inactive"
          rkid attributes to enable the coder to place different formatting on
          current and non-current page numbers in the navbar.
          eg; <li rkid="active"><span class="currentPage">PageNumber</span></li>
             <li rkid="inactive"><a href="IndexPageURL_">_PageNumber</a></li>
       "content"
          a <div> containing all of the album images and their metadata.
       "pictureblock"
          a mandatory <table> in which the images are placed, one image per <td>.
          the <table> must even be used on the Detail page where only one image is
          displayed.
          the metadata will be within the "pictureblock" table if more than one
          image is displayed so that the metadata can be tied to the image. if
          only one image is displayed; i.e., the Detail page; the metadata may be
          in a <td> outside of the table that the image is in but still within the
          "pictureblock" table, usually in the following format:
             <div rkid="content">
                <table>
                   <td>metadata
                   <td><table rkid="pictureblock">
       "image"
          the rkid for the <img> elements containing the album images, frequently
          placed in <dt> elements within the table's cells.
       "titleblock"
          a <div> containing the title text; usually <h3>; for Journals. the <h3>
          element within this element must be given the attribute rkid="text" or
          Aperture will ignore it.
       "textblock"
          a <div> containing the description text for Journals. as with the
          titleblock, the <p> element/s within this div must be given the
          attribute rkid="text".
       "text"
          the rkid given to the text data within the titleblock and textblock
          elements.
    Place holders:
       PageTitle
          used in the <head> of the html. it's made up of the Album/Journal's name plus a page number. eg; "My lucky album - Page 1".
       IndexPageURL
          the gallery page/s URLs; may be more than one.
       ThumbImageURL
          the href links for the images, whether thumbnails or detail full size.
       DetailPageURL
       used within navbar:
          PageCount
          PageNumber
          PreviousPageNumber
          PreviousPageURL
          NextPageNumber
          NextPageURL
          PageCount the total number of pages
          PageNumber includes all of the page numbers listed in the navbar, one
             occurrence for each page.
          _Previous and _Next are more specific and are currently used to draw the
             prev/next arrows in the navbar.
       ImageName
       ImageNameSpace
       PlateNameSpace
       PlateNumberSpaceSlash
          *only seen* when 'Enable Plate Metadata' option in the tag popup menu is
             chosen.
          used to represent an index of the image in the album. the first image
             shown gets the index 1, the second 2 and so on.
          for the Image placeholders, the word 'Image' is used.
          for the Plate placeholders, the word 'Plate' is used.
          space indicates an extra space after the index, probably for html
             formatting purposes because it's only used within <dt> elements.
          slash indicates an extra / character after the index.
          examples:
             ImageName > 'Image 1'.
             ImageNameSpace > 'Image 1 '.
             PlateNameSpace > 'Plate 1 '.
             PlateNumberSpaceSlash > '1 / '.
       metaname
       metavalue
          the placeholders for all of the metadata names/values in the selected
          metadata set.
       PageWidth
          not sure if Aperture calculates it based on the width and number of
          images being displayed in both gallery and detail pages.
          don't know why it's only used in the Special Occasion theme.
       CellWidth
          the width of the table cells containing the album images. not
          necessarily the width of the images. may include margins as specified in
          the albuminfo.plist files.
       ImageWidth
          the width of the image.
       TableWidth
          the width of the pictureblock table. it can probably be applied to other
          elements too but it's length is almost certainly calculated from the
          pictureblock table.
    Operative attributes:
       removeonfirstpage="yes"
          used in the navbar to remove the Prev link from the first page.
          because it's applied to the <a> element, the <a> element is removed
             while leaving an empty <li> in place.
       removeonlastpage="yes"
          used in the navbar to remove the Next link from the last page.
          because it's applied to the <a> element, the <a> element is removed
             while leaving an empty <li> in place.
       removeonsinglepage="yes"
          used in the navbar to remove elements when there's only one page.
          used in a <div> in the Art Collection to remove the whole navbar on
          single pages.
       contenteditable="yes"
          used in text elements to indicate that the user can customise the text.
          not necessary in titleblock and textblock rkid="text" elements.
       common="yes"
          the element is seen on all pages.
    Other attributes:
       metaseparator="|"
          used in metadata formatting, within the metadata lists.
       metalayout="paragraph"
          used in metadata formatting, within the metadata lists.
       singlenesting="yes"
          used in metadata formatting. not sure what it does yet.
       textid="x"
          used to id text elements outside of the titleblock and textblock
          elements.
          possibly no limit to the number and id names used.
          examples used:
             textid="copyright"
             textid="header1"
       picturename="x"
       pictureimage="true"
          picturename gives the image an id.
          pictureimage="true" tells Aperture that the image is a static image
          which can be designated by the user during setup of the album. they show
          up in Aperture as grey blank rectangles with cross-eyes in the middle.
          they do not need to be inside the "content" element
          with picturename and pictureimage, we can place as many static images on
          the page as we wish.
    Assertions:
       Aperture uses the rkid values to identify the areas of the html to be
       repeated for the respective objects.
       standard id and class attributes are only used by the css for formatting and
       not by Aperture to write the html data.
    Notes:
       Aperture is hardcoded to expect and require that the album images are always
       within a <table rkid="pictureblock"> element. it is not possible to place
       album images outside of the table. all album images must be placed within
       <td> cells within the table. the <td> code is repeated for each image.
       image metadata is also normally within the rkid="content" element although
       it can be outside of the rkid="pictureblock" element.
       by default, the textblock rkid="text" element is added when the T+ button is
       pressed within Aperture. the textblock element is switched with the
       titleblock element when the Title/Text toggle button is clicked.
       width and height attributes of <img> elements are rewritten by Aperture
       based on the inserted images. placeholders aren't necessary within <img>
       elements.
       comments are stripped from the html before export some but some
       Aperture-proprietary attributes are forgotten and left behind.
       some pages use the html 4.0 loose doctype. others use the xhtml 1.0 strict
       doctype.
       all markup is converted and exported in UPPER-CASE. personally, I prefer
       lower-case.
       high-ascii characters entered by the user are not converted to their html
       entities when available. eg, the © character.
       multiple <p> elements can be inserted into the titleblock and textblock
       <div> elements but each of them must have the rkid="text" attribute. any
       element without this attribute will be ommitted by Aperture.
       the reason there are Smart Galleries but no Smart Journals is because you
       need to write text between each row of images.
       titleblock and textblock elements will not be applied to Galleries or Detail
       templates; only to Journals.
       if there are more than one titleblock or more than one textblock, only the
       first will be used by Aperture.
    Questions:
       are there variable scopes with each rkid? eg, within the "content" rkid, can
       every variable/placeholder be accessed?
       why did the Aperture team use Definition List <dl>, <dt>, <dd> elements for
       the images and related metadata in the table? easier css formatting?
    iMac Duo Core 2GHz 2GB   Mac OS X (10.4.6)  

    IMPORTANT!
    An updated version is available in thread:
    Deciphering Aperture Web Themes: the html templates v3.

  • How to load only the jsp page even after applying template

    Hi,
    I have a webpage template with header,footer, Dynamic Menu etc. Now I assigned this .jtpl template to all my existing fases jsp files.
    The problem is when I submit a form in jsp, the entire page including template gets loaded again by which we can notice significant time for loading menus and other things.
    Is there any way to avoid this entire template loading and make only the jsp page to load? Please help
    May be this can be achieved by frames. But I dont have idea on how I can merge template with frames. If someone can provide that even would help me better.
    Thanks in advance.

    Hi
    I found the solution .
    <html>
    <head>
    <script language="JavaScript">
    function checkRefresh()
    if( document.refreshForm.visited.value == "" )
    alert('first ime');
      // This is a fresh page load
      document.refreshForm.visited.value = "1";
      // You may want to add code here special for
      // fresh page loads
    else
    </script>
    </head>
    <body onLoad="JavaScript:checkRefresh();">
    <form name="refreshForm">
    <input type="hidden" name="visited" value="" />
    </form>
    </body>
    </html>

  • Highlight "current" page in CSS Dreamweaver TEMPLATE

    I have created 2 navigation bars (in my header) using an unordered list styled with CSS in a Dreamweaver Template that I created. Here is that template (in the template- the "Beads" link is styled as the current page): http://www.bfranklincrafts.com/Templates/MainTemplateM.dwt 
    I don't want the navbars to be editable in the pages that will be created from this template, so I was NOT planning on putting the navbars in editable regions. But now I'm realizing that if I don't put the navbars in editable regions, I won't be able to go in each link in my navbars to put the "current" style for each page.
    The idea of the template is wonderful because it allows us to create one template and from that template we can make changes that would be past down to all the pages that were created using this template. But if I have to put the navbars in editable regions, it means that if I have to make changes to the navbars, I'll have to go to each individual page to make those changes.
    I really want to show the "current" page that visitors are on, can anyone help!!!
    Liolee

    Hi,
    sorry to bring up an old post but I am having issues with this myself and hope you can help?
    I have coded my site as per your example but still no luck.
    It is an .asp site. and my menu looks like this:
    <ul id="nav">
        <li><a id="home" href="http://www.ampso.co.uk/index.asp"><img src="/images/nav1_gray.jpg" width="84" data-srcover="/images/nav1_full.jpg"></a></li>
        <li><a id="tech" href="http://www.ampso.co.uk/page/88/Technical.asp#.USOIoqWduS0"><img src="/images/nav4_gray.jpg" width="102" data-srcover="/images/nav4_full.jpg" class="wrap_right"></a></li>
        <li><a id="construction" href="http://www.ampso.co.uk/page/89/Construction.asp#.USOQLqWduS0"><img src="/images/nav5_gray.jpg" width="170" data-srcover="/images/nav5_full.jpg" class="wrap_right"></a></li>
        <li><a id="medical" href="http://www.ampso.co.uk/page/87/Medical.asp#.USOUeaWduS0"><img src="/images/nav3_gray.jpg" width="88" data-srcover="/images/nav3_full.jpg" class="wrap_right"></a></li>
        <li><a id="media" href="http://www.ampso.co.uk/page/90/Media.asp#.USOWQKWduS0"><img src="/images/nav6_gray.jpg" width="88" data-srcover="/images/nav6_full.jpg" class="wrap_right"></a></li>
        <li><a id="logistics" href="http://www.ampso.co.uk/page/91/Logistics.asp#.USOXdqWduS0"><img src="/images/nav7_gray.jpg" width="100" data-srcover="/images/nav7_full.jpg" class="wrap_right"></a></li>
        <li><a id="allsectors" href="http://www.paycoservices.co.uk/page/86/All-Sectors.htm"><img src="/images/nav2_gray.jpg" width="120" data-srcover="/images/nav2_full.jpg" class="wrap_right"></li>
        <li><a id="contact" href="http://www.ampso.co.uk/page/205/Welcome-to-Payco.asp#.USObtaWduS0"><img src="/images/nav9_gray.jpg" width="120" data-srcover="/images/nav9_full.jpg" class="wrap_right"></a></li>
    </ul>
    Now the issue arises with adding the code to the pages themselves. For example, if I go to the 'tech' page. I have no editable regions like I would with a html template (even though my main menu is in a top menu template which applies to each page) so I'm not sure exactly where to put the css code.
    Currently the top section of my 'tech' page looks like this:
    <%
    Bodystyle = "style='background:url(/images/bg-further-technical.jpg) center 0px no-repeat;'"
    %>
    <!-- #INCLUDE virtual= "/top.asp" -->
    <div id="further-banner" style="background:url(/images/technical-icon.png) 811px 9px no-repeat; ">
    <h1>Payco Technical  <span>It's your industry so why not do it your way?</span></h1>
    <p><b>You are here:</b>
    <a href="/index.asp">Home</a> /
    <a href='Payco-Technical.asp'>Payco Technical</a> /
    </p>
    </div>
    Now do I paste the css code into here? Or would it help if you saw my whole 'tech' page so you can see the rest?
    Any help would be greatly appreciated.
    Thanks

  • Very simple html template engine...

    Hi forum
    I need to create a very simple html templating engine. My requirements are only load a html document into an object (HTMLDocument for example?), search a couple of particular tag or string, treat the text found between these tags like a block, repeating the content all the necessary times, and replacing a special string within the text for another one.
    Here an example:
    <html>
    <title>Foo page</title>
    <body>
    <table>
    <!-- Initial special tag -->
            <tr>
                <td>{String to replace}</td>
            </tr>
    <!-- Final special tag -->
    </table>
    </body>
    </html>If i pass the html example code for the template engine with the following parameters, the result that i want is:
    Number of times to repeat the BLOCK: 3
    Text to replace de special string: Hello world
    <html>
    <title>Foo page</title>
    <body>
    <table>
            <tr>
                <td>Hello world</td>
            </tr>
            <tr>
                <td>Hello world</td>
            </tr>
            <tr>
                <td>Hello world</td>
            </tr>
    </table>
    </body>
    </html>That�s all. I search in google for something but a encountered only javascript based "applications", except the "Rhino" engine, but that is to much for mi needs.
    Well, i hope anyone can help me.... and sorry for may bad english :P...

    Here's the generated code:
    `include(~service="system", ~language="", ~theme="dm", ~name="TemplateLibraryDHTML.html")`
          `SAP_DynproLayerBegin(003,001,028,001)`
          `SAP_Label("%#AUTOTEXT001")`
          `SAP_DynproLayerEnd()`
          `SAP_DynproLayerBegin(003,003,020,001)`
          `SAP_Label("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_OLD")`
          `SAP_DynproLayerEnd()`
          `SAP_DynproLayerBegin(030,003,005,001)`
          `SAP_InputField("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_OLD")`
          `SAP_DynproLayerEnd()`
          `SAP_DynproLabelLine(003,003,030)`
          `SAP_DynproLayerBegin(003,004,020,001)`
          `SAP_Label("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_NEW")`
          `SAP_DynproLayerEnd()`
          `SAP_DynproLayerBegin(030,004,005,001)`
          `SAP_InputField("YSRMS_CTR_MASS_NEG_AMEND-YYNEG_AMEND_NEW")`
          `SAP_DynproLayerEnd()`
          `SAP_DynproLabelLine(003,004,030)`
          `SAP_DynproLayerBegin(004,006,014,001)`
          `SAP_Button("CTR_NEG_AMEND_REJ")`
          `SAP_DynproLayerEnd()`

Maybe you are looking for