Scripting Languages
Content from the system can be published as files with any desired file extension. For example, from a single content repository multiple sites can be managed, each with a different scripting language like ASP, ASPX, PHP, CFM, SSI, and JSP. The system supports managing content that is published to multiple servers in a non-heterogeneous environment.
The first step for publishing content with a specific file extension is to modify the publish configuration.
A. Change Configuration Output File Extension
To change the configuration output file extension:
- Go to the Administration area, and select Configuration Sets from the left navigation bar.
- Select the desired configuration set from the left navigation bar. In our case, we will choose Web Standard.
- Click the Edit tab.
- Select the Configurations pane. You will automatically be placed on the default HTML configuration.
- In the Output File Extension field, type .asp (or a different extension, depending on your needs).
- Click the Submit button to save the updated configuration set.
With a configuration set to publish files in a designated extension, the next step is to incorporate the appropriate source code include line. Code to include other scripting code can be entered directly in the template or in blocks or formats that are placed in template regions. Includes can even be dynamically written out with XSLT based on input from the user in a data definition or system asset. The benefit is that content from the system can be combined with custom programming to create new opportunities.
B. Incorporate Scripting Include in Template
To modify the template with scripting include code:
- Go to the Home area.
- Browse to a page that uses the desired template. In our case, we will select about.
- On the View tab of the page, click the Configurations pane to view the individual configurations and their corresponding templates.
- With the configurations and their templates displayed, click on the template to be modified. In our case, we will select templates/standard from the HTML configuration.
- Now with the template displayed, click the Edit tab.
- For the XML field, scroll to the very bottom and put in the appropriate include code before the tag. For our ASP example, we will enter:
- Click the Submit button to record the template change.
With the template updated, now you can publish out the content and it will have the appropriate file extension and scripting language includes. Because the scripting language include won’t be processed in the CMS, it is sometimes important to give the CMS user a visual clue that a specific region of content will be different when it is published to the live server. The CMS supports pseudo-tags whereby content is tagged as "viewable internally" in the CMS or "externally" when content is published.
C. System View Internal and External
To incorporate the pseudo-tags for internal and external view, please do the following:
- Browse to the appropriate template. In our case, we will select templates/standard.
- Click the Edit tab.
- Scroll to the bottom of the XML field area and just before the body closing tag, type the following:
- Click Submit to record the template changes.
If you browse to a page that uses the template, you’ll see the content at the bottom of the page. When you publish the page, the resulting file won’t have the notice and will have the include for the actual dynamic code.
