This is a list of known issues / incompatibilities with QuotaFolder

Bugs in Zope:

- ZopeTutorial does some inproper exception catching, causing QuotaExceeded
  errors to be ignored (and actually the product to be imported twice).
  The relevant code is:

      try:
        folder.manage_importObject(tutorialExamplesFile)
    except:
        folder._p_jar=self.Destination()._p_jar
        folder.manage_importObject(tutorialExamplesFile)
        
- A similair problem probably occurs when installing userfolders - if a user is past 
  his quota and tries to create a userfolder, the error 'this folder already contains a 
  userfolder', and the userfolder is created nonetheless

  This actually brings the quotafolder out of sync!!! (because due to the exception,
  the quota isn't updated, but the transaction isn't aborted either)

  -- RESOLVED 16Mar02 This bug has been worked around, though the error 'this object
     already has a userfolder' will appear if the quota is exceeded.

Bugs in QuotaFolder:

- Maximum object size is not always enforced, esp. when importing objects
  (or hierarchies of objects)

- The following script used to give problems:

    doc = container.doc
    container.manage_delObjects(['doc'])
    doc.manage_edit('hello'*100, 'hacked')

  Hooked objects now check if they are still contained in their parent.
  What if doc is placed in a pseudo parent folder?

- Pressing 'Sync' in the Quota tab brings you back to the Quota tab, however,
  the tab itself indicates 'Contents' is selected. -- RESOLVED 18Mar02

- QuotaExceeded exceptions aren't always precise - it displays how much quota
  you would need for the operation, but that may not be correct.

- QuotaFolder seems to mess up undo capabilities (under what circumstances?)

- QuotaFolder is not compatible with FLE. Creation goes fine (it seems), but
  newly created objects / modified objects are not added. -- RESOLVED 16Mar02

- It is still possible to store large amounts of data in properties. A solution
  would be to test if an object is an instance of PropertyManager, and account
  the size of the properties appropriately.
