Skip to content
Switch branches/tags
Go to file
Cannot retrieve contributors at this time

Project: DNN Liquid Content Subscribo in Second Life


Several years ago, Second Life® residents were limited to 25 groups that they can join. Joining groups is necessary for many things, including getting freebies from a vendor, getting access to a parcel or a region, getting permissions to terraform land or modify objects, getting notices about events or new products or store discounts, and many others. Eventually, Second Life increased the allowed number of groups to 42, which is still not enough for some residents.

freebie merchandise that require group membership - Maitreya **Figure 1 - Freebie merchandise like these are usually given away to members of a store group to get customers to come back or to introduce newbies to the brand. Location: **

To capture users who don't want to use up their group slots, a few scripters have created subscribos, which are objects that residents touch to be added to a mailing list, which is stored in some database off-world (i.e., Google Sheets).

Similar techniques have been used for scripted vendors, which are inworld objects that sell merchandise. Vendors can be created without scripts; however, scripts can track what customers have bought inworld, so that they could be automatically sent updates to the product.

This also allows merchants to review their sales without having to do much bookkeeping. Inworld transactions in Linden dollars (the inworld currency) are kept on the Second Life database for only about a month. Then they are deleted forever. So, scripted vendors eliminate the worry that the record of a sales transaction is lost, just because the merchant was stranded for a few months on a remote tropical island with no internet access.

a subscribo in the Second Life Marketplace Figure 2 - One of several subscribo brands in the SL Marketplace.

DNN Subscribo

The DNN Subscribo is a basic subscribo, that uses Liquid Content™ to store customer information and announcements as content items.

  • The name of the subscription list is stored in the inworld object's description, so that multiple subscribos for different subscription lists can easily be set up.

  • When an unknown user clicks the SUBSCRIBE button, a content item of the type SL User is created.

    • The SL username becomes the name of the content item.
    • The SL UUID is saved in a text field.
    • The subscription list for that subscribo is selected.
  • When an existing user clicks the SUBSCRIBE button, ...

    • If the user is already a member of that subscription list, no change in subscription.
    • If the user is not yet a member, that subscription list is selected.
    • In both cases, the content item description is changed. (hardcoded for demo purposes)
  • When an existing user clicks the UNSUBSCRIBE button, the subscription list for that subscribo is deselected. (The user is not deleted.)

  • When anyone (not necessarily a subscriber) clicks the logo, the currently active promos are displayed.

This product can be expanded into an inworld vendor that is also a sales and customer tracking system.


On the DNN side:

  • A content type to track subscribers:

    • The SL username can be used as the content item name.
    • A single-line field to hold the SL UUID of the subscriber. This UUID is required by many Second Life APIs for private communications, product delivery, etc.
    • A multiple-choice field for mailing lists. Set to Checkboxes. Screenshot of a content type definition in Evoq Figure 3 - Content Type for the subscriber information.
  • A content type to store the promos:

    • The name/title of the promo can be used as the content item name.
    • Start datetime and end datetime define the time span when the promo is active.
    • A multi-line text for the description of the promo.

On the Second Life side:

  • A textured cube:

    • Face #0 serves as the SUBSCRIBE button,
    • Face #1 serves as the UNSUBSCRIBE button,
    • Face #3 (company logo) serves as the button to notify the user of current promos, and
    • Face #4 (left-hand side) serves as the script reset button, and
    • Faces #2 (right-hand side) and #5 (back side) will load the site in the user's chosen browser. A textured and tortured cube in Second Life with settings Figure 4 - Settings for our cube as described.
  • A Linden Scripting Language (LSL) script. LSL is the programming language used in Second Life and other OpenSim worlds. (OpenSim is a technology based on SL.) The LSL script has dependencies on the way the object is configured. You can create the same interactive object many ways:

    • You can use multiple prims that are combined into one object, and a different action is performed depending on which prim is touched. Con: Parcels and regions have limitations on land impact. A basic prim equals one land impact (LI). The LI of mesh objects vary, depending on the number of tris on the mesh. So users prefer objects that use as few prims or LI as possible. (Objects attached to avatar do not have LI limitations, although complex attachments can cause lag.)
    • You can also use just one face of the cube, and a different action is performed depending on what part of the face is touched. Con: This requires a more complex script that calculates the point that was touched and then matching it with some data structure that defines which points should do which action.
    • Our script (DNNSubscriboForSL.txt) assigns different faces of a single prim (a cube) to do different actions, which uses only one LI and less complex code.

APIs Used

The core functionality of the LSL script uses the following APIs:

LSL Script

For the complete script, see DNNSubscriboForSL.txt.

The following are the DNN-related variables used by the script:

string TGTDOMAIN = "";
string DNNUSERCONTENTTYPEID =  "00000000-0000-0000-0000-000000000000";  // "SL User"
string DNNPROMOCONTENTTYPEID = "00000000-0000-0000-0000-000000000000";  // "SL Promo"

string sImgUrl = "http://...";

    HTTP_MIMETYPE, "application/json",
    HTTP_BODY_MAXLENGTH, 16384,   // max length for Mono
    HTTP_CUSTOM_HEADER, "Authorization", "Bearer 00000000000000000000000000000000"

NOTE: You must replace the DNNUSERCONTENTTYPEID and DNNPROMOCONTENTTYPEID with the UUIDs of the content types you create in your DNN site. You must also replace the "Bearer" UUID with your own API key.

The following are the HTTP Requests:

GET using a query

t_kHttpReqGet = llHTTPRequest(
    TGTDOMAIN + "/ContentItems?ContentTypeId=" + (string) DNNPROMOCONTENTTYPEID,
    "" );

GET using the content item UUID of the specific "SL User"

t_kHttpReqGet = llHTTPRequest(
    TGTDOMAIN + "/ContentItems/" + t_kDNNID,
    "" );


t_kHttpReqPost = llHTTPRequest(
    TGTDOMAIN + "/ContentItems?publish=true",
    sPostStr );


t_kHttpReqPut = llHTTPRequest(
    TGTDOMAIN + "/ContentItems/" + t_kDNNID + "?publish=true",
    sPostStr );

To parse the JSON structure returned in the HTTP Response, insert the parsing code (using llJsonGetValue()) in the http_response event handler.

Flowchart Figure 5 - Flowchart of the LSL script.


  • An Evoq site.
  • Superuser/Host access to your site.
  • A Second Life account.
  • Some knowledge of how to create and manipulate prims.
  • Some knowledge of how to script in the Linden Scripting Language. (Or copy the script from DNNSubscriboForSL.txt.)
  • 10L$ (10 Linden dollars = approximately US$0.04) to upload a texture.


  1. In Evoq, create a content type and an API key.

    1. Create an API key.

    2. Create a content type for users. See Figure 3.

      1. Set the content type name to SL User.
      2. Create the following fields:
        1. (Single-line) Name: SL UUID
        2. (Multiple Choice) Name: Subcriptions Appearance: Checkboxes Choices: inactive, customer, creator, announcements, gifts, etc. (The script uses announcements.)
  2. In a graphics program, create a square texture.

    1. The bottom 1/8 as a red stripe for unsubscribing.

    2. The next higher 1/8 as a green stripe for subscribing.

    3. The remaining space to indicate what mailing list people would be subscribing to. NOTE: Save the texture as .jpg (not .png). The image must not be more than 2048x2048 pixels, which will be automatically shrunk to 1024x1024 during upload.

    Sample texture: (You can request a full-perms copy of this texture inside Second Life from DNNDiaNNa.) DNN Subscribo texture Figure 6 - Sample texture to be applied on the prim for the subscribo.

  3. Inside Second Life, put the subscribo together.

    1. Upload the texture.

    2. Create the object.

      1. Rez a cube.
      2. Torture the cube.
        • Size: <0.5, 0.60396, 0.01>
        • Taper: x = 0.0, y = 0.8
        • Top Shear: x = 0.0, y = -0.2
      3. Apply the texture. Adjust the texture scale and offset for each of the active faces to show only the relevant part of your texture.
    3. Create a new script.

      1. Create a new script in the Contents tab of the object or in your inventory.
      2. Copy and paste the LSL code to the script you created (replacing the default code) and save.
      3. In the script, replace the values for the following:
        • DNNUSERCONTENTTYPEID - The identifier for the *SL User" content type.
        • DNNPROMOCONTENTTYPEID - The identifier for the *SL Promo" content type.
        • BASIC_HTTP_PARAMETERS > HTTP_CUSTOM_HEADER - The API key after "Bearer". NOTE: These numbers differ for every Evoq site.
      4. You can make additional changes as you wish.
    4. Set the permissions of the script and the object itself as needed. Recommended: Copy only for both the subscribo object and the script.

Related links

DNN DiaNNa with completed subscribo Figure 7 - DiaNNa (username:dnndianna) inside Second Life with the completed subscribo.