Closed ayvazyan10 closed 5 months ago
I can't confirm disabling the customer with status 1 leads to "crashing." Please provide more detailed STRs.
P.S. Despite the fact status 1 is undocumented, it's still valid, and everything should work as expected.
i provided full details explanation, also give links on api docs, i checked in on my server and not going to check again because it very hard to recover stacked status plesk db, you can reject pull request.
The status node is optional. It specifies the current status of the customer account. Data type: objectStatus (plesk_common.xsd). Allowed values: 0 (active) | 16 (disabled_by admin) | 4 (under backup/restore) | 256 (expired). Default value: 0. Only status values 0 and 16 can be set up.
from official documentation.
For customers allowed status can be only 0 or 16. Also webspaces(subscribtions) allowed values: 0 (active) | 16 (disabled_by admin) (there is no status "1")-- when status 1 is provided on customer plesk db is crashing somehow and customer stacked in disabled mode.
https://docs.plesk.com/en-US/obsidian/api-rpc/about-xml-api/reference/managing-customer-accounts/customer-settings/general-customer-account-settings/type-clientsetgeninfo.34625/
https://docs.plesk.com/en-US/obsidian/api-rpc/about-xml-api/reference/managing-subscriptions/subscription-settings/general-subscription-information/node-gen_setup-type-setgensetuptype.33860