Hey Andreas, thanks for the reply. I have Globals.InitializeClass(classname) at the end of my product code (outside the class) I turned on Verbose Security, but hmm... maybe this is not a security issue after all. I have code that worked within my product before like: def send_password_reminder(self, email): """ blah """ Now I see get a name error when trying to access it. *Error Type: NameError* *Error Value: name 'send_password_reminder' is not defined I thought it was a security problem... Is this related to something else? Thanks again! -e- *Andreas Jung wrote:

--On 27. Februar 2006 15:20:11 -0800 Ed Colmar <ed@greengraphics.net> wrote:

...

Hello

I recently moved my zope product developed on a 2.8 server on to a 2.8.5 server, and all of my python code is no longer being published out.

In the past I had been using a doc string """ doc """ to make methods accessible. I realize this is not the proper procedure, but it worked. Now, on the 2.8.5 server, all of these are refused. I've been going through and doing security.declarePublic('methodname') on everything I want to be public, but it does not appear to have any effect.

Are there any other changes that I need to make to my product in order to get back the functionality I had previously?

Do you call InitializeClass()? Perhaps VerboseSecurity might help you.

-aj

hey All It appears that I have solved it... My process in moving over the product from the old server was to blame. Here's what I did: export all of the zodb contents, and tarball the python product. Then I imported the zodb contents into the new server, and un-tarred the product. This resulted in the error of not finding the python methods, even though it appeard to be connected. So, I added the product form the add menu, and copy/pasted the zodb contents, and now it's all happy. For future refrence, is there a call to conenct this class back into the zodb filesystem after it has been moved to a new instance? Thanks for all the help! -e-