• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

XML Parser Error

A

AndrewT

Guest
I am trying to develop a Plesk server plugin for ClientExec. Whenever I execute the plugin code using the CE software i keep getting this error
<?xml version="1.0"?>
<packet version="1.3.2.4">
<system>
<status>error</status>
<errcode>1002</errcode>
<errtext>Parser error: Cannot parse the XML from the source specified</errtext>
</system>
</packet>

Here is the code I am using to create a new client
<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
<packet version="1.3.1.0">
<client>
<add>
<gen_info>
<cname>test</cname>
<pname>this</pname>
<login>out</login>
<passwd>12345</passwd>
</gen_info>
</add>
</client>
</packet>

I notice the packet versions are different. Could that be a problem? I have tested this as a standalone script and it works fine. Any ideas?

Thanks in advance!
 
I figured out what was going on....

Plesk returns a xml repsonse. So I had two identical tags on the page causind the error.

I have another question - how can shutoff the xml output that comes from plesk after using the api?
 
It depends on where you can ignore this output.
If you are using php scripts - you can utilize php output buffering for example...
 
Same problem with Expand and 7.5.2 on FBSD, all operations with domains wors fine..
 
Back
Top