During traversersing, the object targeted by 'path/to/btreefolder' is correctly retrieved.
Then, the 'my_new_file.txt' is searched, and does not exists, so, a NullResource shoud be created to handle the request.
With a regular folder, it behaves like that.
With the BTreeFolder2, the __getitem__ method, that is used in this case, is inerited from BTreeFolder2.BTreeFolder2Base and does not implement this behavior.
It can be fixed with the patch file joined to be applied at Products/BTreeFolder2/BTreeFolder2.py
This bug also occurs when you try to put an item thru webdav.
When a PUT request is done (by webdav for instance), the ressource url requested looks like this: my_zope_ server. ext/path/ to/btreefolder/ my_new_ file.txt
http://
During traversersing, the object targeted by 'path/to/ btreefolder' is correctly retrieved.
Then, the 'my_new_file.txt' is searched, and does not exists, so, a NullResource shoud be created to handle the request.
With a regular folder, it behaves like that.
With the BTreeFolder2, the __getitem__ method, that is used in this case, is inerited from BTreeFolder2. BTreeFolder2Bas e and does not implement this behavior.
It can be fixed with the patch file joined to be applied at Products/ BTreeFolder2/ BTreeFolder2. py
Regards,
Benoît.