comanage-dev - [comanage-dev] CoPersonRole creation via REST fails
Subject: COmanage Developers List
List archive
- From: Scott Koranda <>
- To: comanage-dev <>
- Subject: [comanage-dev] CoPersonRole creation via REST fails
- Date: Sat, 2 Mar 2013 15:40:23 -0600
- Authentication-results: sfpop-ironport03.merit.edu; dkim=pass (signature verified)
Hi,
When I try to create a CoPersonRole via the REST API it fails
with this:
403 CO Does Not Exist
This error is being thrown in checkRestPost() in
AppController.php in this clause:
if($this->requires_co && !isset($this->cur_co)) {
// If a CO is required and we didn't find one,
// bail
$this->restResultHeader(403, "CO Does Not Exist");
return(false);
}
Yes, I am sure it is there in that clause and not the one
above it.
The CoPersonRole model does have requires_co set, but I have
looked through beforeFilter() and add() at all levels in the
controllers (CoPersonRoleController, StandardController, and
AppController) and I don't see how the CO could be set during
a REST call.
The API doesn't include a CoId. I tried putting one in just in
case but that didn't work.
I think the right place to fix this is in checkRestPost(), but
I am not sure.
Please advise...
Scott
- [comanage-dev] CoPersonRole creation via REST fails, Scott Koranda, 03/02/2013
- [comanage-dev] Re: CoPersonRole creation via REST fails, Scott Koranda, 03/02/2013
- [comanage-dev] Re: CoPersonRole creation via REST fails, Scott Koranda, 03/03/2013
- [comanage-dev] Re: CoPersonRole creation via REST fails, Scott Koranda, 03/02/2013
Archive powered by MHonArc 2.6.16.