Apply HTML template to message

Hi folks,
I have a situation where I need to apply an HTML tempate to message which I then e-mail.
I have no problem with the mail adapter ...but the template is another question.
Any ideas ????
Cheers,
Guy

Guy,
THe best way to organise your mail that is sent via XI mail adapter is <b>using XSLT mapping</b>. There is a couple of blogs available in SDN by Prakash Arunachalam on this topic, but even that throws no light in the approach of applying a HTML template
Regards,
Jai Shankar

Similar Messages

Applying HTML Content Templates to Builtin Item Types

Using 10.1.4,
Is there any way of applying HTML Content Templates to the Builtin Item Types, e.g. Page Path, it doesn't appear to work if you set the attribute to use the template on the region settings?

The Builtin Item Types are indeed not affected by the HTML Content Layout. This is an undocumented feature in the product. A documentation bug has been logged to get it amended in the Portal documentation :
Bug 5581113 : DOCUMENT RESTRICTION FOR HTML CONTENT LAYOUTS AND BUILT-IN NAVIGATION ITEMS

Applying Updated Templates

When I am applying an update templates file.dwt to the
current page (Modify - Templates - Update Current Page), an error
message pops up
Macromedia Dreamweaver MX 2004
There is an error at line 16, column 87 (absolute position
664) of "N:\20-Marketing-Comms\Marketing\WEBSITE\BHRC
website\html\Templates\BHRCcontent.dwt": Nested editable regions
Does anyone know what this means and how do I get around it?
Thanks.

> Does anyone know what this means and how do I get around
it?
Yes - it means you have a problem with the current page. Can
you show me
the page (please post a link to it, if you can)....
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
==================
"Advice Please" <[email protected]> wrote in
message
news:enmetj$sa7$[email protected]..
> When I am applying an update templates file.dwt to the
current page
> (Modify -
> Templates - Update Current Page), an error message pops
up
>
> Macromedia Dreamweaver MX 2004
> ---------------------------
> There is an error at line 16, column 87 (absolute
position 664) of
> "N:\20-Marketing-Comms\Marketing\WEBSITE\BHRC
> website\html\Templates\BHRCcontent.dwt": Nested editable
regions
> ---------------------------
>
> Does anyone know what this means and how do I get around
it?
>
> Thanks.
>
>

[svn] 3120: When you point Flex Builder at a local sandbox trunk build, it couldn' t generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build

Revision: 3120
Author: [email protected]
Date: 2008-09-05 10:44:10 -0700 (Fri, 05 Sep 2008)
Log Message:
When you point Flex Builder at a local sandbox trunk build, it couldn't generate the html-templates folder correctly for new projects so we moved all the html templates up one level and removed the html-templates directory and adjusted build.xml's to accommodate the directory change
Modified Paths:
flex/sdk/trunk/build.xml
flex/sdk/trunk/webapps/webtier/build.xml
Added Paths:
flex/sdk/trunk/templates/client-side-detection/
flex/sdk/trunk/templates/client-side-detection/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection/index.template.html
flex/sdk/trunk/templates/client-side-detection-with-history/
flex/sdk/trunk/templates/client-side-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.css
flex/sdk/trunk/templates/client-side-detection-with-history/history/history.js
flex/sdk/trunk/templates/client-side-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/client-side-detection-with-history/index.template.html
flex/sdk/trunk/templates/express-installation/
flex/sdk/trunk/templates/express-installation/AC_OETags.js
flex/sdk/trunk/templates/express-installation/index.template.html
flex/sdk/trunk/templates/express-installation/playerProductInstall.swf
flex/sdk/trunk/templates/express-installation-with-history/
flex/sdk/trunk/templates/express-installation-with-history/AC_OETags.js
flex/sdk/trunk/templates/express-installation-with-history/history/
flex/sdk/trunk/templates/express-installation-with-history/history/history.css
flex/sdk/trunk/templates/express-installation-with-history/history/history.js
flex/sdk/trunk/templates/express-installation-with-history/history/historyFrame.html
flex/sdk/trunk/templates/express-installation-with-history/index.template.html
flex/sdk/trunk/templates/express-installation-with-history/playerProductInstall.swf
flex/sdk/trunk/templates/metadata/
flex/sdk/trunk/templates/metadata/AC_OETags.js
flex/sdk/trunk/templates/metadata/readme.txt
flex/sdk/trunk/templates/no-player-detection/
flex/sdk/trunk/templates/no-player-detection/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection/index.template.html
flex/sdk/trunk/templates/no-player-detection-with-history/
flex/sdk/trunk/templates/no-player-detection-with-history/AC_OETags.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.css
flex/sdk/trunk/templates/no-player-detection-with-history/history/history.js
flex/sdk/trunk/templates/no-player-detection-with-history/history/historyFrame.html
flex/sdk/trunk/templates/no-player-detection-with-history/index.template.html
Removed Paths:
flex/sdk/trunk/templates/html-templates/

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

I applied a template to a page with SWFs and now that page does not play the SWFs. Why?

I applied a template to a page with SWFs and now that page does not play the SWFs (just a blank area where the SWF should be). When I detach the template it will play the flash file. This site will eventually be updated via Adobe Contribute. And I just discovered that when applying a template to a page that uses HTML datasets (Master/Detail),it no longer reads the Master/detail regions and displays a blank. Any thoughts?
[Moved to Dreamweaver forum by moderator]

Firstly, you shouldn't really 'apply' a template to a page, you should create a child page by going to FILE>NEW>Page from Template. Too many things can happen when applying a template the way you are doing it. eg:; editable and non-editable regions not matching up and being asked where to place these regions and in all likelihood, you end up with 2 or more of the same region.
When a swf file is inserted into a page, a corresponding Scripts folder is written automatically is stored in the root of the site - it is also linked to in the head of the document. What I believe is happening is that when you apply a template to the page, the Template has no idea that there is a swf file on the page and is not aware of the correct link to the Scripts folder. If you do a test and add the swf file to the template page itself, I bet that the links to the swf and the scripts folder are correct - because DW knows the correct path to the script file. Hence the reason the page probably works when you detach it from a template.

Apply a template to a page with A LOT of Javascript

I am trying to apply a template to this
page
for use in another website. When I do this, the javascript no
longer works. How do I work around this?
Thanks,
Melissa

* Spawn a child from the template.
* Copy content from this page and paste it into the new child
page you just
spawned until you have completed the content.
* Copy everything in the head of this page from the first
<csactions> tag
down through the </csactiondict> tag, and paste it into
the EDITABLE region
called "head" in the head of the page you just spawned.
You should be fine now.
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
==================
"Melliska" <[email protected]> wrote in
message
news:gabs1n$de4$[email protected]..
>I am trying to apply a template to this
http://mysticalartprints.com/
> for use in another website. When I do this, the
javascript no longer
> works. How do I work around this?
>
> Thanks,
> Melissa
>
>
>

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.

HTML Template for Web Dynpro (ABAP)

Hi Guys,
I am developing a webpage in webdynpro abap.
my requirement is to use a existing HTML(same as existing applications) template for this.
how do i do that ?
regards
Siddharth

You don't. That isn't how Web Dynpro works. The architecture is such that it abstracts the HTML/JavaScript rendering of the output. You place a UI element on the screen and only a metadata reprsentation of the screen is created at design time. At runtime different rendering engines can be applied to produce the final output. This allows SAP to add new rendering engines and to improve the rendering engines over time without having to adjust the applicaitons itself. This makes Web Dynpro sutiable for producing Business Transactions, but not general web pages. It also gives us the flexibility to render Web Dynpro in HTML/JavaScript, a desktop client (.Net 3.0 and WPF), and a RIA client (Adobe Flex).
You can alter the theme of the WDA application when running in HTML rendering. The theme gets automatically inherited from the NetWeaver Portal - or you can apply a stanalone theme when running without the portal. Theming allows for some basic changes of color scheme and branding elements - but is not the same as applying a complete HTML template.

How to apply a template to a page uploaded using sftp?

I would like to upload the .html document with the appropriate template using sftp instead of applying the template using BC's back end.

Hi,
You cannot apply/assign a template to a page via sftp. You'll need to action this via back-end or using DW. Since you prefer not doing this in the back-end DW extension would be the alternative.
- http://tv.adobe.com/watch/introducing-business-catalyst/getting-started-with-business-cata lyst-and-dreamweaver-cs6-creating-and-publishing-sites/
Kind regards,
-Sidney

Changing HTML templates for Standard SRM screens!!!!!

Hello SRM gurus,
I have to modify the standard SRM PO screen. I have modified the screen and added the requirement tracking number field but on activation it gives me message to adapt the HTML template manually.
How to change HTML template assigned to the screen? Also what more needs to be done for the field to appear on the SRM portal?
I am not aware even of the transaction code to be used.
Your help will highly be appreciated and rewarded.
Regards,
Shrikant Gavali.

Hi,
You need not chnage the Standard SRM screen nor the HTML template to add a custom field in the PO sceen.
Please check these notes:
672960 - user-defined fields.pdf
676016 - user-defined fields.pdf
There is an additional note for req tracking no not available in SC but in your case you want the field in PO so wont be relevant.
Note 676016 - SRM: Requirement Tracking Number not available
Also refre this weblog for adding custom fields in the std SRM screens:
/people/nanda.kondagunta/blog/2006/10/23/how-to-create-custom-fields-in-srm
The tcode for PO is BBP_POC.If you ever need to modify the HTML template for this screen/trascn,goto SE80.select Internet service as BBP_POC.There you can see all the HTNL templates and each of which corresponds to some screen in the trascn BBP_POC(PO trascn).
BR,
Disha.
Do reward points for useful answers.

[CS3] Publish problem with no valid HTML templates

Hi,
I have a project file which I have publish numerous times
before without problems. It has come to finally publishing it for
the last time and when I go to publish an error messages comes up
saying...
"no valid HTML templates are avaliable to complete this
operation".
I have reinstalled the app again but still getting the
problem.
Any ideas...

I get to the point where you select Publish Settings in the
file menu but then it comes up with the error message...

Converting a html template to php

How do I convert my html template to a php template? Any help
would be appreciated.
Thanks

You do not need to do anything.
"foo.dwt" can be used to create HTML, or PHP child pages.
If you really want to do it, though, you can rename foo.dwt
to foo.dwt.php
(using DW's Files panel) and let DW adjust the pages
accordingly.
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
==================
"littlemax" <[email protected]> wrote in
message
news:f1sodn$6kb$[email protected]..
> How do I convert my html template to a php template? Any
help would be
> appreciated.
>
> Thanks

Html template change and refresh on ITS Admin

hi all,
I need to change the HTML templates sent via email to the users. I found the files on the ITS server and changed them but when I view the same templates in ITS Admin then it is still showing the previous version.
The mentioned HTML templates are only present in the ITS server not as an internet service in SE80 so I cannot change and publish them from SAP.
Please advise that how can they be changed and refreshed so the changes to the layout appear.
Thanks,
FS

Hello FS,
ITSAdmin and local files - so you are using an external ITS 6.20?
If you did not start up the ITS in debug mode with ~adminenabled you will need to restart the ITS to apply the changes (that will be preparsed and cached in the ITS for performance reasons).
With best regards,
TJ

HTML Template for Items

I'm working on creating an HTML template for use with and Item type portlet on Portal 10.1.4. I have the items themselves rendering as I want with the layout I want but I'm having an issue with the item categories. Since the template renders itself for each item, how do I add the category to the layout so that it renders similar to the portal default, which is grouped by category. The category is displayed once and the items assigned to that category are listed below it. If I add the category substitution tag to the template the category name is rendered along with each item. If there are 14 items in one category then the same category displays 14 times.
Does anyone have any ideas on how to accomplish this? Thanks in advance.

You don't. That isn't how Web Dynpro works. The architecture is such that it abstracts the HTML/JavaScript rendering of the output. You place a UI element on the screen and only a metadata reprsentation of the screen is created at design time. At runtime different rendering engines can be applied to produce the final output. This allows SAP to add new rendering engines and to improve the rendering engines over time without having to adjust the applicaitons itself. This makes Web Dynpro sutiable for producing Business Transactions, but not general web pages. It also gives us the flexibility to render Web Dynpro in HTML/JavaScript, a desktop client (.Net 3.0 and WPF), and a RIA client (Adobe Flex).
You can alter the theme of the WDA application when running in HTML rendering. The theme gets automatically inherited from the NetWeaver Portal - or you can apply a stanalone theme when running without the portal. Theming allows for some basic changes of color scheme and branding elements - but is not the same as applying a complete HTML template.

Apply HTML template to message

Similar Messages

Maybe you are looking for