Facebook
Twitter
R
rootusertom
Guest
Hello,
I am sorry but the RPC-API is driving me nuts.
As root, I can fetch all sites by leaving the filter empty. If I try that in the role of a certain reseller, I get no domains at all, though some of the sites were created by that reseller.
If I try to fetch a certain site of the reseller by using its ID or name as a filter, this will work.
This will also work whe I use parent-id as a filter, inserting the webspace id.
When I use the parent-id filter on a webspace with no sites, I get an 'ok' response (which I deem the correct answer).
But when do that as root I get an error: 1015 Webspace does not exist
The documentation says this error code means "Object owner not found". What is correct? And what is more: why do I get an error at all?
If it is the policy that root cannot fetch data belonging to resellers, why can I fetch all customers and webspaces then, regardless if I fetch all or certain ones at a time?
This is very confusing and frustrating.
(All API requests have been made using protocol version 1.6.3.4)
Regards, Tom
I am sorry but the RPC-API is driving me nuts.
As root, I can fetch all sites by leaving the filter empty. If I try that in the role of a certain reseller, I get no domains at all, though some of the sites were created by that reseller.
If I try to fetch a certain site of the reseller by using its ID or name as a filter, this will work.
This will also work whe I use parent-id as a filter, inserting the webspace id.
When I use the parent-id filter on a webspace with no sites, I get an 'ok' response (which I deem the correct answer).
But when do that as root I get an error: 1015 Webspace does not exist
The documentation says this error code means "Object owner not found". What is correct? And what is more: why do I get an error at all?
If it is the policy that root cannot fetch data belonging to resellers, why can I fetch all customers and webspaces then, regardless if I fetch all or certain ones at a time?
This is very confusing and frustrating.
(All API requests have been made using protocol version 1.6.3.4)
Regards, Tom
