this has nothing to do with zope.
the problem is due to the severe monkey patching, use of eval, and other
bad practices in this product.
its monkey patched attributes into zcatalog and in doing so altered the
modules namespace, replacing the id function with a string.
which leads to the error,
Note that 2.6.4 contains massive changes to the security
implementation. I'd imagine the product you use has not been updated
accordingly.
Stefan
On 13.10.2004, at 17:24, Nagarjuna G. wrote:
This product works perfectly till 2.6.3, starting from 2.6.4 and
upwards this problem appears. Looking
Can anybody please help me,
Our product Named GNOWSYS is working perfectly in zope 2.6
but when ported to zope 2.7 it does'nt get instantiated.
I guess the way we are cataloging our Objects is not correct
The Traceback of the error that occurs when we try to instantiate our product
is as follows
Best to contact the authors of the corresponding directly.
-aj
--On Mittwoch, 13. Oktober 2004 16:32 Uhr +0530 MET 2004-2005
[EMAIL PROTECTED] wrote:
Can anybody please help me,
Our product Named GNOWSYS is working perfectly in zope 2.6
but when ported to zope 2.7 it does'nt get instantiated.
I
On Wed, Oct 13, 2004 at 12:56:50PM +0200, Andreas Jung wrote:
Best to contact the authors of the corresponding directly.
Well, the author (undersigned) doesn't know what to do. The question
was not from the users of the application but from the developers.
This product works perfectly till
--On Mittwoch, 13. Oktober 2004 20:54 Uhr +0530 Nagarjuna G.
[EMAIL PROTECTED] wrote:
On Wed, Oct 13, 2004 at 12:56:50PM +0200, Andreas Jung wrote:
Best to contact the authors of the corresponding directly.
Well, the author (undersigned) doesn't know what to do. The question
was not from the
MET 2004-2005 wrote at 2004-10-13 16:32 +0530:
...
The Traceback of the error that occurs when we try to instantiate our product
is as follows
Exception Type TypeError
Exception Value 'str' object is not callable
* Module Products.ZCatalog.ZCatalog, line 537, in
