Skip Navigation

Frequently Asked Questions

  • Why can't a SiteExecutive user view the Source button?

    In order for a user to see the Source button when editing a page or template, the user must:

    • Be added to the SE Page Source or SE Template Source group.
    • Have at least Write access to the area where the page or template is located.
    • Have Read access to the Administrative Users node within the Site Explorer, either individually or through a group that has Read access to the node.
  • Where can I get sample files for the Advanced Forms module?

    Sample files can be found here: <siteexecutive_root>\server\mod\addons\semod_advancedforms\_sample.

    Sample files include: State and Country text populators, Module populator, Custom Result Handler, and Javascript functions.

  • How can I control the HTML output of the Navigation module?

    There are two configurable fields in the Navigation module that allow users to restrict the levels of navigation that are shown. Start Level allows a user to specify which level of navigation to begin rendering in the instance of the module. End Level allows a user to specify which level of navigation to stop rendering in the instance of the module. These fields relieve the problem with site crawlers and text-only browsers reading the entire HTML of navigation hidden by CSS.

  • How does the Image Rotator module function differently on a page than a template?

    When inserted on a page, the images included in the Image Rotator module can be displayed as a slide show and can be set up to rotate automatically or manually by site visitors. When inserted on the template, the images can appear as background or foreground images, but will not rotate on their own. The images will rotate when the web browser window is refreshed.

  • Why are the Properties of my uploaded image incorrect?

    Images created in CMYK mode, when uploaded to SiteExecutive, display incorrect attributes (such as image height and width and file size). These images cannot be rendered by the web server. These files will sometimes become locked and cannot be deleted or replaced, causing significant performance issues. To avoid rendering and performance problems, content authors should use the RGB mode when creating images for SiteExecutive. If an image in CMYK mode must be used, the image mode should be changed to RGB through an image editor such as PhotoShop.

  • Why do I receive a 404 error when clicking a link to a file?

    This happens when a file uploaded into a multi-server instance of SiteExecutive is not copied to the rendering server. This occurs because Microsoft IIS 6.0 requires a MIME type to replicate the file. To fix this issue, IIS must be configured with the appropriate MIME type for the affected file extension. Follow the example below to configure IIS.

    To configure IIS so SiteExecutive will upload files correctly, follow these steps for all servers:

    1. Open IIS Manager.
    2. Expland local computer server.
    3. Right-click the local computer server and select Properties.
    4. Select MIME Types tab.
    5. Click New and enter the following:
      • Associated Extension: .FLV
      • MIME Type: flv-application/octet-stream
    6. Click OK
    7. Restart IIS
  • Why is my published page not rendering?

    When a page has an expiration date set, that page will stop appearing as an active page when the expiration date is reached. In order to become active again, the page must be re-published. On the Approval tab, SiteExecutive will display a notification that the expiration date needs to be reset before the page can be re-published. The content author must edit the Expire Date field in the Properties tab first before re-publishing.

  • Why am I receiving the error: "Element site undefined in CFML structure"?

    This occurs when the site URL you are trying to access is not in the se.conf file as serveralias. To fix this, put the site URL as the name value of the serveralias in the se.conf file and restart ColdFusion service. Example:
    <serveralias name="" />

  • Why do administrators receive an email stating that a form cannot be submitted?

    By default, a ColdFusion Session is set to timeout after 20 minutes. This creates problems because if a user takes longer than the ColdFusion Session variable to submit the form, then the session times out and the submission is considered SPAM. If you desire to change this default, consider the following steps.

    1. Log into ColdFusion Administrator.
    2. On the left, under Server Settings, select Memory Variables.
    3. Under Default Timeout, enter the desired length for the Session Variables.