Skip Navigation | Groups

This site uses cookies- for more information see the Cookie Policy | Continue

 

Restrictions when using Interactive Buttons

Interactive Buttons - Restrictions


Restrictions:

A page using shared borders can be divided into five areas. At least one of these areas (Main Content) will be present in the page, but not necessarily all five.

  1. Main Content
  2. Top border
  3. Left border
  4. Right border
  5. Bottom border

A page using Include Pages can also be divided into areas:

  1. Main Content
  2. Include Page 1
  3. Include Page 2
  4. etc.
  1. If Interactive Buttons are used in any of these areas, they can only be used in one area.  When FP builds an Interactive Button on a page the image is given an ID, which must be unique on that page.  The IDs given start from img1, img2 and so on.
    When Shared borders or Includes are added to a page, the IDs on the included files are not changed, hence it is possible that the same IDs could be given to buttons in different areas on the page.  See Button Test to see how this works (or, rather, fails).
    There is a workaround for this restriction, involving editing the HTML code.

Some of the restrictions below do not apply to Expression Web 3 and 4. Expression Web 3 and 4 can and do modify the paths in javascript used to call the behaviours in Interactive Buttons - but the programs do not modify any other links in Javascript functions that may be in the page. However, Expression Web 3 and 4 add their own foibles ...

  1. For Shared Borders, the Interactive Button Images must not be located in the _borders folder, nor in any folder where pages using the Shared Border are located.
    A relative path to the button images from the Shared Borders pages must be established that will be the same as the relative path to the images from the pages containing the shared borders.  Placing the buttons in the images folder usually takes care of this. (There is a workaround, but it should be regarded as crazy!  Also, if the use of Code View is acceptable, the problem may be sanely resolved for a server based web, where the web is the root web, but will not work on disc based webs, and perhaps not where the web is a subweb.)

    Note that if the web is designed using a disc based web, this restriction does not apply - unless the website is HTTP published to a server running the FrontPage extensions. In a disc-based website, the links to the buttons are correctly maintained. However, when publishing to a server running FP extensions the pages are rebuilt on the server, and the links break.
  2. If using Include Pages containing Interactive Buttons, these must be placed in their own folder, one level down from the root.  The button images must not be saved into this folder, nor must any pages using the includes. 
    **Alternatively, the Include Pages and the pages using them may be saved into the same folder (including the root folder) - the buttons, in this case, can be saved anywhere, with no restrictions. (see workaround).  As for Shared Borders, if working in Code View is acceptable, the problem can be completely resolved.
    Again, a relative path to the button images from the main pages must be established that is the same as the path from the include pages to those images.

    Note that if the web is designed using a disc based web, this restriction does not apply - unless the website is HTTP published to a server running the FrontPage extensions. In a disc-based website, the links to the buttons are correctly maintained. However, when publishing to a server running FP extensions the pages are rebuilt on the server, and the links break.
  3. Pages using the Shared Borders or Include Pages must be located in folders one level below the root folder, but not the _borders folder, nor the folder containing the include pages [except as ** above].
    Since FP cannot manage links within JavaScript, the same relative path to the button images must exist for all pages using the border/include.  In particular, the Shared Border (or Include Page [except as ** above]) cannot be applied to the web-site's Home page, nor to any pages in the root of the web.
    (See workaround)