The set operation lets you change settings of specified sites.
A request XML packet that changes site settings should include the set operation node:
<packet>
<site>
<set>
...
</set>
</site>
</packet>
The set node does not have a separate type, it is nested within the complex type (site.xsd
). The set node has the following graphics representation:
It indicates sites to be updated with the specified information. Data type: siteFilterType (site.xsd
). To see the structure of this node, proceed to section Available Filters.
It contains a collection of settings that will be set for the filtered sites. Data type: none.
It specifies a collection of general site settings that will be set for the filtered sites. Data type: setSiteGenSetupType (site.xsd
). To see the structure of this node, proceed to section Node set/gen_setup.
It specifies a collection of preferences for the filtered sites. Data type: domainPrefs (plesk_domain.xsd
). To see the structure of this node, proceed to section Site Preferences.
It specifies hosting settings for the filtered sites. Data type: siteHostingAgentSet (site.xsd
). To see the structure of this node, proceed to section Hosting.
It specifies the amount of disk space allotted for email boxes and mailing lists on the filtered sites. Data type: none. To see the structure of this node, proceed to section Disk Space Usage.
Important: When creating request packets, put nodes and elements in the order they follow in the packet structure.
The set node of the response packet is structured as follows:
common.xsd
).Below is an example of a request packet which sets hosting properties for domain sample3.tst (on Windows hosting):
<packet>
<site>
<set>
<filter>
<name>sample3.tst</name>
</filter>
<values>
<hosting>
<vrt_hst>
<property>
<name>fp</name>
<value>false</value>
</property>
<property>
<name>fp_ssl</name>
<value>false</value>
</property>
<property>
<name>fp_auth</name>
<value></value>
</property>
<property>
<name>fp_admin_login</name>
<value></value>
</property>
<property>
<name>fp_admin_password</name>
<value></value>
</property>
<property>
<name>ssl</name>
<value>true</value>
</property>
<property>
<name>php</name>
<value>true</value>
</property>
<property>
<name>php_handler_id</name>
<value>fastcgi-5.3</value>
</property>
<property>
<name>ssi</name>
<value>false</value>
</property>
<property>
<name>cgi</name>
<value>true</value>
</property>
<property>
<name>perl</name>
<value>true</value>
</property>
<property>
<name>python</name>
<value>true</value>
</property>
<property>
<name>asp</name>
<value>false</value>
</property>
<property>
<name>asp_dot_net</name>
<value>false</value>
</property>
<property>
<name>miva</name>
<value>false</value>
</property>
<property>
<name>webstat</name>
<value>awstats</value>
</property>
<property>
<name>webstat_protected</name>
<value>true</value>
</property>
<property>
<name>errdocs</name>
<value>false</value>
</property>
<property>
<name>php_version</name>
<value>5.3</value>
</property>
<property>
<name>webdeploy</name>
<value>false</value>
</property>
<property>
<name>www_root</name>
<value>/sample4</value>
</property>
</vrt_hst>
</hosting>
</values>
</set>
</site>
</packet>
Response:
<packet version="1.6.3.0">
<site>
<set>
<result>
<status>ok</status>
<filter-id>18</filter-id>
<id>18</id>
</result>
</set>
</site>
</packet>