S29 Site Information

Use the S29 Tag to display different types of site information such as the site ID, domain, session ID, and remote address.

A secure_path_full parameter is available for sites with custom and non-custom secure domains. For details and examples, see Using the secure_path_full parameter.

Application

Platform

Can You Add This S-Tag in the WYSIWYG content editor?

No, this S-Tag cannot be added using the WYSIWYG content editor toolbar. Add the S-Tag code to the HTML using the Plain Text editor. 

Can You Add This S-Tag in the Luminate CMS WYSIWYG content editor?

No, this S-Tag cannot be added using the Luminate CMSWYSIWYG content editor. Add the S-Tag code to the HTML using the Plain Text editor in Luminate CMS.

Format

  • Standard[[S29: parameter]]

  • XML<convio:session name="29" param="parameter" />

Parameters

  • admin_domain - Renders domain name of administrative server for site

  • admin_path - Renders current administrative path

  • domain - Renders the nonsecure domain name of the site

  • original_domain - Renders the original host name used for the current request before redirection

  • path - Renders the current path

  • request_domain- Renders the host name used for the current request

  • remote_addr - Returns the IP address of the client machine in dotted quad format (For example, 203.163.198.221)

  • secure_domain - Renders the secure domain name of the site

  • secure_path - Renders the secure path

  • secure_path_full - Renders the secure domain name of the site followed by the site shortname portion of the path (for sites that do not have a custom secure domain). You can use secure_path_full to replace domain when you construct secure URLs to resources on your site, where the URL does not include the /site/ portion. For details and examples, see Using the secure_path_full parameter.

  • session_ID - Renders session ID

  • site_ID - Renders site ID

  • user_ID - Renders user ID

Sample Code

  • Standard

    <a href="https://[[S29:secure_path_full]]/ConsProfileUser">Printer Friendly</a>

    <img src="[[?x0x::x[[S4]]x::https://[[S29:secure_path_full]]::..]]/images/Recur.jpg" width="9" height="9" alt="Recurring event!">

  • XML

    <convio:session name="29" param=" REMOTE_ADDR " />

Using the secure_path_full parameter

For sites with a secure domain, the secure_path_full parameter can replace domain when you construct secure URLs to resources on your site where the URL does not include the /site/ portion. The parameter renders the secure domain, followed by the site shortname in the URL path.

What does each parameter represent?

  • Non-custom secure domain
    If the URL to a nonsecure PageBuilder page on the site starts with http://www.mynpsite.org/site/PageServer? and the URL to a secure donation form on the site starts with https://secure2.convio.net/mynpsite/site/Donation2?, then:

domain = www.mynpsite.org

path = /site/

secure_domain = secure2.convio.net

secure_path = /mynpsite/site/

secure_path_full = secure2.convio.net/mynpsite/

  • Custom secure domain

    If the URL to a nonsecure PageBuilder page on the site starts with http://www.mynpsite.org/site/PageServer? and the URL to a custom secure donation form on the site starts with https://secure.mynpsite.org/site/Donation2?, then:

domain = www.mynpsite.org

path = /site/

secure_domain = secure.mynpsite.org

secure_path = /site/

secure_path_full = secure.mynpsite.org/

Example

The footer of your email links to an image at this location:

http://www.mynpsite.com/content/images/myEmailFooter.jpg

And you can access that image securely on a:

  • Default secure domain https://secure2.convio.net/mynpsite/content/images/myEmailFooter.jpg

    --OR--

  • Custom secure domain, such as secure.mynpsite.org https://secure.mynpsite.org/content/images/myEmailFooter.jpg

You can write the nonsecure URL as:

http://[[S29:domain]]/content/images/myEmailFooter.jpg

Or, if you have a custom secure domain, you can write the secure URL as:

https://[[S29:secure_domain]]/content/images/myEmailFooter.jpg

However, note that this will fail for the default secure domain, because it's missing the /mynpsite/ portion of the URL (the site shortname identifier).

So, if you use the secure_path_full parameter and write the secure URL as:

https://[[S29:secure_path_full]]content/images/myEmailFooter.jpg,

this will work for both a default and custom secure domain.

The advantage of using S29 in these scenarios is that the URL will continue to work if the domain or secure domain changes in the future.