[Zope] title is not safe for unpickling

[Brian Withun]

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C0D877.B6E25D10
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by hilgraeve.com id JAA17350


Using 2.1.4 on linux, I have run into the following error:

"title is not safe for unpickling"

I get this error when I try to rename or delete a particular object in on=
e
of my folders.  The object itself is troubling because the management
interface shows the object to be a folder (the little icon is the folder
icon) but it's not a container, I can't get inside of it.  Deleting it is
impossible, and deleting any PARENT of it is impossible.  Although it
carries a folder icon, the management tree (at left) does not have a litt=
le
"+/-" expander box next to it.  It is definitely not a true folder.

And no, I have no ZClasses or anything like that.  We use ZSQL and DTML
Methods and DTML Objects, and Mailhosts, and a database connection or two=
,
but nothing more sophisticated than that.

I'm attaching an export of the parent folder to this object, as well as a=
n
export of the object itself.

On my system, the folder "Personal" contains this object named
"form_wrapper_wrapper"  When form_wrapper_wrapper was originally created,=
 it
was a DTML Method.  It is no longer a DTML Method, and I can't fathom wha=
t
has happened to it.

"tranalyzer.py" found some problems in the Zope transaction log, and pack=
ing
the Data.fs made tranalyzer.py happy, but of course did nothing to correc=
t
the actual problem.  The last entry spit out by tranalyzer.py before the
problem had to do with a version I had created.

Lately, two rare things have happened, neither of which are an obvious
culprit, but they may be worth mentioning:
1) I created, used, and committed a version.  I don't do that often, and =
so
having done this so coincidentally in time with the introduction of the
error carries some suspicion.  The version created did not, however, modi=
fy
anything near the form_wrapper_wrapper.

2) Another developer has been playing with WebDrive, attempting to access
objects on the Zope server.  It doesn't appear that 2.1.4 played well wit=
h
WebDrive and our editor of choice, so WebDrive was dropped for the time
being.  We have no reason to believe that WebDrive caused any problems, b=
ut
again, it was on the same day the error was introduced so suspicion is hi=
gh
(though we never accessed form_wrapper_wrapper from WebDrive!)

Does anyone have any ideas?  Is there some "undocumented" way of destroyi=
ng
a Zope object?

When I access the form_wrapper_wrapper object (try to view its contents) =
 I
get a Zope error, which has also been attached.

The last oddity I've noticed is that when I change the title of the paren=
t
folder (Personal), the title changes on BOTH the Personal folder, and the
form_wrapper_wrapper thing inside of the Personal folder...

hmmmmmmm ?

------------
Bri=E1n Withun

------=_NextPart_000_000C_01C0D877.B6E25D10
Content-Type: application/octet-stream;
	name="Personal.zexp"
Content-Disposition: attachment;
	filename="Personal.zexp"
Content-Transfer-Encoding: base64

WkVYUAAAAAAAABHvAAAAAAAAAQooKFUKT0ZTLkZvbGRlcnEBVQZGb2xkZXJxAnRxA050Ln1xBChV
AmlkcQVVCFBlcnNvbmFscQZVEl9fYWNfbG9jYWxfcm9sZXNfX3EHfXEIVQxCcmlhbiBXaXRodW5x
CV1xClUFT3duZXJxC2FzVQhfb2JqZWN0c3EMKH1xDShVCW1ldGFfdHlwZXEOVQtEVE1MIE1ldGhv
ZHEPaAVVFGZvcm1fd3JhcHBlcl93cmFwcGVycRB1dFUFdGl0bGVxEVUSQUJTREZLQUpEU0ZMS0FK
U0RncRJoEChVCAAAAAAAABHEcRMoVQ5PRlMuRFRNTE1ldGhvZHEUVQpEVE1MTWV0aG9kcRV0dFF1
Lv////////////////////8=

------=_NextPart_000_000C_01C0D877.B6E25D10
Content-Type: application/octet-stream;
	name="form_wrapper_wrapper.zexp"
Content-Disposition: attachment;
	filename="form_wrapper_wrapper.zexp"
Content-Transfer-Encoding: base64

WkVYUP////////////////////8=

------=_NextPart_000_000C_01C0D877.B6E25D10
Content-Type: text/plain;
	name="zope error.txt"
Content-Disposition: attachment;
	filename="zope error.txt"
Content-Transfer-Encoding: quoted-printable

<HTML>
<HEAD><TITLE>Zope Error</TITLE></HEAD>
<BODY>

<TABLE BORDER=3D"0" WIDTH=3D"100%">
<TR VALIGN=3D"TOP">

<TD WIDTH=3D"10%" ALIGN=3D"CENTER">
&nbsp;
</TD>

<TD WIDTH=3D"90%">
  <H2>Zope Error</H2>
  <P>Zope has encountered an error while publishing this resource.
  </P>
  <P><STRONG>Debugging Notice</STRONG></P>
 =20
  Zope has encountered a problem publishing your object.<p>
Missing doc string at: https:// [edited] =
/Home/Addresses/L/Personal/form_wrapper_wrapper
  <HR NOSHADE>

  <P>Troubleshooting Suggestions</P>

  <UL>
  <LI>The URL may be incorrect.</LI>
  <LI>The parameters passed to this resource may be incorrect.</LI>
  <LI>A resource that this resource relies on may be encountering an =
error.</LI>
  </UL>

  <P>For more detailed information about the error, please
  refer to the HTML source for this page.
  </P>

  <P>If the error persists please contact the site maintainer.
  Thank you for your patience.
  </P>
</TD></TR>
</TABLE>

</BODY>
</HTML>
<PRE>
Traceback (innermost last):
  File /usr/lib/Zope-2.1.4-src/lib/python/ZPublisher/Publish.py, line =
214, in publish_module
  File /usr/lib/Zope-2.1.4-src/lib/python/ZPublisher/Publish.py, line =
179, in publish
  File /usr/lib/Zope-2.1.4-src/lib/python/Zope/__init__.py, line 202, in =
zpublisher_exception_hook
    (Object: ElementWithAttributes)
  File /usr/lib/Zope-2.1.4-src/lib/python/ZPublisher/Publish.py, line =
151, in publish
  File /usr/lib/Zope-2.1.4-src/lib/python/ZPublisher/BaseRequest.py, =
line 348, in traverse
  File /usr/lib/Zope-2.1.4-src/lib/python/ZPublisher/HTTPResponse.py, =
line 521, in debugError
NotFound: (see above)

</PRE>
------=_NextPart_000_000C_01C0D877.B6E25D10--