* Can't view manage_main, get: The parameter, <em>trueself</em>, was omitted from the request.
Funny I got this error just yesterday with the following snip of code: def __getitem__(self, key, REQUEST=None): # yeah return HTMLFile('null', globals()) if you create a object, x and access http://.../x/y then I get the exact same error. http://.../x/y?trueself=1 (or any other value) brings up the 'null' document correctly. I wanted to create an object that hooked into a filesystem on disk, turning the rest of the Zope request into a relative path access. Myguess was the problem stems from the fact that I am returning a method and not an object and ZPublisher expects to get an object from a x['y'] (__getitem__) access.
* Display in Folder listing is bogus:
<? icon> Zope ()
Even though I gave it an id and title..
THIS I've seen before. Here is my original post:
When you return to the management interface, any previous NM or ZT entried you added have the id 'Zope', and no title (in the alpha and bogus beta 1, it's says 'Principia' instead, this is the difference mentioned previously). Clicking on them also gives a 404. Quite strangely, on the left hand frame (if you refresh) each object you created will put a titleless folder icon in the tree with a plus icon next to it, clicking on the icon will break the folder open an in there you will find another titleless folder icon with a plus, and so on, ad infinitum.
Do you have the infinite folder problem with the left hand navigation screen described above? Here was my solution:
Well, if anyone was curious I found the problem that was causing my application object to disapear. Acutally Skip, your the one who posted this problem that made me figure it out (with a big DUH!) In the near past before Zope I tried out BoboPOS, but instead of reading the package docs and figuring that out I just dumped all the files into my /lib/python1.5/ dir. Now, when my programs import the Persistent class the *old* way (the new way way, of course, for me to discover later) import Persistence it loaded the old Persistence class, instead of the *new* one which is properly loaded import BoboPOS.Persistence this is why I was getting __class__ name errors in the TJar.py component. Obviously the older objects don't work with the new long running transactions that TJar gives us. This is a subtle error, if your custom objects give the above error, you are using an old version of the Persistence.Persistent class with the new version of the POS. Is there a way this can be made to fail quite obviously? Michel
This might not be your problem, but some of the symptoms are similar. Hope this helps. Michel