|
The behavior when creating content instances is to
1) update the state tag of the parent container
2) use the value of the state tag in the parent as value for content instance state tag
3) ensure the content instance "fits" in the container ie it will not exceed the value
of the parent container's max_byte_size
4) ensure max_instances of parent is not zero as then NO content instances will fit
5) if this new content instance causes the cumulative number of instances to be over
the quota, then post process by removing the "oldest" instance. Also, remove "older"
instances until the cumulative value of the byte_size of the container is under quota.
The behavior when updating max_nr_instances (mni), or max_byte_size (mbs) of a container is to re-validate the container's quota and remove "older" instances until the quotas have been met. Obviously this will only happen if the new values for
mni and/or mbs are reduced.
Should now be fixed!
|