I've recently started adding plone.caching ruleset declarations to my views:
<cache:ruleset
for=".views.MyContentTypeView"
ruleset="plone.content.itemView"
/>
I've started seeing these in my development site's log:
2012-10-23 14:48:02 ERROR Zope.SiteErrorLog 1351000082.330.867850813917 http://localhost:12311/my_content_type/##landing
Traceback (innermost last):
Module ZPublisher.Publish, line 117, in publish
Module zope.event, line 31, in notify
Module zope.component.event, line 24, in dispatch
Module zope.component._api, line 136, in subscribers
Module zope.component.registry, line 321, in subscribers
Module zope.interface.adapter, line 585, in subscribers
Module plone.caching.hooks, line 102, in intercept
Intercepted
From hooks.py, in intercept()'s docstring:
To properly abort request processing, this will raise an exception. The
actual response (typically an empty response) is then set via a view on
the exception. We set and lock the response status to avoid defaulting to
a 404 exception.
It therefore looks like these errors might be expected behaviour? If so, is it possible to get Zope to ignore these errors so they don't clutter my logs?
Related
I am running a pretty much unmodified instance of Plone 5.0.
I created a lot of folders today, one of which was named "Layout" in a parent folder "Design", which was in the root folder.
This Layout folder caused an error in the view of the Design folder. All I see is the error page
We’re sorry, but there seems to be an error…
The error has been logged as entry number 1470387402.080.1605824509.
If you need to report this to the
Site Administration, please include this entry number in your message.
The error log of Plone has the following entry:
Exception Type
RuntimeError
Exception Value
maximum recursion depth exceeded
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.BaseRequest, line 444, in traverse
Module Products.CMFCore.DynamicType, line 147, in __before_publishing_traverse__
Module Products.CMFDynamicViewFTI.fti, line 236, in queryMethodID
Module Products.CMFDynamicViewFTI.fti, line 197, in defaultView
Module Products.CMFPlone.PloneTool, line 771, in browserDefault
Module Products.CMFDynamicViewFTI.browserdefault, line 99, in getLayout
Module Products.CMFDynamicViewFTI.fti, line 136, in getViewMethod
Module Products.CMFDynamicViewFTI.browserdefault, line 72, in __call__
Module Products.CMFDynamicViewFTI.browserdefault, line 72, in __call__
Module Products.CMFDynamicViewFTI.browserdefault, line 72, in __call__
Module Products.CMFDynamicViewFTI.browserdefault, line 72, in __call__
Module Products.CMFDynamicViewFTI.browserdefault, line 72, in __call__
and goes on for a couple of dozen identical calls.
This only happens with this specific folder. I deleted it and created it again: same error. All other folders work fine, even much deeper folder structures work fine.
Any idea what is wrong with this specific folder name?
Sometimes this happen with Plone due to acquisition.
Some names are reserved (looking at your traceback the issue seems related to the view selection, and Layout is in fact a dangerous name).
Plone itself protects you from creating some bad ids but it can cover all the cases.
Another common case with this type of issue is calling a catalog index "data", or calling a content like a catalog index.
Just use a different name.
I'm trying to upgrade a Plone 4.0.10 site to 5.0. I went through the upgrade to 4.3.6 and somewhat painfully got it to work there. In my Data.fs I have two Plone sites: the site in question, and another one that has nothing but the default content (News, Events, Users). When I moved the Data.fs and blobs from the 4.3.6 to the Plone 5 instance, the "empty" site upgraded fine. However, if I even try to go to the ZMI root for the production site, or to load the site, I get this:
2015-12-05 17:19:24 ERROR Zope.SiteErrorLog 1449364764.10.146181213601 http://localhost:8080/mysite
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.BaseRequest, line 444, in traverse
Module ZPublisher.BeforeTraverse, line 97, in __call__
Module Products.CMFCore.PortalObject, line 75, in __before_publishing_traverse__
Module zope.event, line 31, in notify
Module zope.component.event, line 24, in dispatch
Module zope.component._api, line 136, in subscribers
Module zope.component.registry, line 321, in subscribers
Module zope.interface.adapter, line 585, in subscribers
Module zope.component.event, line 32, in objectEventNotify
Module zope.component._api, line 136, in subscribers
Module zope.component.registry, line 321, in subscribers
Module zope.interface.adapter, line 585, in subscribers
Module plone.app.theming.plugins.hooks, line 33, in onRequest
Module plone.app.theming.policy, line 91, in isThemeEnabled
AttributeError: 'NoneType' object has no attribute 'enabled'
I don't know why plone.app.theming is involved, since the old site had no Diazo theme, and I'm just loading the ZMI. Also, the problem seems to be that there is no IRegistry:
In plone.app.theming.policy.getSettings:
def getSettings(self):
"""Settings for current theme."""
registry = queryUtility(IRegistry)
And registry at this point is None, and so is settings in plone.app.theming.policy.isThemeEnabled.
Any suggestions on how to proceed?
plone.app.theming has to be installed in Plone 4. Include p.a.t in your Plone 4.3.6 Site and re-upgrade.
(How to upgrade sites to Plone 5, 24:15)
I'm attempting an upgrade of an existing site from Plone 3.3.6 to Plone 4.3.7, and then on to Plone 5.0.
The existing site is very small, and has no add-on Products installed (vanilla Plone, vanilla template, etc.) It did have CacheFu installed, but after some earlier obvious errors with that, I removed it prior to the upgrade. I'm simply copying the contents of var/filestorage (Data.fs, etc) from v3 site to v4 site and re-running buildout.
In Plone 4.3.7, when running the UPGRADE option, I see a lot of successful activity, and then the following error at the bottom:
Upgrade aborted. Error:
Traceback (most recent call last):
File "/usr/local/Plone4_migration/buildout-cache/eggs/Products.CMFPlone-4.3.7-py2.7.egg/Products/CMFPlone/MigrationTool.py", line 259, in upgrade
step['step'].doStep(setup)
File "/usr/local/Plone4_migration/buildout-cache/eggs/Products.GenericSetup-1.7.7-py2.7.egg/Products/GenericSetup/upgrade.py", line 160, in doStep
self.handler(tool)
File "/usr/local/Plone4_migration/buildout-cache/eggs/plone.app.upgrade-1.3.18-py2.7.egg/plone/app/upgrade/v40/betas.py", line 99, in beta3_beta4
value.remove('Large Plone Folder')
AttributeError: 'tuple' object has no attribute 'remove'
If I skip Plone 4.x and jump right to Plone 5.0, I can't even run the UPGRADE feature, and just get the following error trace on the console:
2015-10-09 01:14:21 ERROR Zope.SiteErrorLog 1444371261.060.792132208718 http://www.example.com/example
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.BaseRequest, line 444, in traverse
Module ZPublisher.BeforeTraverse, line 97, in __call__
Module Products.CMFCore.PortalObject, line 75, in __before_publishing_traverse__
Module zope.event, line 31, in notify
Module zope.component.event, line 24, in dispatch
Module zope.component._api, line 136, in subscribers
Module zope.component.registry, line 321, in subscribers
Module zope.interface.adapter, line 585, in subscribers
Module zope.component.event, line 32, in objectEventNotify
Module zope.component._api, line 136, in subscribers
Module zope.component.registry, line 321, in subscribers
Module zope.interface.adapter, line 585, in subscribers
Module plone.app.theming.plugins.hooks, line 33, in onRequest
Module plone.app.theming.policy, line 90, in isThemeEnabled
AttributeError: 'NoneType' object has no attribute 'enabled'
This is a known bug which has a fix that was not released yet: https://github.com/plone/Products.CMFPlone/issues/1134
Can anybody explain me that error - and how I can repair it?
We use:
Plone 4
Zope 2.12.19
ZEO
zodb-temporary-storage
Error Log
Site Error
An error was encountered while publishing this resource.
Sorry, a site error occurred.
Traceback (innermost last):
Module ZPublisher.Publish, line 239, in publish_module_standard
Module ZPublisher.Publish, line 197, in publish
Module ZPublisher.Publish, line 197, in publish
Module ZPublisher.Publish, line 197, in publish
Module ZPublisher.Publish, line 173, in publish
Module plone.app.linkintegrity.monkey, line 17, in zpublisher_exception_hook_wrapper
Module ZPublisher.Publish, line 135, in publish
Module Zope2.App.startup, line 291, in commit
Module transaction._manager, line 93, in commit
Module transaction._transaction, line 322, in commit
Module transaction._transaction, line 419, in _commitResources
Module ZODB.Connection, line 767, in tpc_vote
Module ZEO.ClientStorage, line 1068, in tpc_vote
Module ZEO.ClientStorage, line 905, in _check_serials
ConflictError: database conflict error (oid 0x08, class Products.Transience.Transience.Length2, serial this txn started with 0x0394fddba7126fbb 2012-03-08 07:23:39,157504, serial currently committed 0x0394fddbb0a4cb22 2012-03-08 07:23:41,400873)
Troubleshooting Suggestions
The URL may be incorrect.
The parameters passed to this resource may be incorrect.
A resource that this resource relies on may be encountering an error.
For more detailed information about the error, please refer to the error log.
If the error persists please contact the site maintainer. Thank you for your patience.
I tried to repaire the Data.fs without any errors...
Thanks in advance.
Conflict Errors occur when two users try to update the same object (often one that is part of a catalogue data structure) at the same time and the system cannot resolve the conflict. You should ensure that your ZEO server includes all of the eggs from the Zope instance to ensure you have all the conflict resolution code.
If you are seeing these on simple views, then it probably means you have some code that is updating the database on rendering that view. This is not a good idea with ZODB.
I'm on Plone 4.0.1 and I'm trying to use c.googleanalytics 1.1.
Following the docs I registered my domain on google accounts and I got my "OAuth Consumer Key" and "OAuth Consumer Secret".
Now, every time I try to access the portal (no matter the user) I get this:
Traceback (innermost last):
Module ZPublisher.Publish, line 127, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 47, in call_object
Module zope.formlib.form, line 782, in __call__
Module five.formlib.formbase, line 50, in update
Module zope.formlib.form, line 745, in update
Module plone.fieldsets.form, line 24, in setUpWidgets
Module zope.formlib.form, line 384, in setUpEditWidgets
Module zope.schema._field, line 291, in bind
Module Products.Five.schema, line 36, in get
Module collective.googleanalytics.vocabularies, line 45, in getWebProperties
Module plone.memoize.volatile, line 276, in replacement
Module collective.googleanalytics.utility, line 213, in getAccountsFeed
Module collective.googleanalytics.utility, line 172, in makeClientRequest
Module gdata.analytics.service, line 97, in GetAccountList
Module gdata.analytics.service, line 77, in QueryAccountListFeed
Module gdata.service, line 1097, in Get
Module gdata.service, line 1108, in Get
RequestError: {'status': 403, 'body': 'No Analytics account was found for the currently logged-in user.', 'reason': 'Forbidden'}
How it's supposed to work if I cannot insert my authentication data?
I see in
collective.googleanalytics-1.1-py2.6.egg/collective/googleanalytics/interfaces/utility.py
that there is a field "auth_token" so I suppose that something must be filled in... but that's impossible because the above mentioned error does not allow to get the form.
Thank in advance for any pointers.
It looks like you're getting a bad AuthSub token, perhaps by authorizing using a non-Google account:
http://groups.google.com/group/google-analytics-data-export-api/browse_thread/thread/712abe41ad57095b/363bb2aa1db308fd
I've opened a bug report in the collective.googleanalytics issue tracker:
http://plone.org/products/collective.googleanalytics/issues/9/view
Please follow up with me there so that we can get this resolved. Thanks!