( Sat, 30 Apr 2005 14:10:46 -0700 ) Dave Kuhlman :

> On Thu, Apr 28, 2005 at 12:45:40AM +0200, Rakotomandimby (R12y) Mihamina
> wrote:
>> On Thu, 2005-04-28 at 00:16 +0200, Rakotomandimby (R12y) Mihamina wrote:
>> > > I wonder what happen to my CPS...
>> > Is there any need to re-create the chat room?
>> 
>> Just for the tests, I added another chat room. Not efficient.
>> 
>> If I suppress the CPSChat directory from the Products directory (then
>> stop-start Zope), It disapears from the installable product in the
>> portal_quickinstaller.
>> 
>> If I re-add id to the Products directory, it is installable. I installed
>> a modified version of CPSChat (I also changed other things (I suppressed
>> the displaying of the time+date of each message, just to see if changes
>> take efect)): Niet, nothing changed.
>> 
>> 
> Is it possible that, even though the entry in portal_quickinstaller
> disappears and reappears, the implementation is already in your CPSDefault
> Site and that you will not get a new implementation until you create a new
> CPSDefault Site.  I believe that the file
> someproduct/Extensions/install.py runs when a CPSDefault site is created. 
> Am I correct about that?
> 
> If I am, then you might try creating a new CPSDefault Site and checking
> for your changes in that.
> 
> And, if your changes show up in the new site, maybe there is hope ...
> 
> You might take a look at
> Products/CPSDocument/Extensions/upgrade.py.  It appears to do what you are
> asking for with respect to CPSDocument types and without creating a new
> CPSDefault Site.  Here is a doc string from that file:
> 
> # +++++++++++++++++++++++++++++++++++++++++++++++++++ def
> upgradeDocuments(self):
>     """Upgrade various documents to new portal_types and/or new schemas.
> 
>     Howto use the upgradeDocuments ExternalMethod: - Log into the ZMI as
>     manager
>     - Go to your CPS root directory
>     - Create an External Method with the following parameters:
> 
>     id            : upgradeDocuments
>     title         : Use this method if you upgrade an instance older than
>     CPS 3.2$    Module Name   : CPSDocument.upgrade Function Name :
>     upgradeDocuments
> 
>     - save it
>     - then click on the test tab of this external method """
> # +++++++++++++++++++++++++++++++++++++++++++++++++++
> 
> Or am I just being fooled here?
> 

I got errors:

- global name 'log_key' is not defined

- Traceback (innermost last):

    * Module ZPublisher.Publish, line 101, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 39, in call_object
    * Module Products.ExternalMethod.ExternalMethod, line 225, in __call__
      __traceback_info__: ((<CPSDefaultSite instance at b35964d0>,), {}, None)
    * Module 
/home/mihamina/websites/2/Products/CPSDocument/Extensions/upgrade.py, line 48, 
in upgradeDocuments
    * Module 
/home/mihamina/websites/2/Products/CPSDocument/Extensions/upgrade.py, line 58, 
in modifyPortalType

NameError: global name 'log_key' is not defined

I'm running a today svn version.


-- 
Mirroir de logiciels libres       http://www.etud-orleans.fr
D�veloppement de logiciels libres http://aspo.rktmb.org/activites/developpement
Infogerance de serveur d�di�      http://aspo.rktmb.org/activites/infogerance
(En louant les services de l'ASPO vous luttez contre la fracture numerique)


_______________________________________________
cps-devel mailing list
http://lists.nuxeo.com/mailman/listinfo/cps-devel

Reply via email to