MLCGetMemberStatus Method (ConnectionId, SessionId, String, Int32, String) Content Studio 5.7 SDK
Content Studio Web Content Management System

[This is preliminary documentation and is subject to change.]

Retrieves the MLC status for an MLC member (category).

Namespace: ContentStudio.Document.MLC
Assembly: CSServer5 (in CSServer5.dll) Version: 5.7.5016.0 (5.7.5016.0)
Syntax

public string GetMemberStatus(
	ConnectionId connectionId,
	SessionId sessionId,
	string xmlParameterData,
	out int status,
	out string statusText
)

Parameters

connectionId
Type: ContentStudioConnectionId
A value that identifies the web site
sessionId
Type: ContentStudio.SecuritySessionId
A value that identifies the user's session. This value usually originates from a call to OpenSession(ConnectionId).
xmlParameterData
Type: SystemString
XML that contains the parameters that this call uses. This XML is according to the Content Studio parameters XML schema
status
Type: SystemInt32
An integer indicating result of the call. Zero is success.
statusText
Type: SystemString
The textual representation of the call result.

Return Value

Type: String
Xml with the following sample syntax
<root>
    <status>0</status>
    <statustext>Success</statustext>
    <mlcstatus masterid="527" mastername="Svenska EPT-Dokument" mastermodule="XMLDocument" masterlanguageid="1053" masterlanguage="Swedish - Sweden" masterlanguagecode="sv" status="2" languageid="1030" language="Danish" languagecode="da" pathname="MLC/Svenska EPT-Dokument/Danska EPT-Dokument" />
    <!-- more member elements can follow -->
</root>

The status value can be either zero which indicates that the category is not an MLC member or a combination of the following flags values.
  • 0x1 - Master category
  • 0x2 - Member category
  • 0x4 - A connected object exists (for master categories only)
Content Studio permissions

Read permission is required on the selected category.
Remarks

This is the backwards compatible implementation of this method. This implementation does not throw any exceptions, instead callers must examine the outcome of the call in the Status and StatusText output parameters.
See Also

Reference