Skip to Content.
Sympa Menu

comanage-dev - Re: Fwd: [comanage-dev] Notes on CO-172

Subject: COmanage Developers List

List archive

Re: Fwd: [comanage-dev] Notes on CO-172


Chronological Thread 
  • From: Marie Huynh <>
  • To: Benn Oshrin <>
  • Cc:
  • Subject: Re: Fwd: [comanage-dev] Notes on CO-172
  • Date: Fri, 9 Sep 2011 15:46:47 -0700

Is there a preferred pattern for the error messages in
app/libs/lang.php I should be aware of?

And just to be clear, I'm blocking deletions of COUs with children? I
have that working now.




On Thu, Sep 8, 2011 at 1:51 PM, Benn Oshrin
<>
wrote:
> On 9/8/11 4:44 PM, Marie Huynh wrote:
>>>
>>>  40x Not Member ->  403 Wrong CO
>>>  40x Has Children ->  403 Child COU Exists
>>>
>>> Note Edit also requires both checks since you can edit the parent_cou_id,
>>> which would effectively behave as a delete followed by an add.
>>
>> Do we consider deletion as a type of edit?  If deletions are in a
>> separate category, the existence or lack of children should not block
>> an edit unless you want to prevent a whole chain of COUs from being
>> moved.  Is that the case?  Or are edits actually implemented as a
>> delete + add?
>
> Edits are not implemented as delete + add, but it does come back to the
> question of how should this behave.
>
> I'm inclined to agree with Scott's message from last night and keep this
> check for delete, but maybe it makes less sense for edit? If I pick the
> wrong parent COU, why can't I easily pick another?
>
> -Benn-
>



Archive powered by MHonArc 2.6.16.

Top of Page