Versions

EditLive 8.x
EditLive 7.x

EditLive 8 Documentation

Skip to end of metadata
Go to start of metadata

Overview

When implementing EditLive! within an application using the ASP or JSP load-time properties provided with EditLive!, it is important to note the scope of the properties once they are set. This section of the documentation details the scope of each load-time property. Properties with a global scope affect all instances of EditLive! within a page, while properties with a local scope affect only the instance of EditLive! they are set for.

In the EditLive! JavaScript load-time properties, all properties are local and must be set individually for each instance of EditLive!.

Distinguishing Between Local and Global Properties in ASP, ASP.NET and JSP

When using either the ASP or JSP load-time properties of EditLive!, local and global properties are set in separate objects or tags.

For ASP, global properties are set on the EditLiveForJavaGlobal object while local properties are set via the EditLiveForJava object.

For JSP, global properties are set on the ELJGlobal tag while local properties are set via the ELJInstance tag.

For ASP.NET load-time properties, both local and global properties are set via the same tag. If multiple instances of EditLive! are declared in the same page then the global properties set in the first instance of EditLive! take precedence over any others.

Global Properties

Note: The Init Method (ASP only) must be called on the EditLiveForJavaGlobal object in the ASP load-time properties in order to load these values for all instances of EditLive! on the page.

Local Properties

Note: The Show Method must be called on the EditLiveForJava object in the ASP load-time properties in order to load these values for the specific instance of EditLive! on the page.

Labels: