• The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Standards in XML API

P

Patrick M

Guest
I am a new user of the Plesk API and I was struck by the problematic schema validations.

One rather curious validation exception I got was because I reused the same code to generate the inner elements of a Client/add and a Client/set xml requests.

When revising the schema, I understood that the exception was thrown because the sequence order was not respected:

ADD: <hosting> comes before <limits>
SET: <hosting> comes after <limits>

Working around this situation involves making two specific routines for the two calls, not very pleasant when doing maintenance.

Any ideas regarding this ?
 
You must log in or register to reply here.

Similar threads

J
How to deploy Plesk Onyx on Amazon EC2
Replies
0
Views
4K
joerg
J
M
  • Poll
Upgrading Apache, PHP and MySQL on CentOS with Plesk (level: Intermediate)
Replies
5
Views
18K
Mrinal KantiM
M
Back
Top