Quantcast

Plone cache purge error

classic Classic list List threaded Threaded
25 messages Options
12
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Plone cache purge error

I'm trying to migrate a Plone 3.1.7 site to a more current version.
When I do so, the migration fails, and I'm told there is a problem
with my installation of CacheFu (which I know has been
replaced/integrated into the Plone 4 core).  I am unable to uninstall
or even disable CacheFu from within the 3.1.7 instance.  I've just
downloaded the latest version of CacheFu, which is now CacheSetup
1.2.1, the package for which no longer includes the dependent pieces
it used to.  So I've also downloaded the latest version of
CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
I have imported the old ZODB database, both of these packages show up
in "Add/Remove Products".  When I then try to install CacheSetup, I
get a cryptic traceback:

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 584,
in installProducts
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 543,
in installProduct
   - __traceback_info__: ('CacheSetup',)
  Module Products.CacheSetup.patch, line 127, in cookResources
  Module Products.CacheSetup.content.cache_tool, line 535, in
manage_purgePageCache
AttributeError: manage_purge

I haven't found any references to this error anywhere and would
appreciate some help in what to do next.

Thanks,
~John

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
Alan Runyan-3 Alan Runyan-3
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

On Wed, Aug 24, 2011 at 1:44 PM, John DeStefano
<[hidden email]> wrote:

> I'm trying to migrate a Plone 3.1.7 site to a more current version.
> When I do so, the migration fails, and I'm told there is a problem
> with my installation of CacheFu (which I know has been
> replaced/integrated into the Plone 4 core).  I am unable to uninstall
> or even disable CacheFu from within the 3.1.7 instance.  I've just
> downloaded the latest version of CacheFu, which is now CacheSetup
> 1.2.1, the package for which no longer includes the dependent pieces
> it used to.  So I've also downloaded the latest version of
> CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
> I have imported the old ZODB database, both of these packages show up
> in "Add/Remove Products".  When I then try to install CacheSetup, I
> get a cryptic traceback:

What is the problem with your installation of CacheFu during
migration?  What is the exception?
I would UNINSTALL CacheFu and then attempt migration but it sounds
like you do not have
CacheFu installed?  What about just putting cachefu and squidtool into
your installation
but DO NOT install them (Add/Remove Products).  And try the migration.

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
Dieter Maurer Dieter Maurer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by deesto
John DeStefano wrote at 2011-8-24 14:44 -0400:

>I'm trying to migrate a Plone 3.1.7 site to a more current version.
>When I do so, the migration fails, and I'm told there is a problem
>with my installation of CacheFu (which I know has been
>replaced/integrated into the Plone 4 core).  I am unable to uninstall
>or even disable CacheFu from within the 3.1.7 instance.  I've just
>downloaded the latest version of CacheFu, which is now CacheSetup
>1.2.1, the package for which no longer includes the dependent pieces
>it used to.  So I've also downloaded the latest version of
>CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
>I have imported the old ZODB database, both of these packages show up
>in "Add/Remove Products".  When I then try to install CacheSetup, I
>get a cryptic traceback:
>
>Traceback (innermost last):
> ...
>  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 543,
>in installProduct
>   - __traceback_info__: ('CacheSetup',)
>  Module Products.CacheSetup.patch, line 127, in cookResources
>  Module Products.CacheSetup.content.cache_tool, line 535, in
>manage_purgePageCache
>AttributeError: manage_purge

Strange (surprising) "AttributeError"s can be caused by
"broken" objects (as they lack their true class with their
typical infrastructure).

Check the ZMI whether you find "broken" objects and ensure, you do not.
Then try again.



--
Dieter

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by Alan Runyan-3
Hi Alan,

On Thu, Aug 25, 2011 at 1:37 AM, Alan Runyan-3 [via Plone]
<[hidden email]> wrote:

> On Wed, Aug 24, 2011 at 1:44 PM, John DeStefano
> <[hidden email]> wrote:
>> I'm trying to migrate a Plone 3.1.7 site to a more current version.
>> When I do so, the migration fails, and I'm told there is a problem
>> with my installation of CacheFu (which I know has been
>> replaced/integrated into the Plone 4 core).  I am unable to uninstall
>> or even disable CacheFu from within the 3.1.7 instance.  I've just
>> downloaded the latest version of CacheFu, which is now CacheSetup
>> 1.2.1, the package for which no longer includes the dependent pieces
>> it used to.  So I've also downloaded the latest version of
>> CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
>> I have imported the old ZODB database, both of these packages show up
>> in "Add/Remove Products".  When I then try to install CacheSetup, I
>> get a cryptic traceback:
> What is the problem with your installation of CacheFu during
> migration?  What is the exception?

The AttributeError reported was "manage_purge"; traceback in original
post.  I've gone through a few levels of code now tracing this back,
and haven't found anything useful yet, aside from some interesting
comments in the caching code ("# This is lame :( ").

> I would UNINSTALL CacheFu and then attempt migration but it sounds
> like you do not have
> CacheFu installed?

CacheFu is installed and activated on the original 3.1.7 site, but I
can't de-activate it (nothing happens when I toggle the on/off option)
and thus can't remove it.

> What about just putting cachefu and squidtool into
> your installation
> but DO NOT install them (Add/Remove Products).  And try the migration.

I get the same error when I place them in the new instance whether I
install them or not.

Thanks,
~John
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by Dieter Maurer
Hi Dieter,

On Thu, Aug 25, 2011 at 5:10 AM, Dieter Maurer [via Plone]
<[hidden email]> wrote:

> John DeStefano wrote at 2011-8-24 14:44 -0400:
>>I'm trying to migrate a Plone 3.1.7 site to a more current version.
>>When I do so, the migration fails, and I'm told there is a problem
>>with my installation of CacheFu (which I know has been
>>replaced/integrated into the Plone 4 core).  I am unable to uninstall
>>or even disable CacheFu from within the 3.1.7 instance.  I've just
>>downloaded the latest version of CacheFu, which is now CacheSetup
>>1.2.1, the package for which no longer includes the dependent pieces
>>it used to.  So I've also downloaded the latest version of
>>CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
>>I have imported the old ZODB database, both of these packages show up
>>in "Add/Remove Products".  When I then try to install CacheSetup, I
>>get a cryptic traceback:
>>
>>Traceback (innermost last):
>> ...
>>  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 543,
>>in installProduct
>>   - __traceback_info__: ('CacheSetup',)
>>  Module Products.CacheSetup.patch, line 127, in cookResources
>>  Module Products.CacheSetup.content.cache_tool, line 535, in
>>manage_purgePageCache
>>AttributeError: manage_purge
> Strange (surprising) "AttributeError"s can be caused by
> "broken" objects (as they lack their true class with their
> typical infrastructure).

Indeed.

> Check the ZMI whether you find "broken" objects and ensure, you do not.
> Then try again.

I did have some broken cache-related objects at the root of the site.
Removing those objects has not affected the outcome.  Rebuilding the
catalog fails with (I assume) a related HTTP cache header error.

~John
Alan Runyan-3 Alan Runyan-3
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by deesto
2011/8/25 deesto <[hidden email]>:

> Hi Alan,
>
> On Thu, Aug 25, 2011 at 1:37 AM, Alan Runyan-3 [via Plone]
> <[hidden email]> wrote:
>> On Wed, Aug 24, 2011 at 1:44 PM, John DeStefano
>> <[hidden email]> wrote:
>>> I'm trying to migrate a Plone 3.1.7 site to a more current version.
>>> When I do so, the migration fails, and I'm told there is a problem
>>> with my installation of CacheFu (which I know has been
>>> replaced/integrated into the Plone 4 core).  I am unable to uninstall
>>> or even disable CacheFu from within the 3.1.7 instance.  I've just
>>> downloaded the latest version of CacheFu, which is now CacheSetup
>>> 1.2.1, the package for which no longer includes the dependent pieces
>>> it used to.  So I've also downloaded the latest version of
>>> CMFSquidTool (1.5.1).  In a clean 3.1.7 "preview" instance, into which
>>> I have imported the old ZODB database, both of these packages show up
>>> in "Add/Remove Products".  When I then try to install CacheSetup, I
>>> get a cryptic traceback:
>> What is the problem with your installation of CacheFu during
>> migration?  What is the exception?
> The AttributeError reported was "manage_purge"; traceback in original
> post.  I've gone through a few levels of code now tracing this back,
> and haven't found anything useful yet, aside from some interesting
> comments in the caching code ("# This is lame :( ").
>
>> I would UNINSTALL CacheFu and then attempt migration but it sounds
>> like you do not have
>> CacheFu installed?
>
> CacheFu is installed and activated on the original 3.1.7 site, but I
> can't de-activate it (nothing happens when I toggle the on/off option)
> and thus can't remove it.

well, it must be throwing a error or something. check the ZMI and
see if anything is broken.

>> What about just putting cachefu and squidtool into
>> your installation
>> but DO NOT install them (Add/Remove Products).  And try the migration.
>
> I get the same error when I place them in the new instance whether I
> install them or not.

so your software on the filesystem is out-of-sync with your database.
start your application in foreground mode and see if it breaks.  this traceback
would probably be very useful.

alan

------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Alan,

On Thu, Aug 25, 2011 at 5:09 PM, Alan Runyan-3 [via Plone]
<[hidden email]> wrote:
>>
>> CacheFu is installed and activated on the original 3.1.7 site, but I
>> can't de-activate it (nothing happens when I toggle the on/off option)
>> and thus can't remove it.
> well, it must be throwing a error or something. check the ZMI and
> see if anything is broken.

It wasn't throwing any error to standard out or the logs (in fact, I
was hoping to get some "print"s into the code to output before the
traceback, but found that I can't without some TAL magic), and I only
saw the tracebacks during certain operations.

>>> What about just putting cachefu and squidtool into
>>> your installation
>>> but DO NOT install them (Add/Remove Products).  And try the migration.
>>
>> I get the same error when I place them in the new instance whether I
>> install them or not.
>
> so your software on the filesystem is out-of-sync with your database.

Well, yes: I'm trying to migrate v3 data to a v4 instance.

> start your application in foreground mode and see if it breaks.  this
> traceback
> would probably be very useful.

Good call:

# ./plonectl fg client1
client1: 2011-08-25 17:14:44 INFO ZServer HTTP server started at Thu
Aug 25 17:14:44 2011
        Hostname: 0.0.0.0
        Port: 8080

2011-08-25 17:14:49 INFO Zope Set effective user to "plone"
2011-08-25 17:14:52 ERROR Application Could not import Products.CacheSetup
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 72, in <module>
    run()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 21, in run
    starter.prepare()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 86, in prepare
    self.startZope()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 259, in startZope
    Zope2.startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/__init__.py",
line 47, in startup
    _startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/App/startup.py",
line 67, in startup
    OFS.Application.import_products()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 583, in import_products
    import_product(product_dir, product_name, raise_exc=debug_mode)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface


So, at the least, there's still something missing from the cache
product I'd downloaded.

~John
Mike Cullerton Mike Cullerton
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Does this help?

http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-zope-2-interfaces

On Aug 25, 2011, at 3:20 PM, deesto wrote:

Hi Alan,

On Thu, Aug 25, 2011 at 5:09 PM, Alan Runyan-3 [via Plone]
<<a href="x-msg://196/user/SendEmail.jtp?type=node&amp;node=6726391&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote:
>>
> start your application in foreground mode and see if it breaks.  this
> traceback
> would probably be very useful.

Good call:

# ./plonectl fg client1
client1: 2011-08-25 17:14:44 INFO ZServer HTTP server started at Thu
Aug 25 17:14:44 2011
        Hostname: 0.0.0.0
        Port: 8080

2011-08-25 17:14:49 INFO Zope Set effective user to "plone"
2011-08-25 17:14:52 ERROR Application Could not import Products.CacheSetup
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 72, in <module>
    run()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 21, in run
    starter.prepare()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 86, in prepare
    self.startZope()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 259, in startZope
    Zope2.startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/__init__.py",
line 47, in startup
    _startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/App/startup.py",
line 67, in startup
    OFS.Application.import_products()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 583, in import_products
    import_product(product_dir, product_name, raise_exc=debug_mode)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface


So, at the least, there's still something missing from the cache
product I'd downloaded.

~John




------------------------------------------------------------------------------
EMC VNX: the world's simplest storage, starting under $10K
The only unified storage solution that offers unified management
Up to 160% more powerful than alternatives and 25% more efficient.
Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
Laurence Rowe Laurence Rowe
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by deesto
deesto wrote
Hi Alan,

On Thu, Aug 25, 2011 at 5:09 PM, Alan Runyan-3 [via Plone]
<[hidden email]> wrote:
>>
>> CacheFu is installed and activated on the original 3.1.7 site, but I
>> can't de-activate it (nothing happens when I toggle the on/off option)
>> and thus can't remove it.
> well, it must be throwing a error or something. check the ZMI and
> see if anything is broken.

It wasn't throwing any error to standard out or the logs (in fact, I
was hoping to get some "print"s into the code to output before the
traceback, but found that I can't without some TAL magic), and I only
saw the tracebacks during certain operations.

>>> What about just putting cachefu and squidtool into
>>> your installation
>>> but DO NOT install them (Add/Remove Products).  And try the migration.
>>
>> I get the same error when I place them in the new instance whether I
>> install them or not.
>
> so your software on the filesystem is out-of-sync with your database.

Well, yes: I'm trying to migrate v3 data to a v4 instance.

> start your application in foreground mode and see if it breaks.  this
> traceback
> would probably be very useful.

Good call:

# ./plonectl fg client1
client1: 2011-08-25 17:14:44 INFO ZServer HTTP server started at Thu
Aug 25 17:14:44 2011
        Hostname: 0.0.0.0
        Port: 8080

2011-08-25 17:14:49 INFO Zope Set effective user to "plone"
2011-08-25 17:14:52 ERROR Application Could not import Products.CacheSetup
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 72, in <module>
    run()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 21, in run
    starter.prepare()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 86, in prepare
    self.startZope()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 259, in startZope
    Zope2.startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/__init__.py",
line 47, in startup
    _startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/App/startup.py",
line 67, in startup
    OFS.Application.import_products()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 583, in import_products
    import_product(product_dir, product_name, raise_exc=debug_mode)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 1, in <module>
    import cache_tool, caching_policy_manager
  File "/var/plone4/zeocluster/products/CacheSetup/content/cache_tool.py",
line 51, in <module>
    from Products.CacheSetup.interfaces import ICacheTool
  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
line 2, in <module>
    from Interface import Interface as OldInterface
ImportError: No module named Interface


So, at the least, there's still something missing from the cache
product I'd downloaded.
The problem is that you are trying to use an ancient version of CacheFu under Plone4. You need to remove it from your products folder and, if you did not uninstall it from the add-ons control panel before you upgraded, you need to add Products.CacheSetup to your buildout - the latest version will at least start and uninstall under Plone4 though it won't actually do anything.

Laurence
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Laurence,

On Thu, Aug 25, 2011 at 5:43 PM, Laurence Rowe [via Plone]
<[hidden email]> wrote:

> The problem is that you are trying to use an ancient version of CacheFu
> under Plone4.

I do have an old version installed in my v3 production instance, but
that is merely because I can't remove or even disable it.  In this
Plone 4 instance I'm trying to migrate to, I had downloaded the most
recent tarball version of CacheSetup (1.2.1) and decompressed it in
the products folder.  The error I included in my initial post came
from trying to install this version via Plone/ZMI in the new instance.

> You need to remove it from your products folder and, if you
> did not uninstall it from the add-ons control panel before you upgraded, you
> need to add Products.CacheSetup to your buildout - the latest version will
> at least start and uninstall under Plone4 though it won't actually do
> anything.

I've had to use the tarball, as I'm behind a proxy and buildout fails
to pull packages, even with 'http_proxy' set; I believe this is due to
a urllib issue.  I don't see an .egg package to download manually
among the listed downloads:
http://pypi.python.org/pypi/Products.CacheSetup#downloads

~John
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by Mike Cullerton
Hi Michael,

On Thu, Aug 25, 2011 at 6:08 PM, Michael Cullerton [via Plone]
<[hidden email]> wrote:
> Does this help?
> http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-zope-2-interfaces

It might, but where would I look for this interface type?  I would
think this wouldn't apply, as I'm trying to install the latest version
of the product in Plone 4 in an attempt to upgrade a Plone 3 site
instance to v4.  I see no reference to this type of call in the client
logs, but perhaps that's not the proper place to look.

Thanks,
~John
Mike Cullerton Mike Cullerton
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

John,

I just searched for your error on Google.

From looking at your error message

  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py", 
line 2, in <module> 
    from Interface import Interface as OldInterface 
ImportError: No module named Interface 

I'd say look for a string at line 2 in interfaces.py that says "from Interface import Interface as OldInterface"

and according to the web page I referenced, change it to "from zope.interface import Interface as OldInterface" 

Good luck,
Mike

On Aug 30, 2011, at 9:45 AM, deesto wrote:

Hi Michael,

On Thu, Aug 25, 2011 at 6:08 PM, Michael Cullerton [via Plone]
<<a href="x-msg://148/user/SendEmail.jtp?type=node&amp;node=6742684&amp;i=0" target="_top" rel="nofollow" link="external">[hidden email]> wrote:
> Does this help?
> http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-zope-2-interfaces

It might, but where would I look for this interface type?  I would
think this wouldn't apply, as I'm trying to install the latest version
of the product in Plone 4 in an attempt to upgrade a Plone 3 site
instance to v4.  I see no reference to this type of call in the client
logs, but perhaps that's not the proper place to look.

Thanks,
~John


View this message in context: Re: Plone cache purge error
Sent from the General Questions mailing list archive at Nabble.com.
------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users


------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Mike,

On Tue, Aug 30, 2011 at 1:59 PM, Mike Cullerton [via Plone]
<[hidden email]> wrote:

> John,
> I just searched for your error on Google.
> From looking at your error message
>
>   File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
> line 2, in <module>
>     from Interface import Interface as OldInterface
> ImportError: No module named Interface
>
> I'd say look for a string at line 2 in interfaces.py that says "from
> Interface import Interface as OldInterface"
> and according to the web page I referenced, change it to "from
> zope.interface import Interface as OldInterface"
> Good luck,
> Mike

Thanks.  Good advice.  But I knew it seemed too simple a solution!
After changing the import:

# bin/client1 fg

2011-08-30 15:57:24 INFO ZServer HTTP server started at Tue Aug 30 15:57:24 2011
        Hostname: 0.0.0.0
        Port: 8080
2011-08-30 15:57:24 INFO Zope Set effective user to "plone"
2011-08-30 15:57:25 ERROR Application Could not import Products.CacheSetup
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 2, in <module>
    import policy_folder
  File "/var/plone4/zeocluster/products/CacheSetup/content/policy_folder.py",
line 25, in <module>
    class CachePolicy(NoCatalog, OrderedBaseFolder):
  File "/var/plone4/zeocluster/products/CacheSetup/content/policy_folder.py",
line 28, in CachePolicy
    __implements__ = (OrderedBaseFolder.__implements__, ICachePolicy)
AttributeError: type object 'OrderedBaseFolder' has no attribute
'__implements__'
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 72, in <module>
    run()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/run.py",
line 21, in run
    starter.prepare()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 86, in prepare
    self.startZope()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/Startup/__init__.py",
line 259, in startZope
    Zope2.startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/__init__.py",
line 47, in startup
    _startup()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Zope2/App/startup.py",
line 67, in startup
    OFS.Application.import_products()
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 583, in import_products
    import_product(product_dir, product_name, raise_exc=debug_mode)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/Application.py",
line 606, in import_product
    product=__import__(pname, global_dict, global_dict, silly)
  File "/var/plone4/zeocluster/products/CacheSetup/__init__.py", line
10, in <module>
    from content import *
  File "/var/plone4/zeocluster/products/CacheSetup/content/__init__.py",
line 2, in <module>
    import policy_folder
  File "/var/plone4/zeocluster/products/CacheSetup/content/policy_folder.py",
line 25, in <module>
    class CachePolicy(NoCatalog, OrderedBaseFolder):
  File "/var/plone4/zeocluster/products/CacheSetup/content/policy_folder.py",
line 28, in CachePolicy
    __implements__ = (OrderedBaseFolder.__implements__, ICachePolicy)
AttributeError: type object 'OrderedBaseFolder' has no attribute
'__implements__'


Any other thoughts?  other than going into all of the modules and
manually changing all `__implements__` calls, which seems like a bad
idea?  I tried doing just that, and ended up with a vocabulary error,
which I traced back to here:
http://plone.org/products/ploneboard/issues/219

After a manual fix for that import call, a debug start-up looked
great, until I tried to actually view anything, at which point things
blew up: see below.

Thanks,
~John

===========

Traceback (innermost last):
  Module ZPublisher.Publish, line 126, in publish
  Module ZPublisher.mapply, line 77, in mapply
  Module ZPublisher.Publish, line 46, in call_object
  Module Shared.DC.Scripts.Bindings, line 322, in __call__
  Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec
  Module Products.CMFCore.FSPageTemplate, line 240, in _exec
  Module Products.CacheSetup.patch_cmf, line 29, in FSPT_pt_render
  Module Products.CacheSetup.patch_utils, line 9, in call_pattern
  Module Products.CMFCore.FSPageTemplate, line 180, in pt_render
  Module Products.CacheSetup.patch_cmf, line 77, in PT_pt_render
  Module Products.CacheSetup.patch_utils, line 9, in call_pattern
  Module Products.PageTemplates.PageTemplate, line 79, in pt_render
  Module zope.pagetemplate.pagetemplate, line 113, in pt_render
  Module zope.tal.talinterpreter, line 271, in __call__
  Module zope.tal.talinterpreter, line 343, in interpret
  Module zope.tal.talinterpreter, line 888, in do_useMacro
  Module zope.tal.talinterpreter, line 343, in interpret
  Module zope.tal.talinterpreter, line 533, in do_optTag_tal
  Module zope.tal.talinterpreter, line 518, in do_optTag
  Module zope.tal.talinterpreter, line 513, in no_tag
  Module zope.tal.talinterpreter, line 343, in interpret
  Module zope.tal.talinterpreter, line 888, in do_useMacro
  Module zope.tal.talinterpreter, line 343, in interpret
  Module zope.tal.talinterpreter, line 533, in do_optTag_tal
  Module zope.tal.talinterpreter, line 518, in do_optTag
  Module zope.tal.talinterpreter, line 513, in no_tag
  Module zope.tal.talinterpreter, line 343, in interpret
  Module zope.tal.talinterpreter, line 583, in do_setLocal_tal
  Module zope.tales.tales, line 696, in evaluate
   - URL: file:/var/plone4/zeocluster/products/CacheSetup/skins/cache_setup/global_cache_settings.pt
   - Line 2, Column 4
   - Expression: <PythonExpr
request.RESPONSE.setHeader('Content-Type', 'text/html;charset=%s' %
charset)>
   - Names:
      {'container': <PloneSite at /my-site>,
       'context': <ATDocument at /my-site/front-page>,
       'default': <object object at 0x7f0195aaab20>,
       'here': <ATDocument at /my-site/front-page>,
       'loop': {},
       'nothing': None,
       'options': {'args': ()},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping
object at 0x7c772b8>,
       'request': <HTTPRequest,
URL=http://localhost:8080/my-site/front-page/document_view>,
       'root': <Application at >,
       'template': <FSPageTemplate at /my-site/document_view used for
/my-site/front-page>,
       'traverse_subpath': [],
       'user': <PropertiedUser 'admin'>}
  Module Products.PageTemplates.ZRPythonExpr, line 48, in __call__
   - __traceback_info__: request.RESPONSE.setHeader('Content-Type',
'text/html;charset=%s' % charset)
  Module PythonExpr, line 1, in <expression>
NameError: name 'charset' is not defined
------
2011-08-30T16:15:57 ERROR root Exception while rendering an error message
Traceback (most recent call last):
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/OFS/SimpleItem.py",
line 241, in raise_standardErrorMessage
    v = s(**kwargs)
  File "/var/plone4/buildout-cache/eggs/Products.CMFCore-2.2.4-py2.6.egg/Products/CMFCore/FSPythonScript.py",
line 130, in __call__
    return Script.__call__(self, *args, **kw)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Shared/DC/Scripts/Bindings.py",
line 322, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Shared/DC/Scripts/Bindings.py",
line 359, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone4/buildout-cache/eggs/Products.PythonScripts-2.13.0-py2.6.egg/Products/PythonScripts/PythonScript.py",
line 344, in _exec
    result = f(*args, **kw)
  File "Script (Python)", line 34, in standard_error_message
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Shared/DC/Scripts/Bindings.py",
line 322, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Shared/DC/Scripts/Bindings.py",
line 359, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone4/buildout-cache/eggs/Products.CMFCore-2.2.4-py2.6.egg/Products/CMFCore/FSPageTemplate.py",
line 240, in _exec
    result = self.pt_render(extra_context=bound_names)
  File "/var/plone4/zeocluster/products/CacheSetup/patch_cmf.py", line
29, in FSPT_pt_render
    return call_pattern(self, 'pt_render',
'__CacheSetup_FSPageTemplate_%s__', source, extra_context)
  File "/var/plone4/zeocluster/products/CacheSetup/patch_utils.py",
line 9, in call_pattern
    return getattr(self, pattern % __name__)(*args, **kw)
  File "/var/plone4/buildout-cache/eggs/Products.CMFCore-2.2.4-py2.6.egg/Products/CMFCore/FSPageTemplate.py",
line 180, in pt_render
    self, source, extra_context
  File "/var/plone4/zeocluster/products/CacheSetup/patch_cmf.py", line
77, in PT_pt_render
    return call_pattern(self, 'pt_render',
'__CacheSetup_PageTemplate_%s__', source, extra_context)
  File "/var/plone4/zeocluster/products/CacheSetup/patch_utils.py",
line 9, in call_pattern
    return getattr(self, pattern % __name__)(*args, **kw)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Products/PageTemplates/PageTemplate.py",
line 79, in pt_render
    showtal=showtal)
  File "/var/plone4/buildout-cache/eggs/zope.pagetemplate-3.5.2-py2.6.egg/zope/pagetemplate/pagetemplate.py",
line 113, in pt_render
    strictinsert=0, sourceAnnotations=sourceAnnotations)()
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 271, in __call__
    self.interpret(self.program)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 343, in interpret
    handlers[opcode](self, args)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 888, in do_useMacro
    self.interpret(macro)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 343, in interpret
    handlers[opcode](self, args)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 533, in do_optTag_tal
    self.do_optTag(stuff)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 518, in do_optTag
    return self.no_tag(start, program)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 513, in no_tag
    self.interpret(program)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 343, in interpret
    handlers[opcode](self, args)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 888, in do_useMacro
    self.interpret(macro)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 343, in interpret
    handlers[opcode](self, args)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 533, in do_optTag_tal
    self.do_optTag(stuff)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 518, in do_optTag
    return self.no_tag(start, program)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 513, in no_tag
    self.interpret(program)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 343, in interpret
    handlers[opcode](self, args)
  File "/var/plone4/buildout-cache/eggs/zope.tal-3.5.2-py2.6.egg/zope/tal/talinterpreter.py",
line 583, in do_setLocal_tal
    self.engine.setLocal(name, self.engine.evaluateValue(expr))
  File "/var/plone4/buildout-cache/eggs/zope.tales-3.5.1-py2.6.egg/zope/tales/tales.py",
line 696, in evaluate
    return expression(self)
  File "/var/plone4/buildout-cache/eggs/Zope2-2.13.8-py2.6.egg/Products/PageTemplates/ZRPythonExpr.py",
line 48, in __call__
    return eval(self._code, vars, {})
  File "PythonExpr", line 1, in <expression>
NameError: name 'charset' is not defined



Thanks,
~John
Dieter Maurer Dieter Maurer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by deesto
deesto wrote at 2011-8-25 14:20 -0700:
> ...
>    from Products.CacheSetup.interfaces import ICacheTool
>  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
>line 2, in <module>
>    from Interface import Interface as OldInterface
>ImportError: No module named Interface

I give Lawrence right. This "CacheSetup" seems old -- and has no chance
to work under Plone 4 (in fact a Zope version above Zope 2.11.x for some "x").

"Interface" is the old Zope [2] interface implementation.
Tres Seaver ripped it out of some Zope 2.11.x version as it has caused
several problems very difficult to analyse.


If you are sure that the above "CacheSetup" is current, then this
would mean "CacheSetup" no longer works with Plone 4 (which uses
Zope 2.12). In this case, the easiest approach would be to cleanly uninstall
"CacheSetup/CacheFu" in your Plone 3 instance before you migrate to Plone 4.
Hopefully, the uninstall would delete all objects depending on the package.

Otherwise, you could try again with a current version (but uninstalling
before migration may still be a better option).



--
Dieter

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Dieter,

On Wed, Aug 31, 2011 at 2:10 AM, Dieter Maurer [via Plone]
<[hidden email]> wrote:

> deesto wrote at 2011-8-25 14:20 -0700:
>> ...
>>    from Products.CacheSetup.interfaces import ICacheTool
>>  File "/var/plone4/zeocluster/products/CacheSetup/interfaces.py",
>>line 2, in <module>
>>    from Interface import Interface as OldInterface
>>ImportError: No module named Interface
>
> I give Lawrence right. This "CacheSetup" seems old -- and has no chance
> to work under Plone 4 (in fact a Zope version above Zope 2.11.x for some
> "x").
>
> "Interface" is the old Zope [2] interface implementation.
> Tres Seaver ripped it out of some Zope 2.11.x version as it has caused
> several problems very difficult to analyse.
>
>
> If you are sure that the above "CacheSetup" is current, then this
> would mean "CacheSetup" no longer works with Plone 4 (which uses
> Zope 2.12).

The version I've added to the Plone 4 instance is the latest available
tarball on PyPi (1.2.1).

> In this case, the easiest approach would be to cleanly uninstall
> "CacheSetup/CacheFu" in your Plone 3 instance before you migrate to Plone 4.
> Hopefully, the uninstall would delete all objects depending on the package.

I assumed so.  But as I'd mentioned in my original post, and in
previous attempts, I am unable to uninstall or even disable CacheFu
from within the 3.1.7 instance.  Toggling the "Enable CacheFu" box in
the existing Cache Configuration Tool and clicking "Save" results in a
traceback [1].

> Otherwise, you could try again with a current version (but uninstalling
> before migration may still be a better option).

I've tried this several times now.  At least at this point, after
hacking the CacheSetup scripts to use modern interface implementation
calls, I get a different error than before after migration attempts
(NameError: name 'charset' is not defined).

Does this mean that the step in the migration/upgrade tool labeled
"Uninstall a broken CacheFu" isn't really doing something that it
claims to have done ("Ran upgrade step: Uninstall a broken CacheFu")?

Thanks,
~John


[1] Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFFormController.FSControllerPageTemplate, line 90,
in __call__
  Module Products.CMFFormController.BaseControllerPageTemplate, line
28, in _call
  Module Products.CMFFormController.ControllerBase, line 231, in getNext
  Module Products.CMFFormController.Actions.TraverseTo, line 38, in __call__
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFFormController.FSControllerPythonScript, line
104, in __call__
  Module Products.CMFFormController.Script, line 145, in __call__
  Module Products.CMFCore.FSPythonScript, line 140, in __call__
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.CMFCore.FSPythonScript, line 196, in _exec
  Module None, line 1, in content_edit
   - <FSControllerPythonScript at /my-site/content_edit used for
/my-site/portal_cache_settings>
   - Line 1
  Module Products.CMFCore.FSPythonScript, line 140, in __call__
  Module Shared.DC.Scripts.Bindings, line 313, in __call__
  Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
  Module Products.CMFCore.FSPythonScript, line 196, in _exec
  Module None, line 13, in content_edit_impl
   - <FSPythonScript at /my-site/content_edit_impl used for
/my-site/portal_cache_settings>
   - Line 13
  Module Products.Archetypes.BaseObject, line 661, in processForm
  Module Products.Archetypes.BaseObject, line 651, in _processForm
   - __traceback_info__: (<CacheTool at
/my-site/portal_cache_settings>, <Field enabled(boolean:rw)>, <bound
method CacheTool.setEnabled of <CacheTool at
/my-site/portal_cache_settings>>)
  Module Products.Archetypes.utils, line 162, in mapply
  Module Products.CacheSetup.content.cache_tool, line 242, in setEnabled
  Module Products.CacheSetup.enabler, line 28, in enableCacheFu
  Module Products.CacheSetup.enabler, line 91, in restoreCachingPolicyManager
AttributeError: caching_policy_manager
Dieter Maurer Dieter Maurer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

deesto wrote at 2011-8-31 08:56 -0700:

> ...
>> Otherwise, you could try again with a current version (but uninstalling
>> before migration may still be a better option).
>
>I've tried this several times now.  At least at this point, after
>hacking the CacheSetup scripts to use modern interface implementation
>calls, I get a different error than before after migration attempts
>(NameError: name 'charset' is not defined).
>
>Does this mean that the step in the migration/upgrade tool labeled
>"Uninstall a broken CacheFu" isn't really doing something that it
>claims to have done ("Ran upgrade step: Uninstall a broken CacheFu")?

Obviously, something went wrong. I cannot tell you what this was.


To my belief, the most promising approach is to get "CacheFu" cleanly
deinstalled in your old instance -- then migrate.

We may need to concentrate on resolving the problems assiciated
with this approach.


An alternative approach -- though I am not sure
that it will work.

The base idea: apparently, your migrated Plone site has a significant
problem. Thus, start with a fresh one and "import" your old site's
specifics.

These specifics include at least the site's content. You could try
one of the several export/import mechanisms.
Unfortunately, between Plone 3 and Plone 4 the folder implementation
changed significantly. I am not sure whether Plone 3 folders still
work under Plone 4 without an explicite migration. Therefore,
the ZMI export/import (or equivalently, the Zope "Copy&Paste") may
not be enought to get the old folders work in Plone 4.
Archetypes based export/import or WebDAV based copy are alternatives
you could try.

"GenericSetup" export/import could help you to get most of your
old site's configuration into the new site. However, the import might
destroy new important configuration.

Due to these expected difficulties, I believe that getting
rid of "CacheFu" in the old instance is more promising.

> ....
>
>Thanks,
>~John
>
>
>[1] Traceback (innermost last):
> ...
>   - <FSPythonScript at /my-site/content_edit_impl used for
>/my-site/portal_cache_settings>
>   - Line 13
>  Module Products.Archetypes.BaseObject, line 661, in processForm
>  Module Products.Archetypes.BaseObject, line 651, in _processForm
>   - __traceback_info__: (<CacheTool at
>/my-site/portal_cache_settings>, <Field enabled(boolean:rw)>, <bound
>method CacheTool.setEnabled of <CacheTool at
>/my-site/portal_cache_settings>>)
>  Module Products.Archetypes.utils, line 162, in mapply
>  Module Products.CacheSetup.content.cache_tool, line 242, in setEnabled
>  Module Products.CacheSetup.enabler, line 28, in enableCacheFu
>  Module Products.CacheSetup.enabler, line 91, in restoreCachingPolicyManager
>AttributeError: caching_policy_manager

Why do you want to enable "CacheFu"?
I think that you should want to get rid of it.



--
Dieter

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Dieter,

On Mon, Sep 5, 2011 at 3:18 AM, Dieter Maurer [via Plone]

>>Does this mean that the step in the migration/upgrade tool labeled
>>"Uninstall a broken CacheFu" isn't really doing something that it
>>claims to have done ("Ran upgrade step: Uninstall a broken CacheFu")?
> Obviously, something went wrong. I cannot tell you what this was.
>
>
> To my belief, the most promising approach is to get "CacheFu" cleanly
> deinstalled in your old instance -- then migrate.
>
> We may need to concentrate on resolving the problems assiciated
> with this approach.

I agree.  Details of my latest attempts at the end of this message.

> An alternative approach -- though I am not sure
> that it will work.
>
> The base idea: apparently, your migrated Plone site has a significant
> problem. Thus, start with a fresh one and "import" your old site's
> specifics.
>
> These specifics include at least the site's content. You could try
> one of the several export/import mechanisms.
> Unfortunately, between Plone 3 and Plone 4 the folder implementation
> changed significantly. I am not sure whether Plone 3 folders still
> work under Plone 4 without an explicite migration. Therefore,
> the ZMI export/import (or equivalently, the Zope "Copy&Paste") may
> not be enought to get the old folders work in Plone 4.
> Archetypes based export/import or WebDAV based copy are alternatives
> you could try.
>
> "GenericSetup" export/import could help you to get most of your
> old site's configuration into the new site. However, the import might
> destroy new important configuration.
>
> Due to these expected difficulties, I believe that getting
> rid of "CacheFu" in the old instance is more promising.

Yes, I have tried exporting objects from one instance to another, as
well as just a copy of the old content and paste into a new site on
the same instance, and all attempts fail.  Let me know if you have any
ideas on pursuing this further.

> Why do you want to enable "CacheFu"?
> I think that you should want to get rid of it.

That was just one of many attempts to get anything to work.

Here are the in-depth results of my latest attempts:

If I take the existing 3.1.7 Plone instance, add the latest available
version of CacheSetup (and Squid) to Products on the file system, and
try to uninstall the existing CacheSetup 1.1 via Add/Remove Products
in Plone, I get a traceback within Plone:

Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module <string>, line 4, in _facade
  Module AccessControl.requestmethod, line 64, in _curried
  Module Products.CMFQuickInstallerTool.QuickInstallerTool, line 621,
in uninstallProducts
  Module Products.CMFQuickInstallerTool.InstalledProduct, line 288, in uninstall
  Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
   - __traceback_info__: ((<PloneSite at /my-site>,), {'reinstall':
False}, (False,))
  Module /var/plone/zeocluster/client1/Products/CacheSetup/Extensions/Install.py,
line 67, in uninstall
  Module Products.CacheSetup.enabler, line 34, in enableCacheFu
  Module Products.CacheSetup.enabler, line 97, in restoreCachingPolicyManager
AttributeError: caching_policy_manager


If I first re-install CacheSetup to bring it up to version 1.2.1, and
then try to uninstall CacheSetup 1.2.1, I get a ZMI traceback:
Traceback (innermost last):
    * Module ZPublisher.Publish, line 202, in publish_module_standard
    * Module ZPublisher.Publish, line 150, in publish
    * Module plone.app.linkintegrity.monkey, line 21, in
zpublisher_exception_hook_wrapper
    * Module Zope2.App.startup, line 221, in zpublisher_exception_hook
    * Module ZPublisher.Publish, line 119, in publish
    * Module ZPublisher.mapply, line 88, in mapply
    * Module ZPublisher.Publish, line 42, in call_object
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPageTemplate, line 216, in _exec
    * Module Products.CacheSetup.patch_cmf, line 29, in FSPT_pt_render
    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
    * Module Products.CMFCore.FSPageTemplate, line 155, in pt_render
    * Module Products.CacheSetup.patch_cmf, line 77, in PT_pt_render
    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
    * Module Products.PageTemplates.PageTemplate, line 89, in pt_render
    * Module zope.pagetemplate.pagetemplate, line 117, in pt_render
    * Module zope.tal.talinterpreter, line 271, in __call__
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 891, in do_useMacro
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 891, in do_useMacro
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 891, in do_useMacro
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 536, in do_optTag_tal
    * Module zope.tal.talinterpreter, line 521, in do_optTag
    * Module zope.tal.talinterpreter, line 516, in no_tag
    * Module zope.tal.talinterpreter, line 346, in interpret
    * Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
    * Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
    * Module zope.tales.tales, line 696, in evaluate
      URL: file:/var/plone/zeocluster/client1/Products/CacheSetup/skins/cache_setup/global_cache_settings.pt
      Line 5, Column 4
      Expression: <PythonExpr
here.enableHTTPCompression(request=request, debug=0)>
      Names:
      {'container': <PloneSite at /my-site>,
       'context': <PloneSite at /my-site>,
       'default': <object object at 0xf775d528>,
       'here': <PloneSite at /my-site>,
       'loop': {},
       'nothing': None,
       'options': {'args': ()},
       'repeat': <Products.PageTemplates.Expressions.SafeMapping
object at 0xe550392c>,
       'request': <HTTPRequest,
URL=http://localhost:8080/my-site/prefs_install_products_form>,
       'root': <Application at >,
       'template': <FSPageTemplate at /my-site/prefs_install_products_form>,
       'traverse_subpath': [],
       'user': <PropertiedUser 'admin'>}

    * Module Products.PageTemplates.ZRPythonExpr, line 49, in __call__
      __traceback_info__: here.enableHTTPCompression(request=request, debug=0)
    * Module PythonExpr, line 1, in <expression>
    * Module Products.CMFCore.FSPythonScript, line 140, in __call__
    * Module Shared.DC.Scripts.Bindings, line 313, in __call__
    * Module Shared.DC.Scripts.Bindings, line 350, in _bindAndExec
    * Module Products.CMFCore.FSPythonScript, line 196, in _exec
    * Module None, line 10, in enableHTTPCompression
      <FSPythonScript at /my-site/enableHTTPCompression>
      Line 10
AttributeError: portal_cache_settings (Also, the following error
occurred while attempting to render the standard error message, please
see the event log for full details: portal_cache_settings)

From that point on, I could no longer view any site content without a
similar error.

In the site's portal_quickinstaller, CacheSetup (v1.2.1) and
CMFSquidTool (1.5.1) both appeared under Installable Products;
however, under Installed Products,  CMFSquidTool (1.0) remained as the
sole entry.

I then removed from ZMI Control_Panel/Products:
CacheSetup (Installed product CacheSetup (1.2.1)) 2011-09-12 14:26
Product
CMFSquidTool (Installed product CMFSquidTool (1.5.1)) 2011-09-12 14:26
PageCacheManager (Installed product PageCacheManager (1.0.2
(SVN/UNRELEASED))) 2007-05-22 14:40
PolicyHTTPCacheManager (Installed product PolicyHTTPCacheManager
(1.0.0)) 2006-09-25 11:57
StandardCacheManagers (Installed product StandardCacheManagers
(StandardCacheManagers-1-1-0))

And removed from site's portal_quickinstaller contents:
CacheSetup
CMFSquidTool
Product.CMFSquidTool

I did a zope restart, and all the above removed products were
returned, with the same results on viewing the site.

~John
Dieter Maurer Dieter Maurer
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

deesto wrote at 2011-9-12 12:00 -0700:

> ...
>If I take the existing 3.1.7 Plone instance, add the latest available
>version of CacheSetup (and Squid) to Products on the file system, and
>try to uninstall the existing CacheSetup 1.1 via Add/Remove Products
>in Plone, I get a traceback within Plone:
>
>Traceback (innermost last):
> ...
>  Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
>   - __traceback_info__: ((<PloneSite at /my-site>,), {'reinstall':
>False}, (False,))
>  Module /var/plone/zeocluster/client1/Products/CacheSetup/Extensions/Install.py,
>line 67, in uninstall
>  Module Products.CacheSetup.enabler, line 34, in enableCacheFu
>  Module Products.CacheSetup.enabler, line 97, in restoreCachingPolicyManager
>AttributeError: caching_policy_manager

Check where (on what object) "restoreCachingPolicyManger" looks
for the "caching_policy_manager".

I expect that the "Products.CacheSetup" you are currently trying
does not correspond to the ZODB content of your site.
The code seems to expect that during installation, a copy
of "caching_policy_manager" has been saved, but the ZODB object seems
to lack it.

As a workaround, you could make "restoreCachingPolicyManager"
a no operation (let it immediately return) and delete/create the
"caching_policy_manager" manually (or create via "GenericSetup").


>If I first re-install CacheSetup to bring it up to version 1.2.1, and
>then try to uninstall CacheSetup 1.2.1, I get a ZMI traceback:

Try to use the old "Products.CacheSetup" -- the same version you
have used all along (you are still working in your old instance environment,
aren't you?). Do not try a new "CacheSetup" version.

Use your original instance (including the original "Products.CacheSetup")
to uninstall "CacheSetup" from your portal.

Report any problem that occurs thereby.


>Traceback (innermost last):
> ...
>    * Module Products.CacheSetup.patch_cmf, line 29, in FSPT_pt_render
>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>    * Module Products.CMFCore.FSPageTemplate, line 155, in pt_render
>    * Module Products.CacheSetup.patch_cmf, line 77, in PT_pt_render
>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>    * Module Products.PageTemplates.PageTemplate, line 89, in pt_render
> ...
>    * Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
>    * Module Products.PageTemplates.Expressions, line 221, in evaluateStructure
>    * Module zope.tales.tales, line 696, in evaluate
>      URL: file:/var/plone/zeocluster/client1/Products/CacheSetup/skins/cache_setup/global_cache_settings.pt
>      Line 5, Column 4
>      Expression: <PythonExpr
> ...
>    * Module None, line 10, in enableHTTPCompression
>      <FSPythonScript at /my-site/enableHTTPCompression>
>      Line 10
>AttributeError: portal_cache_settings

Maybe a bug in the uninstallation code (or some version problem).

Apparently, "Products.CacheSetup" has added one or more layers
to the "portal_skins" skin. Uninstallation may then pose non trivial
phasing requirements.
For your traceback, I guess that the "enableHTTPCompression" above
comes from "Products.CacheSetup" and expects an object "portal_cache_settings"
(belonging to "Products.CacheSetup"). After "portal_cache_settings"
is uninstalled, the above "enableHTTPCompression" can no longer be used
but apparently is yet.

As a workaround measure: locate the source of the above script
and comment out all code referencing "Products.CacheSetup" objects.
If necessary, let it return immediately (you will lose http compression -
but that is only an optimization).

>>From that point on, I could no longer view any site content without a
>similar error.

Looks as if the uninstallation forgot to remove the
"Products.CacheSetup" introduced skin layers.

Patch the problematic "enableHTTPCompression" script (as sketched above)
and then remove (manually) all references to layers defined by
"Products.CacheSetup" under "portal_skins" ("Properties" tab).


It is important for me that our discussion remains on the list.

However, you may include me on "CC:" on your followups.
This probably will drastically improve my response speed: I
read the list digest, delivered only once or twice a week;
in consequence, without the "CC:", you will get a response from me only once
or twice a week. With me on "CC:", you can expect a response within one
or two days.


--
Dieter

------------------------------------------------------------------------------
Doing More with Less: The Next Generation Virtual Desktop
What are the key obstacles that have prevented many mid-market businesses
from deploying virtual desktops?   How do next-generation virtual desktops
provide companies an easier-to-deploy, easier-to-manage and more affordable
virtual desktop model.http://www.accelacomm.com/jaw/sfnl/114/51426474/
_______________________________________________
Plone-Users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/plone-users
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

Hi Dieter,

Before going through your suggestions below, I tried to clean up the
existing instance as best as possible.  What can I do about these
problems I see in debug mode as I poke through the site:

- This error occurs in portal_quickinstallier, although this product
has already been removed from the instance, and the file system
directories removed, it's still hiding somewhere:
2011-09-16 10:25:52 WARNING OFS.Uninstalled Could not import class
'WindowZTool' from module 'Products.windowZ.WindowZTool'

- These warnings occur when viewing portal_skins; I can confirm that
the called paths don't exist but not sure how to fix them:
/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
UserWarning: DirectoryView plone_tableless refers to a non-existing
path 'CMFPlone/skins/plone_tableless'
  (self.id, reg_key), UserWarning)
/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
UserWarning: DirectoryView cache_prefs_plone20 refers to a
non-existing path 'CacheSetup/skins/cache_prefs_plone20'
  (self.id, reg_key), UserWarning)
/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
UserWarning: DirectoryView cache_setup_globals refers to a
non-existing path 'CacheSetup/skins/cache_setup_globals'
  (self.id, reg_key), UserWarning)

- These are called from portal_transforms (and catalog rebuilds); none
of them are listed there, and some refer to a product that has long
since been removed:
2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
lynx_dump, using BrokenTransform: Error
 Unable to find binary "lynx" in
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
text_to_emoticons (ImportError), using BrokenTransform: Error
 No module named Ploneboard.transforms.text_to_emoticons
2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
url_to_hyperlink (ImportError), using BrokenTransform: Error
 No module named Ploneboard.transforms.url_to_hyperlink

I also see references to previously removed product classes when
viewing the root ZMI:
WARNING OFS.Uninstalled Could not import class 'Someproduct' from
module 'Products.Someproduct'
^ These are removed everywhere I could find them, including the file
system, so I assume they're cached somewhere.  But I've rebuilt the
catalog, compacted the database to 0 days, and flushed the database
cache.

- Several errors such as these are returned while performing a catalog
clear and rebuild, which completes but takes some time:
2011-09-16 10:27:22 INFO Archetypes
Products/Archetypes/Field.py[1207]:getIndexable
Error while trying to convert file contents to 'text/plain' in <Field
file(file:rw)>.getIndexable() of <ATFile at /site/some-path/some.doc>:
Unable to find binary "wvHtml" in
/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin

^ I can fix that one by installing `wv` (and its dependent `libgsf`),
but just wondering why that's necessary if it's not a prerequisite for
Plone.

At this point, a zope client debug start-up is relatively clean, save
for 'Marshall libxml2-python not available' (which is strange as the
package is installed), multiple deprecation warnings on registry.py
versioning, and the following, which is related to CacheSetup but
seems like only a warning:
/var/plone/zeocluster/client1/Products/CacheSetup/content/base_cache_rule.py:19:
DeprecationWarning: Products.PageTemplates.TALES has moved to
zope.tales.tales. Import of Products.PageTemplates.TALES will become
unsupported in 2.12
  from Products.PageTemplates.TALES import CompilerError


Now, onward with your recommendations ...

On Thu, Sep 15, 2011 at 9:56 AM, Dieter Maurer [via Plone]
<[hidden email]> wrote:

> deesto wrote at 2011-9-12 12:00 -0700:
>> ...
>>If I take the existing 3.1.7 Plone instance, add the latest available
>>version of CacheSetup (and Squid) to Products on the file system, and
>>try to uninstall the existing CacheSetup 1.1 via Add/Remove Products
>>in Plone, I get a traceback within Plone:
>>
>>Traceback (innermost last):
>> ...
>>  Module Products.ExternalMethod.ExternalMethod, line 231, in __call__
>>   - __traceback_info__: ((<PloneSite at /my-site>,), {'reinstall':
>>False}, (False,))
>>  Module
>> /var/plone/zeocluster/client1/Products/CacheSetup/Extensions/Install.py,
>>line 67, in uninstall
>>  Module Products.CacheSetup.enabler, line 34, in enableCacheFu
>>  Module Products.CacheSetup.enabler, line 97, in
>> restoreCachingPolicyManager
>>AttributeError: caching_policy_manager
> Check where (on what object) "restoreCachingPolicyManger" looks
> for the "caching_policy_manager".
>
> I expect that the "Products.CacheSetup" you are currently trying
> does not correspond to the ZODB content of your site.
> The code seems to expect that during installation, a copy
> of "caching_policy_manager" has been saved, but the ZODB object seems
> to lack it.

Your assumption is correct: in the previous migration instance, I had
taken the old stuff and replaced the CacheSetup package with the
latest version.  I've now reverted this instance to use everything
from the old version.

> As a workaround, you could make "restoreCachingPolicyManager"
> a no operation (let it immediately return) and delete/create the
> "caching_policy_manager" manually (or create via "GenericSetup").
>
>
>>If I first re-install CacheSetup to bring it up to version 1.2.1, and
>>then try to uninstall CacheSetup 1.2.1, I get a ZMI traceback:
>
> Try to use the old "Products.CacheSetup" -- the same version you
> have used all along (you are still working in your old instance environment,
> aren't you?). Do not try a new "CacheSetup" version.
>
> Use your original instance (including the original "Products.CacheSetup")
> to uninstall "CacheSetup" from your portal.
>
> Report any problem that occurs thereby.

From [site]/portal_quickinstaller, I uninstall CacheSetup v1.1, and it
seems to work: both CacheSetup and CMFSquidTool are moved from the
list of installed products to the list of those available for install.
 However, moving back to view the Plone site root then throws a
massive traceback, and rebuilding the catalog fails as well.  The site
view traceback is "AttributeError: portal_cache_settings", which I
don't understand since portal_cache_settings got removed from the site
on uninstall.

Also, the base_cache_rule.py warning remains on zope client in debug
startup, but perhaps that's only because I didn't remove the Products
directory after uninstall.  If I remove the directory entirely, all
kinds of things break, and the instance won't start.

In the ZMI site view, all of the content object type entries appear
with a type name (ATFolder, etc.) instead of an icon, and
"AttributeError: portal_cache_settings" is thrown there as well.

>>Traceback (innermost last):
>> ...
>>    * Module Products.CacheSetup.patch_cmf, line 29, in FSPT_pt_render
>>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>>    * Module Products.CMFCore.FSPageTemplate, line 155, in pt_render
>>    * Module Products.CacheSetup.patch_cmf, line 77, in PT_pt_render
>>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>>    * Module Products.PageTemplates.PageTemplate, line 89, in pt_render
>> ...
>>    * Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
>>    * Module Products.PageTemplates.Expressions, line 221, in
>> evaluateStructure
>>    * Module zope.tales.tales, line 696, in evaluate
>>      URL:
>> file:/var/plone/zeocluster/client1/Products/CacheSetup/skins/cache_setup/global_cache_settings.pt
>>      Line 5, Column 4
>>      Expression: <PythonExpr
>> ...
>>    * Module None, line 10, in enableHTTPCompression
>>      <FSPythonScript at /my-site/enableHTTPCompression>
>>      Line 10
>>AttributeError: portal_cache_settings
> Maybe a bug in the uninstallation code (or some version problem).
>
> Apparently, "Products.CacheSetup" has added one or more layers
> to the "portal_skins" skin. Uninstallation may then pose non trivial
> phasing requirements.
> For your traceback, I guess that the "enableHTTPCompression" above
> comes from "Products.CacheSetup" and expects an object
> "portal_cache_settings"
> (belonging to "Products.CacheSetup"). After "portal_cache_settings"
> is uninstalled, the above "enableHTTPCompression" can no longer be used
> but apparently is yet.
>
> As a workaround measure: locate the source of the above script
> and comment out all code referencing "Products.CacheSetup" objects.
> If necessary, let it return immediately (you will lose http compression -
> but that is only an optimization).

OK, which script do you mean here? I assume these files:
CacheSetup/skins/cache_setup/global_cache_settings.pt
CMFPlone/skins/plone_scripts/enableHTTPCompression.py
... which refer to:
CacheSetup/skins/cache_setup/enableHTTPCompression.py

After editing these, I see the same symptoms (AttributeError:
portal_cache_settings, AT type names instead of icons, catalog rebuild
fails, etc.). Also noticed that in [site]/manage_workspace, there are
still CacheSetup "Add" items available to add to the site.

>>>From that point on, I could no longer view any site content without a
>>similar error.
>
> Looks as if the uninstallation forgot to remove the
> "Products.CacheSetup" introduced skin layers.
>
> Patch the problematic "enableHTTPCompression" script (as sketched above)
> and then remove (manually) all references to layers defined by
> "Products.CacheSetup" under "portal_skins" ("Properties" tab).

Removed cache_setup from portal_skins-> Properties, but that hasn't
changed any of the above conditions.  I'll include the current
traceback for viewing site content via ZMI in [1].

> It is important for me that our discussion remains on the list.
>
> However, you may include me on "CC:" on your followups.
> This probably will drastically improve my response speed: I
> read the list digest, delivered only once or twice a week;
> in consequence, without the "CC:", you will get a response from me only once
> or twice a week. With me on "CC:", you can expect a response within one
> or two days.

Understood.  Thanks for your help.

~John

[1]
2011-09-16 14:20:45 ERROR Zope.SiteErrorLog
http://localhost:8080/my-site/folder_icon.gif/index_html
Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFCore.FSImage, line 126, in index_html
  Module Products.CMFCore.utils, line 460, in _setCacheHeaders
  Module Products.CacheSetup.content.caching_policy_manager, line 69,
in getHTTPCachingHeaders
  Module Products.CacheSetup.content.caching_policy_manager, line 54,
in getHeadersToAddAndRemove
  Module Products.CMFCore.utils, line 123, in getToolByName
AttributeError: portal_cache_settings
2011-09-16 14:20:45 ERROR Zope.SiteErrorLog
http://localhost:8080/my-site/document_icon.gif/index_html
Traceback (innermost last):
  Module ZPublisher.Publish, line 119, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 42, in call_object
  Module Products.CMFCore.FSImage, line 126, in index_html
  Module Products.CMFCore.utils, line 460, in _setCacheHeaders
  Module Products.CacheSetup.content.caching_policy_manager, line 69,
in getHTTPCachingHeaders
  Module Products.CacheSetup.content.caching_policy_manager, line 54,
in getHeadersToAddAndRemove
  Module Products.CMFCore.utils, line 123, in getToolByName
AttributeError: portal_cache_settings
2011-09-16 14:20:45 ERROR root Exception while rendering an error message
Traceback (most recent call last):
  File "/var/plone/lib/python/OFS/SimpleItem.py", line 227, in
raise_standardErrorMessage
    v = s(**kwargs)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPythonScript.py",
line 140, in __call__
    return Script.__call__(self, *args, **kw)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
313, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
350, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPythonScript.py",
line 196, in _exec
    result = f(*args, **kw)
  File "Script (Python)", line 34, in standard_error_message
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
313, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
350, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPageTemplate.py",
line 216, in _exec
    result = self.pt_render(extra_context=bound_names)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/patch_cmf.py",
line 28, in FSPT_pt_render
    return call_pattern(self, 'pt_render',
'__CacheSetup_FSPageTemplate_%s__', source, extra_context)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/patch_utils.py",
line 9, in call_pattern
    return getattr(self, pattern % __name__)(*args, **kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPageTemplate.py",
line 159, in pt_render
    _setCacheHeaders(self, extra_context)
  File "/var/plone/zeocluster/client1/Products/CMFCore/utils.py", line
460, in _setCacheHeaders
    headers = manager.getHTTPCachingHeaders(
  File "/var/plone/zeocluster/client1/Products/CacheSetup/content/caching_policy_manager.py",
line 69, in getHTTPCachingHeaders
    hdrs = self.getHeadersToAddAndRemove(content, view_method, keywords, time)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/content/caching_policy_manager.py",
line 54, in getHeadersToAddAndRemove
    pcs = getToolByName(self, CACHE_TOOL_ID)
  File "/var/plone/zeocluster/client1/Products/CMFCore/utils.py", line
123, in getToolByName
    raise AttributeError, name
AttributeError: portal_cache_settings
2011-09-16 14:20:45 ERROR root Exception while rendering an error message
Traceback (most recent call last):
  File "/var/plone/lib/python/OFS/SimpleItem.py", line 227, in
raise_standardErrorMessage
    v = s(**kwargs)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPythonScript.py",
line 140, in __call__
    return Script.__call__(self, *args, **kw)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
313, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
350, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPythonScript.py",
line 196, in _exec
    result = f(*args, **kw)
  File "Script (Python)", line 34, in standard_error_message
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
313, in __call__
    return self._bindAndExec(args, kw, None)
  File "/var/plone/lib/python/Shared/DC/Scripts/Bindings.py", line
350, in _bindAndExec
    return self._exec(bound_data, args, kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPageTemplate.py",
line 216, in _exec
    result = self.pt_render(extra_context=bound_names)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/patch_cmf.py",
line 28, in FSPT_pt_render
    return call_pattern(self, 'pt_render',
'__CacheSetup_FSPageTemplate_%s__', source, extra_context)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/patch_utils.py",
line 9, in call_pattern
    return getattr(self, pattern % __name__)(*args, **kw)
  File "/var/plone/zeocluster/client1/Products/CMFCore/FSPageTemplate.py",
line 159, in pt_render
    _setCacheHeaders(self, extra_context)
  File "/var/plone/zeocluster/client1/Products/CMFCore/utils.py", line
460, in _setCacheHeaders
    headers = manager.getHTTPCachingHeaders(
  File "/var/plone/zeocluster/client1/Products/CacheSetup/content/caching_policy_manager.py",
line 69, in getHTTPCachingHeaders
    hdrs = self.getHeadersToAddAndRemove(content, view_method, keywords, time)
  File "/var/plone/zeocluster/client1/Products/CacheSetup/content/caching_policy_manager.py",
line 54, in getHeadersToAddAndRemove
    pcs = getToolByName(self, CACHE_TOOL_ID)
  File "/var/plone/zeocluster/client1/Products/CMFCore/utils.py", line
123, in getToolByName
    raise AttributeError, name
AttributeError: portal_cache_settings
deesto deesto
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Plone cache purge error

In reply to this post by Dieter Maurer
Hi Dieter,

This is getting a bit unwieldy so I'll try to compress the previous thread:

Regarding portal_skins: I had removed these three entries
(plone_tableless, cache_prefs_plone20, cache_setup_globals) from both
portal_skins's Contents and Properties.  Here's what's left in
portal_skins -> Properties -> Skin Selections -> Layers:

custom
archetypes
archetypes_kss
mimetypes_icons
LanguageTool
cmfeditions_views
CMFEditions
ChangeSet
kupu_references
kupu_plone
kupu
fckeditorplone
fckeditor
kupu_tests
CMFPlacefulWorkflow
PasswordReset
ATContentTypes
ATReferenceBrowserWidget
ResourceRegistries
gruf
plone_ecmascript
plone_wysiwyg
plone_prefs
plone_portlets
plone_templates
plone_styles
plone_form_scripts
plone_scripts
plone_forms
plone_images
plone_content
plone_login
plone_deprecated
plone_3rdParty
cmf_legacy
plone_kss

The only think I could think of was perhaps something about the
'custom' skin, which was comprised of just some changes to base site
properties and a few custom file overrides, contained a references,
but I saw no reference to any "cache" in any of these.

Regarding portal_transforms: I had found some previously broken
transforms in Contents and removed them, but the transforms being
called by these errors are not here presently.  I've done searches
through the file system tree for references, and the only positive
match is always Data.fs itself.

You mention a few times below that I need to locate these objects and
references in the ZODB, but it's not clear to me how to do that; a
simple search via 'Find' always comes up empty for objects containing
these terms.

You also mention that third-party packages can be installed in the OS
to alleviate warnings for transforms, parsing, etc.  But these are
more than just warnings (outright errors in some cases), and I'm
trying to simplify this installation as much as possible; things like
'lynx' and 'wv' are not called out as Plone prerequisites and seem
trivial.  Can I disable these completely somehow instead?

You've asked for several tracebacks, which I had withheld from a few
posts because they seemed redundant with previous errors.  But I
include these in detail here in a log attachment.  Bear in mind that
portal_quickinstaller shows no installed products at this point,
though the aforementioned products are present on the file system for
the sake of compatibility, unless specified otherwise in the logs.
The fact that the site still makes reference to uninstalled products
seems to suggest a problem with those products' uninstallers, as
you've mentioned, but I don't know the work-around.

I think that covers your suggestions; if not, please let me know what
I've missed ...

Thanks,
~John


On Sat, Sep 17, 2011 at 4:42 AM, Dieter Maurer <[hidden email]> wrote:

> John DeStefano wrote at 2011-9-16 14:24 -0400:
>> ...
>>- This error occurs in portal_quickinstallier, although this product
>>has already been removed from the instance, and the file system
>>directories removed, it's still hiding somewhere:
>>2011-09-16 10:25:52 WARNING OFS.Uninstalled Could not import class
>>'WindowZTool' from module 'Products.windowZ.WindowZTool'
>
> This (probably) means that your ZODB still contains an object dependent on
> this product. You would need to locate this object and delete it
> (or reprovide the product code).
>
>
>>- These warnings occur when viewing portal_skins; I can confirm that
>>the called paths don't exist but not sure how to fix them:
>>/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
>>UserWarning: DirectoryView plone_tableless refers to a non-existing
>>path 'CMFPlone/skins/plone_tableless'
>>  (self.id, reg_key), UserWarning)
>>/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
>>UserWarning: DirectoryView cache_prefs_plone20 refers to a
>>non-existing path 'CacheSetup/skins/cache_prefs_plone20'
>>  (self.id, reg_key), UserWarning)
>>/var/plone/zeocluster/client1/Products/CMFCore/DirectoryView.py:497:
>>UserWarning: DirectoryView cache_setup_globals refers to a
>>non-existing path 'CacheSetup/skins/cache_setup_globals'
>>  (self.id, reg_key), UserWarning)
>
> "portal_skins" contains these "DirectoryView"s -- but the corresponding
> filesystem directories do not exist.
>
> Visit the "Contents" tab of "portal_skins" and delete the
> corresponding objects. On the "Contents" page, the "DirectoryView"s
> are listed by their id not by their filepath. But usually, the id
> is chosen sensefully, giving some indication towards the filepath.
> A "broken" "DirectoryView" appears empty and you can verify
> a "DirectoryView"'s filepath in its "Properties" tab.
>
> Keep in mind, that your skins (managed under the "Properties" tab
> of "portal_skins") are likely to contain references to these
> problematic "DirectoryView"s. Remove them as well.
>
>
>>- These are called from portal_transforms (and catalog rebuilds); none
>>of them are listed there, and some refer to a product that has long
>>since been removed:
>>2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
>>lynx_dump, using BrokenTransform: Error
>> Unable to find binary "lynx" in
>>/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>>2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
>>text_to_emoticons (ImportError), using BrokenTransform: Error
>> No module named Ploneboard.transforms.text_to_emoticons
>>2011-09-16 10:26:39 ERROR PortalTransforms Cannot register transform
>>url_to_hyperlink (ImportError), using BrokenTransform: Error
>> No module named Ploneboard.transforms.url_to_hyperlink
>
> The first warning tells you that some transform will not work
> because a prerequisite (the binary "lynx") could not be found.
> To get rid of it, you can install "lynx".
>
> The following warnings tell you that "portal_transforms" has
> information about the mentioned transforms but does not
> find necessary code prerequisites.
> Check, whether the "portal_transforms" object contains ("Contents" tab)
> the mentioned transforms -- and, if so, delete them.
> Otherwise, search the source code tree for references to
> the transforms and get rid of the respective sources.
>
>>I also see references to previously removed product classes when
>>viewing the root ZMI:
>>WARNING OFS.Uninstalled Could not import class 'Someproduct' from
>>module 'Products.Someproduct'
>>^ These are removed everywhere I could find them, including the file
>>system, so I assume they're cached somewhere.
>
> Like in the first case: your ZODB still contains objects
> referencing the mentioned products. You must find and delete them
> or reprovide the respective code.
>
>> But I've rebuilt the
>>catalog, compacted the database to 0 days, and flushed the database
>>cache.
>
> Obviously, you missed some objects in the ZODB which still need to
> get deleted. Unfortunately, it is not easy (in general) to locate those
> objects.
>
> Your approach above (associating the occurrence of the warning with
> the request performed) can give you some hints where to look for them.
> For example: when a problem occurs when visiting "portal_skins", then
> a problem is likely for some child of "portal_skins".
>
>
>>- Several errors such as these are returned while performing a catalog
>>clear and rebuild, which completes but takes some time:
>>2011-09-16 10:27:22 INFO Archetypes
>>Products/Archetypes/Field.py[1207]:getIndexable
>>Error while trying to convert file contents to 'text/plain' in <Field
>>file(file:rw)>.getIndexable() of <ATFile at /site/some-path/some.doc>:
>>Unable to find binary "wvHtml" in
>>/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
>
> A similar problem as for the "lynx_dump" transformation, above.
> Some binary (this time "wvHtml") is not installed. Ensure that
> it is installed and the problem will go away.
>
>>I can fix that one by installing `wv` (and its dependent `libgsf`),
>>but just wondering why that's necessary if it's not a prerequisite for
>>Plone.
>
> Plone will work without the binary -- but will be unable to search
> the content of MS Word files ("wvHtml" is used to convert the binary
> Word format into a standard file format (HTML)).
>
> Thus, installing the binary is not strictly necessary -- but allows
> for improved Plone support for MS-Word files.
>
>> ....
>>Now, onward with your recommendations ...
>> ....
>>> Use your original instance (including the original "Products.CacheSetup")
>>> to uninstall "CacheSetup" from your portal.
>>>
>>> Report any problem that occurs thereby.
>>
>>>From [site]/portal_quickinstaller, I uninstall CacheSetup v1.1, and it
>>seems to work: both CacheSetup and CMFSquidTool are moved from the
>>list of installed products to the list of those available for install.
>> However, moving back to view the Plone site root then throws a
>>massive traceback, and rebuilding the catalog fails as well.  The site
>>view traceback is "AttributeError: portal_cache_settings", which I
>>don't understand since portal_cache_settings got removed from the site
>>on uninstall.
>
> You get the "AttributeError" because "portal_cache_settings" has
> been removed. The "uninstall" apparently has not been clean (some
> bug in the "uninstall" code) and there is still something left around
> (maybe something in "portal_skins").
>
> The traceback (which you have not reported) will give hints to
> this "left around".
>
>
>>Also, the base_cache_rule.py warning remains on zope client in debug
>>startup, but perhaps that's only because I didn't remove the Products
>>directory after uninstall.
>
> Indeed.
>
>> If I remove the directory entirely, all
>>kinds of things break, and the instance won't start.
>
> Strange. Your Plone site may no longer work but the instance
> should still start...
>
> You must tell us about the messages from the aborted startup...
> Otherwise, we cannot guess what went wrong.
>
>
>>In the ZMI site view, all of the content object type entries appear
>>with a type name (ATFolder, etc.) instead of an icon, and
>>"AttributeError: portal_cache_settings" is thrown there as well.
>
> We know exceptions of this type already. They look like the one
> discussed below.
>
>>>>Traceback (innermost last):
>>>> ...
>>>>    * Module Products.CacheSetup.patch_cmf, line 29, in FSPT_pt_render
>>>>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>>>>    * Module Products.CMFCore.FSPageTemplate, line 155, in pt_render
>>>>    * Module Products.CacheSetup.patch_cmf, line 77, in PT_pt_render
>>>>    * Module Products.CacheSetup.patch_utils, line 9, in call_pattern
>>>>    * Module Products.PageTemplates.PageTemplate, line 89, in pt_render
>>>> ...
>>>>    * Module zope.tal.talinterpreter, line 745, in do_insertStructure_tal
>>>>    * Module Products.PageTemplates.Expressions, line 221, in
>>>> evaluateStructure
>>>>    * Module zope.tales.tales, line 696, in evaluate
>>>>      URL:
>>>> file:/var/plone/zeocluster/client1/Products/CacheSetup/skins/cache_setup/global_cache_settings.pt
>>>>      Line 5, Column 4
>>>>      Expression: <PythonExpr
>>>> ...
>>>>    * Module None, line 10, in enableHTTPCompression
>>>>      <FSPythonScript at /my-site/enableHTTPCompression>
>>>>      Line 10
>>>>AttributeError: portal_cache_settings
>>> Maybe a bug in the uninstallation code (or some version problem).
>>>
>>> Apparently, "Products.CacheSetup" has added one or more layers
>>> to the "portal_skins" skin. Uninstallation may then pose non trivial
>>> phasing requirements.
>>> For your traceback, I guess that the "enableHTTPCompression" above
>>> comes from "Products.CacheSetup" and expects an object
>>> "portal_cache_settings"
>>> (belonging to "Products.CacheSetup"). After "portal_cache_settings"
>>> is uninstalled, the above "enableHTTPCompression" can no longer be used
>>> but apparently is yet.
>>>
>>> As a workaround measure: locate the source of the above script
>>> and comment out all code referencing "Products.CacheSetup" objects.
>>> If necessary, let it return immediately (you will lose http compression -
>>> but that is only an optimization).
>>
>>OK, which script do you mean here? I assume these files:
>>CacheSetup/skins/cache_setup/global_cache_settings.pt
>>CMFPlone/skins/plone_scripts/enableHTTPCompression.py
>>... which refer to:
>>CacheSetup/skins/cache_setup/enableHTTPCompression.py
>
> Once, you have uninstalled "CacheSetup", the second "enableHTTPCompression.py"
> (the one from "CacheSetup") should no longer be used.
>
> I suspect the "CacheSetup" uninstall to forget the skin cleanup --
> causing that the wrong "enableHTTPCompression" (that from "CacheSetup")
> is still used and no longer functioning (because "portal_cache_settings"
> has been removed by the uninstallation).
>
> If you can still use the ZMI to change "portal_skins",
> use it to remove any layers referencing "CacheSetup" (probably spelled
> differently) in your skin definitions (--> "Properties" tab of
> "portal_skins"). When my assumption is correct, the problem
> will disappear (from this place, at least) if you succeed.
>
>
> If you cannot use the ZMI, then let return the "CacheSetup"
> "enableHTTPCompression.py" immediately. Then change "portal_skins"
> as described above.
>
>
>>After editing these, I see the same symptoms (AttributeError:
>>portal_cache_settings, AT type names instead of icons, catalog rebuild
>>fails, etc.). Also noticed that in [site]/manage_workspace, there are
>>still CacheSetup "Add" items available to add to the site.
>
> Have you performed a restart after your editing?
>
> If so, look again at the resulting traceback. It will tell you
> where precisely the "AttributeError: 'portal_cache_settings'" occured.
>
> If it still comes from "enableHTTPCompression", then there are
> several possibilities:
>
>  *  you made something wrong during your edit and
>     the code referencing "portal_cache_settings" is still executed
>
>  *  the really executed "enableHTTPCompression" is different from
>     the ones you have edited
>
>     There are ways to determine precisely what object is used --
>     but they involve starting Plone in an interactive Python session
>     or some kind of debugging. I will elaborate later, when necessary.
>
>> ...
>>Removed cache_setup from portal_skins-> Properties, but that hasn't
>>changed any of the above conditions.  I'll include the current
>>traceback for viewing site content via ZMI in [1].
>> ...
>>[1]
>>2011-09-16 14:20:45 ERROR Zope.SiteErrorLog
>>http://localhost:8080/my-site/folder_icon.gif/index_html
>>Traceback (innermost last):
>>  Module ZPublisher.Publish, line 119, in publish
>>  Module ZPublisher.mapply, line 88, in mapply
>>  Module ZPublisher.Publish, line 42, in call_object
>>  Module Products.CMFCore.FSImage, line 126, in index_html
>>  Module Products.CMFCore.utils, line 460, in _setCacheHeaders
>>  Module Products.CacheSetup.content.caching_policy_manager, line 69,
>>in getHTTPCachingHeaders
>>  Module Products.CacheSetup.content.caching_policy_manager, line 54,
>>in getHeadersToAddAndRemove
>>  Module Products.CMFCore.utils, line 123, in getToolByName
>>AttributeError: portal_cache_settings
>
> The "AttributeError: portal_cache_settings" now comes from a different
> place. This probably means: we have solved the "enableHTTPCompression"
> problem.
>
> For the future: always look at the tracebacks; they tell you
> where the problem occurs and thereby give invaluable help for
> the analysis.
>
>
> In the current case, the traceback tells you that despite
> you have uninstalled "CacheSetup", your site is still using it
> (another "CacheSetup" "uninstall" bug).
>
> The traceback tells you that the interface happens at
> line "460" of "Products.CMFCore.utils" in "_setCacheHeaders".
> Thus, we have to look there why "CacheSetup" is activated.
> The code there is:
>
>        headers = manager.getHTTPCachingHeaders(
>                          content, view_name, extra_context
>                          )
>
> and "manager" has formerly be determined by
>
>        manager = getToolByName(obj, 'caching_policy_manager', None)
>
> This means that the "CacheSetup" "uninstall" has forgotten to
> restore the original "caching_policy_manger" (a problem
> apparently solved in a later "CacheSetup" version -- but one that
> uses a saved copy of the original "caching_policy_manger" and
> your "caching_policy_manger" lacks this copy).
>
> A workaround could be to manually delete the "caching_policy_manger"
> (and then maybe recreate it manually).
>
>
>
> --
> Dieter
>

plone-traceback-logs.txt (31K) Download Attachment
12
Loading...