HTML Templates in integrated ITS

Hi,
I am using certain ITS services in integrated ITS. However, their look and feel is like WebGUI. For two of the services, there are HTML templates defined but still their look and feel is like WebGUI. If I do not definr ~GENERATEDYNPRO = 1, then I get an internal error. If I use this parameter, then the look and feel is SAP like.
Any pointers?
Thank you.
Abhijeet.

Hi abhijeet,
Set by Service file
~ generateDynpro = 0 -Automatic screen generation
                      disabled.
                   1 -Automatic screen generation
                      enabled.
can you re-publish service again on your ITS and re-start ITS server and test this.
Please share the result.
Thnx,
Suriya.

Similar Messages

Running standard HTML page on integrated ITS?

Is it possible to use the integrated its like MS IIS to run a standard .html page on it?

Hi,
of course, just use the MIME repository for your static HTML
pages or objects like Javascript files, images...
regards
Tobias

ALV GRID and Integrated ITS 7 (SAP GUI for HTML) - dissapears on reload

Hi All,
We have a custom report that uses an ALV grid to display information to the user. Within this grid, there are fields that are display only and fields that are editable. Also, the grid is wider than the screen's width. It works fine in ECC. It also worked fine when we were using ITS 6.4.
We have recently upgraded to ITS 7. Now when we run the report using a Transaction iView (in EP 7) or the Webgui service (SAP GUI for HTML), if a field that is editable has focus when an event is triggered that reloads the grid, the screen becomes blank. So, you can click the Save button and the screen goes blank, also, there are date fields in the grid and if you choose a new date, the grid reloads and the screen becomes blank.
We have found that when the screen is blank, you can use the "Page Up" button on your keyboard and the last few columns of the grid will appear. As if the entire grid has moved off-screen to the left.
If you click onto a non-editable field and refresh or save, the grid returns to its normal state.
We are on Basis Patch level 15.
Does anyone have any ideas on how to fix this?
Also, does anyone know of a standard SAP transaction we can call from the Webgui that would have a similar setup...with an ALV grid containing editable and non-editable fields? We would like to rule out any errors in the report itself. Since it worked before we upgraded and it works fine in ECC. This would be a really big help too.
Thank you so much!
-Kevin

Hi,
Thanks Raymond, I have seen Note 314568. I could not get the second link to work but I have looked at just about every Note in reference to Integrated ITS 7 and Tables or ALV Grids and there are very many, so it would appear that SAP has had a hard time with implementing this control, but I have not seen any instance that matches the problem we are having.
Unfortunately, SAP will not investigate this unless we can provide a standard Transaction that exhibits the same behavior.
If anyone knows of a standard SAP Transaction that displays an ALV Grid that is wider than the screen (requiring a horizontal scroll bar) and with editable and non-editable fields, that would be fantastic. If we can test against that, then we would know for sure if this is a problem with ITS / SAP GUI for HTML, or if there is an issue with this specific report.
Thanks!
-Kevin

Integrated ITS issues in HTML Viewer Control related to applets

We are currently running on integrated ITS - WAS 7.0 kernel 90 at level SAPKB70010. We recently upgraded from a 46C environment that was utilizing external ITS. We also utilize the standard SAP CIC0 transaction (call center interaction center) that is essentially running the webgui service inside of html viewer controls inside of the SAPGUI.
Once we upgraded to the integrated ITS we have lost some functionality. It appears functions like exporting to spreadsheets from ALV grid, for example, no longer work in the CIC0.
Through some investigation, I can see that if I run the webgui service in an IE browser, the ALV grid export functionality will work, and makes use of applets.
If I run the same webgui service in an HTML viewer control (for example, by running thru program RSDEMO_HTML_VIEWER), I can see that the download will not work.
I'm aware the HTML viewer control has limitations, however this functionality worked fine for us when using the External ITS, and is important functionality for our CIC0 transaction. We are using the same version of SAPGUI (640) now we were using before.
Is anyone aware what has changed with Integrated ITS that would make this functionality no longer work in HTML viewer control? or possibly settings that might need adjusted?
Thanks,
Pam Crissman
Pam Crissman

Hi Pam,
I found something on SAP Notes:
Check this:
Note 858959 - ALV export: saving in SAP GUI for HTML as local file
Regards,
Siddhesh

In ITS-Service ITSMOBILE no HTML-Template ALV_GRID.html

Hi all,
i use its-mobile with alv grid. In my Template i changed text:
Unknown type CUST_CTRL for element CONTAINER1
with:
`include(~service="itsmobile", ~theme="99", ~name="alv_grid.html");
alv_grid("ALV", 52, 8);`
But now i get the error: ITS_CANT_LOAD_INCLUDE - that file alv_grid.html is not found. That is right! When i look into ITSMOBILE -> Thema 99 -> HTML-Templates no file called alv_grid.html is there. So how do i get this file?
System is SAP ECC 6.0, Release 700 Support Package SAPKA70016.
Best Regards,
Max

Hi Max,
What is the BASIS Support pack that you are on?
I presume its the same level as your Application Support Pack SAPKA70016? i.e SAPKB70016
For ITSMobile - I thing you would need to be on SAPKB70018?
See notes:
[BC-FES-ITS #1320125 ITSmobile: fixed ALV Grid row selection|http://service.sap.com/sap/support/notes/1320125]
[BC-DWB-TOO-WAB #1142337 Generating program creates slow HTML mobile templates|http://service.sap.com/sap/support/notes/1142337]
Regards,
Oisin

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

SRM ITS - Modify HTML templates

Hello,
I am currently trying to understand the flow of the ITS and the SAP about how the screens are converted into HTML templates to be displayed on the web browsers. I would like to know if it is possible to modify the HTML templates and add some of our own JavaScript Validation or even add our own text field or other objects without touching the ABAP code?
Thanks,
Pramod

Hi Pramod,
You can always change the templates, If you know the standard Program ( You can get the standard program from SE80, input the template name and it gives the details of the programs related to that template) once you know the program you can do the changes in SE51( Screen painter), Input the Program name and the screen number for which this change is required.
Once you input click on Display/ change and at the top in the applicaton toolbar there will be a push button called Layout, click on that that takes you to screen painter where you can add new text fields.
For validation purpose in SRM there a badi BBP_DOC_CHECK which is used for validation purpose, but you need to do some coding depend upon your requirement
Regards
Sameer

How do I surface language specific texts in Integrated ITS?

Hello all,
I'm new to both stand alone and integrated ITS and am researching the upgrade process. In our stand alone templates we used htrc files with our html templates to show language specific texts.
Example.
html template code for a field label
`if (i==2) DETAIL-FLABEL[2]= #KAFN end`
htrc name value pair
z_pz01_en.htrc
KAFN Known As First Name
z_pz01_de.htrc
KAFN Bekannt unter dem Vornamen
I see no hint that htrc's can be used in integrated and am not seeing anything in the way of resource based language texts in integrated. I think I've hit every document out there yet, I have a feeling I'm missing something obvious. Your help is appreciated.
Doug

Edgar,
Thanks so much for the detail!
I have run through the steps for manual creation of translations as well as SIAC_UPLOAD of htrc files and have it working and documented. I will add a few more findings here for others who find this post later.
Some of our old htrc files had duplicate keys (probably from original German version). In stand alone ITS the last key in the file was used so this didn't matter. In integrated ITS this matters for 2 reasons.
1 Uploading/Converting htrc files having logged in in English will cause failures if any of the text being entered in the service parameters has characters that arent consistent with the codepage being used for EN. (Ex. back Azureück). Clean up htrc files to use only the language they should contain.
2 Stand alone ITS was forgiving of htrc files containing duplicate keys. Integrated ITS is not. Remove all duplicate keys.
3. This one is obvious but... if parameters have already been entered in another language you may be prompted to confirm you are changing language and there are several prompts along the way. As these prompts will appear in the logon language itu2019s important to eitheru2026
a. Be fluent in all supported languages , oru2026
b. Memorize button and menu positions.
I do have one additional question.
Our old stand alone setup had an alternate corporate "APCI" design that we used...
File system view -
hostDEV_WWWmimesdesigns"apci"webgui as opposed to the out of box
hostDEV_WWWmimesdesignssap_streamlinewebgui I suppose.
I believe this was then referenced in the global services file ~DESIGN="APCI"
I'm starting research to understand if there is an analog to this in the integrated webgui service or precisely what I have to do to accomplish alternate styles for webgui and our Z_services.
Thanks again, points on the way, If I could award more I would.
Doug

MimeURL with images not functions properly on Integrated ITS

Hi all,
I'm new in ITS and I'm working on Integrated ITS (SAP ECC 6.0). I have to substitute some gif images on HTML template of a customer internet service (on SE80).
I have pointing on the folder:
YYWEB
-Topic 99
-IMAGE
A.GIF
and I create new MIME object B.GIF (under IMAGE folder) I save and publish it.
Into HTML template I have found this code (that's work fine):
<TD background="`mimeURL(~name="/image/a.gif")`" height=32 > </TD>
and I changed in:
<TD background="`mimeURL(~name="/image/b.gif")`" height=32 > </TD>
But nothing is appearing on the browser in place of the B.GIF image.
Any clues?
Thanks in advance,
GB

Perhaps try clearing the Browser Cache and the Integrated ITS Template and MIME Cache using transaction: SITSPMON -> "Template & MIME Cache"
If "B.GIF" is still not shown - use a HTTP sniffer like HTTPWatch to see if the template is ref the correct MIME in the View Source of the HTML page.

How to migrate Themes, HTML templates, MIME objects to ECC6.0

Hi Friends
How to migrate Themes, HTML templates, MIME objects which are developed in SAP Web@Studio.
or How to use program SIAC_UPLOAD ??
regards
siddharth

Hello Murray,
Your steps sound correct. I would add that you generally need the following:
1. publish the IAC, SYSTEM, and WEBGUI Internet Services (also from SE80)
2. make sure the Integrated ITS is working. Meaning you should activate the ITS in the profile parameter, this can be seen in transaction SITSPMON. Some services in transaction SICF also need to be activated, like the default_host/sap/public/bc/its
From your error message though it looks like the URL you have used is either incorrect or you have used the External Alias feature in SICF? The URL for the ITS is usually http://host:port/sap/bc/gui/sap/its/service. Second, the error is about a language resource file (.htrc), you have not specified if you created one or not. To create one in the language you are logged in with just go to SE80, open your Internet Service and double click on the "Topic xx". Don't forget to publish after creating and saving it.
Edgar

ABORT_MESSAGE_STATE when calling transaction via integrated ITS

Hello experts,
we use ECC 6.0 (and therefore Netweaver 7).
I try to start a customer transaction via integrated ITS on our consolidation system with the following link.
http:// ...   :8080/sap/bc/gui/sap/its/webgui/!?~transaction=ZCO16&sap-client=200
In our dev system all works fine so far. But in consoloidation I get errors showing in the browser after logon:
Error when processing your request
What has happened?
The URL http:// ...   :8080/sap/bc/gui/sap/its/webgui/! was not called due to an error.
Note
The following error text was processed in the system Q01 : System error
The error occurred on the application server asapt02sv1_Q01_00 and in the work process 1 .
The termination type was: ABORT_MESSAGE_STATE
The ABAP call stack was:
SYSTEM-EXIT of program SAPMZCO002
What can I do?
If the termination type was RABAX_STATE, then you can find more information on the cause of the termination in the system Q01 in transaction ST22.
If the termination type was ABORT_MESSAGE_STATE, then you can find more information on the cause of the termination on the application server asapt02sv1_Q01_00 in transaction SM21.
If the termination type was ERROR_MESSAGE_STATE, then you can search for more information in the trace file for the work process 1 in transaction ST11 on the application server asapt02sv1_Q01_00 . In some situations, you may also need to analyze the trace files of other work processes.
If you do not yet have a user ID, contact your system administrator.
Error code: ICF-IE-http -c: 200 -u: IE121 -l: E -s: Q01 -i: asapt02sv1_Q01_00 -w: 1 -d: 20080111 -t: 165033 -v: ABORT_MESSAGE_STATE -e: System error
HTTP 500 - Internal Server Error
SM21 says:
16:37:04 DIA 001 200 IE121   ZCO1           W0 1 ITS, User session terminated
long message:
ocumentation for system log message W0 1 :
he user session has been terminated after an error in the log
onversion from SAPdiag to HTML. Look in the preceding syslog entries to
ind the cause of the error. For more error details, refer to the trace
iles.
16:37:04 DIA 001 200 IE121   ZCO1           D0 1 Transaction Canceled ITS_P 001 ( )
long message:
The transaction has been terminated. This may be caused by a
termination message from the application (MESSAGE Axxx) or by an
error detected by the SAP System due to which it makes no sense to
proceed with the transaction. The actual reason for the termination
is indicated by the T100 message and the parameters.
The tracefile of the work process says:
========================================
W Fri Jan 11 16:37:04 2008
W      *** ERROR => julep: PpioCreateParseTree: IRepRetrieve(templates/system/header.html) failed. [w3xxppio.cpp 1184]
W      *** ERROR => julep: PpioCreateHtmlPP: PpioCreateParseTree(templates/system/header.html) failed, rc=0x10c [w3xxppio.cpp 985]
W      *** ERROR => julep: XIntInterpret: PpioCreateHtmlPP(templates/system/header.html) failed, rc=0x10c [w3xxjuce.cpp 529]
W      *** ERROR => xgdk: MsgtBuildHtmlBlock: IntpDoInterpret (templates/system/header.html) failed, rc=0x2101 [w3xxmsgt.c   220]
W      *** WARNING => diag: SemgXGHandleResponse: Returning rc=0xffffffcc [w3xxsemg.cpp 1490]
W      *** ERROR => plugin: XKrnHandleResponse failed rc= -52 [itspxkrn.cpp 764]
W      *** ERROR => plugin: ItspXKrn_HandleResponse failed. 700000840333ba0 rc: 0 [itspxkrn.cpp 391]
W    *** ERROR => ipl_ConvertOut failed rc = 1, send icf error page [itsplxx.c    1526]
M    ***LOG W01=> [itsplxx.c    1527]
W    *** ERROR => ipl_ConvertOut returns 1(ITSPE_FAILURE) [itsplxx.c    1529]
W    *** ERROR => Raise Last error:[1 from: itspxx.cpp :817] [itsplxx.c    1216]
W    *** ERROR => RaiseError(sapdext) ITS_P:01 [itspxx.cpp   817]
==========================================
I don't have any dumps.
Please help. Thanks in advance.
Frank

Hello Ruchit,
> Publishing is done via SE80 but may be it may not be needed. But you can try that out as well.
Please advise. How do I this precisely?
> Try this. Deactivate your SICF completely in consolidation system and then reactivate
> it. After that give this a try.
All services have been activated now (after deactivating first) but I have still the same symptom.
> Also when you are trying to execute this customer transaction just compare the urls you
> are getting in development and consolidation. I guess there is an issue with the
> url you are getting.
I get exact the same URL after (except the hostname of course):
http:// ... 8080/sap/bc/gui/sap/its/webgui/!?sap-system-login-basic_auth=X&sap-client=200&sap-language=EN&%7Etransaction=ZCO16
Regards.
Frank

Logging off from HTML template

Hello!
   What command do I need to issue to log off the WAS server from an HTML template? Is it possible to modify the push-button logic below to do that? We are on 6.40, integrated ITS.
<input type=submit name=<what do I put here?> value=" EXIT   ">
Thanks!
John

Hi Raja;
   Thanks for the response! I tried your suggestion, but I get the dreaded error "The following error text was processed in the system W07 : Templateinterpretation abgebrochen, Template nicht vorhanden". Any suggestions?
Thanks!
John

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.

Adding new text in SHC HTML template with different colour

Hi Gurus,
We are using SRM5.0 Server 550 and SP14 and classic scenario.
Is it possible to change the colour of a newly added text in Shopping cart HTML template?
I mean we have a requirement to add a new text in HTML template of shopping cart and with a different colour so that it woulod be highlighted whenever users try to shop something.
Can anyone let me know the pros and cons of such a thing, if later on they upgrade to SRM7.0 and its feasibility?
Regards,
Teja

Hi,
You can enhance/modify the HTML template.
SRM 7.0 does not use ITS HTML template. So SRM 5.0 is the last version using ITS HTML template and no impact for upgrading to SRM 7.0.
Regards,
Masa

Changes to HTML template not reflected in production

Hi All,
I am facing the following issue.
I have changed an already existing screen(HTML template) and published the service. It is working fine in development environment. This is now transported to production environment and the screen change is not reflected here. We have tried refresing the ITS buffer, but hasnt worked. Any pointers would be of great help.
Thanks,
Shruti

Hi Shruti,
did you check the changed template in the productive environment? Did the transport successfully reached the new system?
If the changed template is available please (re)publish the file on the new environment.
Regards,
Sabine

HTML Templates in integrated ITS

Similar Messages

Maybe you are looking for