[Zope-CMF] Replication And Workflows - "Nightmare of CMF Street"

Norfleet, Sheppard S. sheppard.norfleet at ngc.com
Tue Sep 16 15:23:46 EDT 2003


Replication And Workflows
"Nightmare of CMF Street"

I am having a heck of a time with my application level replication.  I am
able to recreate the object, but apparently the workflow_history attribute
does not seem to travel with the object its tied to.  This seems to be the
case because after I assign the object to the parent on the mirror machine
using xxx._setObject() of the replicated object, the state always seems to
fall back to 'created'.  

I hate it when I don't understand whats going on, the only thing I can see
thats different or weird is that the WorkflowTool uses a PeristentMapping as
a dictionary instead of a plain jane dict {}.  Since its an attribute of the
object, why the special persistant object? I mean its gonna get pickled and
jarred anyway.

Regards,

Sheppard Norfleet

-----Original Message-----
From: zope-cmf-request at zope.org [mailto:zope-cmf-request at zope.org]
Sent: Tuesday, September 16, 2003 12:03 PM
To: zope-cmf at zope.org
Subject: Zope-CMF Digest, Vol 2, Issue 13


Send Zope-CMF mailing list submissions to
	zope-cmf at zope.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://mail.zope.org/mailman/listinfo/zope-cmf
or, via email, send a message with subject or body 'help' to
	zope-cmf-request at zope.org

You can reach the person managing the list at
	zope-cmf-owner at zope.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Zope-CMF digest..."


Today's Topics:

   1. Re: KeyError: main_template when upgrading to CMF 1.3.2
      (Tim Terleg?rd)
   2. Re: [dev] delete members: related changes and updated
      proposal (Tres Seaver)
   3. Re: Re: [dev] some questions regarding Exceptions (Tres Seaver)
   4. Re: CMF 1.4.1 w/Zope 2.7.0b2: No Icons for CMF types
      (Edward Muller)


----------------------------------------------------------------------

Message: 1
Date: Tue, 16 Sep 2003 13:53:32 +0200
From: Tim Terleg?rd <timte878 at student.liu.se>
Subject: [Zope-CMF] Re: KeyError: main_template when upgrading to CMF
	1.3.2
To: Yuppie <schubbe at web.de>
Cc: Zope-CMF List <zope-cmf at zope.org>
Message-ID: <1a5ce21a7230.1a72301a5ce2 at liu.se>
Content-Type: text/plain; charset=us-ascii

> > Uh, oh. I don't remember, actually, how I installed CMF. Maybe
> > it was from CVS and perhaps it's an early 1.4. In 1.3.2 the
> > URLTool is in CMFDefault I found.
> 
> It's never a good idea to downgrade CMF. But on the over hand 
> Plone 1.0.x doesn't work with CMF 1.4.x.

No, I noticed  :)
I think I will skip 1.3.2 and go directly to CMF 1.4 when Plone
1.1 is done. I hope that will work out better.


> Your portal_url object in the root folder of your site 'knows' if 
> it is a CMFCore.URLTool or a CMFDefault.URLTool. You could delete
> the portal_url object ('CMF URL Tool') and add a 'Default URL Tool' 
> instead.

Ok, that explains things. No product imported from CMFCore so it had
to be in ZODB. You confirmed it.


> > Is the KeyError: main_template associated with the URLTool error?
> 
> Don't know. There might be other things broken, depending on the 
> date of your checkout.

I'm back with my old CMF and things work fine. Thanks for clearing
things up Yuppie!

Tim




------------------------------

Message: 2
Date: 16 Sep 2003 11:36:18 -0400
From: Tres Seaver <tseaver at zope.com>
Subject: Re: [Zope-CMF] [dev] delete members: related changes and
	updated	proposal
To: J Cameron Cooper <jccooper at jcameroncooper.com>
Cc: Zope-CMF List <zope-cmf at zope.org>, Yuppie <schubbe at web.de>
Message-ID: <1063726578.22955.73.camel at dhcp155.zope.com>
Content-Type: text/plain

On Mon, 2003-09-15 at 15:49, J Cameron Cooper wrote:

> While the idea that this method should delete the folders by default is 
> fine and expected, it seems strange to have flags that default to true. 
> If it's a "hidden" option, one should turn it on, rather than off, when 
> over-riding. How about:
> 
> def deleteMembers(member_ids, keep_memberareas=0,
>                    keep_localroles=0):

-1.  Such a refactoring is a change to the contract, and will break any
callers which were not using the defaulted parameter.  OTOH, if this is
a new API, or a private method, then feel free. :)

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com





------------------------------

Message: 3
Date: 16 Sep 2003 11:42:02 -0400
From: Tres Seaver <tseaver at zope.com>
Subject: Re: [Zope-CMF] Re: [dev] some questions regarding Exceptions
To: Yuppie <schubbe at web.de>
Cc: Zope-CMF List <zope-cmf at zope.org>, Seb Bacon <seb at jamkit.com>
Message-ID: <1063726922.22955.77.camel at dhcp155.zope.com>
Content-Type: text/plain

On Tue, 2003-09-16 at 06:59, Yuppie wrote:
> Hi!
> 
> 
> Seb Bacon wrote:
> > Yuppie wrote:
> >> Something like this?
> >>
> >>   class CMFError(StandardError):
> >>     ...
> >>   class MembershipError(CMFError):
> >>     ...
> >>   class MetadataError(CMFError):
> >>     ...
> >>   ...
> > 
> > 
> > Definitely.  I can imagine it might be worth discussing the exception 
> > hierarchy a bit.
> 
> After rereading the python docs, I think the root exception has to be
> 
>    class CMFError(Exception):
> 
> Thats the easy part.
> 
> 
> For the hierarchy I see two possible approaches:
> 
> a) by type (CMFValueError, CMFUnauthorizedError, ...)
> 
> b) by module/context (MembershipError, MetadataError, ...)
> 
> We also could combine these two:
> 
>    class MembershipValueError(ValueError, CMFError):
>    class MembershipUnauthorizedError(Unauthorized, CMFError):
>    class MetadataValueError(ValueError, CMFError):
>    class MetadataUnauthorizedError(Unauthorized, CMFError):
>    ...
> 
> 
> I attached the result of grepping CMF 1.4. Currently both approaches 
> exist. The combined solution would provide the best backwards 
> compatibility, but I'm afraid that's overkill.
> 
> I'd prefer approach b).

-1.  The existing exception types have well-understood semantics;  the
new "module-centric" ones would not.  In particular, third-party code
which currently does::

   except ValueErrror, err:

must continue to work, which implies one of:

  - status quo ante

  - approach a)

  - approach "c)" ;)

Tres.
-- 
===============================================================
Tres Seaver                                tseaver at zope.com
Zope Corporation      "Zope Dealers"       http://www.zope.com





------------------------------

Message: 4
Date: Tue, 16 Sep 2003 10:58:51 -0500
From: Edward Muller <edwardam at interlix.com>
Subject: Re: [Zope-CMF] CMF 1.4.1 w/Zope 2.7.0b2: No Icons for CMF
	types
To: Kevin Carlson <khcarlso at bellsouth.net>
Cc: zope-cmf at zope.org
Message-ID: <1063727930.23515.96.camel at palin.>
Content-Type: text/plain; charset="us-ascii"

I doubt this has anything to do with my problem. It's the CMF types that
are having problems displaying their icons in the ZMI. And it's the url
that get's rewritten wrong. The icon is there and displays properly when
I'm not using a re-written/proxied/vhm'd url. I know the rule works
because if I fall back to a zope 2.6.2 site with CMF 1.4.1 everything
works fine via the same rewrite rule.

Just to be sure I went through each of the portal_skins and reloaded
them. No change.

On Tue, 2003-09-16 at 06:51, Kevin Carlson wrote:
> This happened to me once and all I needed to do was "reload" the File
> System Directory Views in the portal_skins directory.  Select a file
> system directory view, choose the properties tab.  Make sure the
> filesystem path is pointing where it needs to be (In order to get the
> view to refresh I had to change the filesystem path to something and
> then change it back to what was already there.)
> 
> Kevin
> 
> Edward Muller wrote:
> > All the Portal Folders & Documents that I've created don't have any
> > icons in the ZMI, they only have the text 'Portal Folder' or 'Document'.
> > 
> > I am using virtual host monster.
> > 
> > Here is the particular re-write rule I am using:
> > 
> > RewriteEngine On RewriteCond %{REQUEST_URI} ^/zope/ixtest
> > RewriteRule ^/zope/ixtest(.*)
> >
http://66.98.146.88:8080/VirtualHostBase/https/ensim3.interlix.com:443/Virtu
alHostRoot/_vh_zope/_vh_ixtest/$1 [L,P]
> > 
> > 
> > I would normally access the ZMI of this zope install via:
> > https://ensim3.interlix.com/zope/ixtest/manage
> > 
> > The image urls look like this:
> > 
> > https://ensim3.interlix.com/zope/ixtest/zope/ixtest/p/document_icon.gif
> > 
> > 
> >   
> > 
> > ____________________________________________________________________
> > _______________________________________________
> > Zope-CMF maillist  -  Zope-CMF at zope.org
> > http://mail.zope.org/mailman/listinfo/zope-cmf
> > 
> > See http://collector.zope.org/CMF for bug reports and feature requests
> >   
-- 
Edward Muller - http://www.interlix.com - "Open Source Specialists"
Dedicated Zope Hosting - Web Hosting - Open Source Consulting
Network & PC Service & Support - Custom Programming
Phone: 417-862-0573 - Cell: 417-844-2435 - Fax: 417-862-0572
Jabber: edwardam at jabber.interlix.com - AIM: edwardam453 - ICQ: 287033
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url :
http://lists.zope.org/pipermail/zope-cmf/attachments/20030916/255728b3/attac
hment-0001.bin

------------------------------

_______________________________________________
Zope-CMF maillist  -  Zope-CMF at zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

http://www.zope.org/Products/PTK/Tracker for bug reports and feature
requests

End of Zope-CMF Digest, Vol 2, Issue 13
***************************************



More information about the Zope-CMF mailing list