Comment 1 for bug 143597

What do you have configured as the 'container-class' for that
database / mount point? It must be a class with an '__init__'
taking a single non-default argument (like OFS.Folder.Folder, the
default) or else a function taking a single argument; in either
case, the caller expects to supply this argument (the "id" of the
new object).

If the class you want to use can't take such an argument, then
you can create a "factory" function which constructs the object,
without it. Note that if the object doesn't know its own ID,
a number of Bad Things (TM) may occur (a broken 'absolute_url' is
the most obvious).

Close this in a month if no feedback follows, or if the configured
object does not (as I suspect) conform to the "folderish
constructor" interface.