External Files

As discussed in the Quick Start Guide Section, depending on the Render Token used, external files can contain TEXT, HTML, Compiled Miva Script, PHP, ASP, Perl, JAVA, CFM, etc.

• TEXT & HTML - The HTML file inserted must contain only the body of HTML document or you will get duplicate HEAD and BODY tags, unless you are rendering an external file in a Merchant Page that does not contain its own HEAD and BODY tags. If you are rendering an external TEXT file and would like to retain the TEXT file alignment, wrap the item above in a set of <PRE></PRE> tags.
  
• Compiled Miva Script - This is a Script, written in MIVA language and compiled using the Compiler available Free from MIVA. If you are using the "run" Render Token, the file does not need any special functions and all Global Merchant variables and arrays will be available. If you are using the "function" Render Token, the file must contain a "ADS_External_File" function. Example of an empty function is below. Module distribution also contains an uncompiled file containing this function with an example breadcrumb navigation script. Merchant Global, All_Settings, Settings, Module, Item and additional Parameter variables and arrays will be available to this function
  • <MvFUNCTION NAME = "ADS_External_File" PARAMETERS = "module var, item, all_settings var, settings var, fparam" STANDARDOUTPUTLEVEL = "text, html, compresswhitespace">
    
    </MvFUNCTION>
    
• PHP, ASP, Perl, JAVA, CFM, etc.. - These executable files must generate HTML or TEXT as their output. If generated file is HTML, it should only contain the body of HTML document or you will get duplicate HEAD and BODY tags, unless you are rendering an external file in a Merchant Page that does not contain its own HEAD and BODY tags. If generated file is TEXT and you would like to retain the TEXT file alignment, wrap the item calling external file in a set of <PRE></PRE> tags.