[Zope3-Users] Trouble Starting up !!
Hi
Steps
1. zopeproject zx
2. cd zx
3. ./bin/buildout
Develop: '/home/zope3/Work/z3w/zx/.'
Unused options for buildout: 'download-directory'.
Updating app.
Updating test.
4. ./bin/zx-debug
--
2009-04-07T11:43:36 WARNING root Developer mode is enabled: this is a
security risk and should NOT be enabled on production servers. Developer
mode can usually be turned off by setting the `devmode` option to `off`
or by removing it from the instance configuration file completely.
Traceback (most recent call last):
File ./bin/zx-debug, line 116, in module
zx.startup.interactive_debug_prompt()
File /home/zope3/Work/z3w/zx/src/zx/startup.py, line 13, in
interactive_debug_prompt
db = zope.app.wsgi.config(zope_conf)
SNIP LOT OF LINES
raise schema.ValidationError(v)
zope.configuration.xmlconfig.ZopeXMLConfigurationError: File
/home/zope3/Work/z3w/zx/site.zcml, line 4.2-4.26
ZopeXMLConfigurationError: File
/home/zope3/Work/z3w/zx/src/zx/configure.zcml, line 10.2-10.42
ZopeXMLConfigurationError: File
/home/zope3/.buildout/eggs/zope.app.zcmlfiles-3.4.3-py2.5.egg/zope/app/zcmlfiles/configure.zcml,
line 62.2-62.38
ConfigurationError: ('Invalid value for', 'package', 'ImportError:
Module zope.app has no global error')
I hope there is something that can be done to ensure that the fresh
installs are trouble-free (there are other issues I posted about recently).
Cheers
___
Zope3-users mailing list
Zope3-users@zope.org
http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] ImportError: No module named viewlet.interfaces !!
On Tue, Apr 7, 2009 at 7:37 AM, Chetan Kumar chetan.ml...@gmail.com wrote: Stephan Richter wrote: For some reason that smells like a circular import problem, Regards, Stephan The reason was the absence of path to zope.viewlet egg from the sys.path. This slippage can surely be attributed to buildout. Also discovered that out of 170 eggs listed in buildout.cfg only about 60 appear in the scipts generated by buildout (paster, debug, ctl, python). Does it sound reasonable to say that buildout machinary may need attention? You should produce a small, self-contained example of the problem so it can be evaluated. My suspicion is a bug in your buildout config rather than buildout itself, but I can't tell from here. -- Benji York Senior Software Engineer Zope Corporation ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] ImportError: No module named viewlet.interfaces !!
Stephan Richter wrote: For some reason that smells like a circular import problem, Regards, Stephan The reason was the absence of path to zope.viewlet egg from the sys.path. This slippage can surely be attributed to buildout. Also discovered that out of 170 eggs listed in buildout.cfg only about 60 appear in the scipts generated by buildout (paster, debug, ctl, python). Does it sound reasonable to say that buildout machinary may need attention? I do not know if this issue has hit others. I added the paths to the scripts and moved one step further before getting caught in another situation. Now, the browser:viewletManager directive is absent. meta.zcml ??? Cheers ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
[Zope3-Users] z3c.form: LookupErrors
Hi, In z3c.form (at least with 1.9.0), if you have a Choice field and the vocabulary changes so that an existing value (or the default value on an add form) is no longer valid, you get a LookupError: Module z3c.form.form, line 126, in updateWidgets Module z3c.form.field, line 259, in update Module z3c.form.browser.select, line 51, in update Module z3c.form.browser.widget, line 61, in update Module z3c.form.widget, line 182, in update Module z3c.form.widget, line 120, in update Module z3c.form.converter, line 258, in toWidgetValue Module z3c.form.term, line 31, in getTerm Module zope.schema.vocabulary, line 124, in getTerm It'd be nicer if z3c.form would catch the error and return field.missing_value or something like that. As it stands, if this happens with a content object, it's impossible to reach the edit form and fix the value! Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] ImportError: No module named viewlet.interfaces !!
Made a mistake in posting last time. Posting again for the sake of completeness: The problem started after installation. Without bothering about KGS the result of the installation is here http://paste.plone.org/27456 (./bin/xv-debug show errors at seen at the bottom) With KGS 3.4.0 (using buildout.cfg snippet from http://download.zope.org/zope3.4/3.4.0/versions.cfg) the situation is different http://paste.plone.org/27457 Here I cannot from zope.viewlet.interfaces import IviewletManager. This is because zope.viewlet-3.4.2-py2.5.egg and zope.contentprovider-3.4.0-py2.5.egg are missing from bin/xv_kgs-debug. If I add these manually I get over the problem. This is not the way it should be. These eggs are listed in the buildout.cfg file http://paste.plone.org/27458 as these were copied from the buildout.cfg snippet The list of eggs in the buildout.cfg and those in the bin/paster and its friends have to be same as this is generated by buildout. Cheers ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] z3c.form: LookupErrors
Hi Martin -Ursprüngliche Nachricht- Von: zope3-users-boun...@zope.org [mailto:zope3-users-boun...@zope.org] Im Auftrag von Martin Aspeli Gesendet: Dienstag, 7. April 2009 16:17 An: zope3-users@zope.org Betreff: [Zope3-Users] z3c.form: LookupErrors Hi, In z3c.form (at least with 1.9.0), if you have a Choice field and the vocabulary changes so that an existing value (or the default value on an add form) is no longer valid, you get a LookupError: Module z3c.form.form, line 126, in updateWidgets Module z3c.form.field, line 259, in update Module z3c.form.browser.select, line 51, in update Module z3c.form.browser.widget, line 61, in update Module z3c.form.widget, line 182, in update Module z3c.form.widget, line 120, in update Module z3c.form.converter, line 258, in toWidgetValue Module z3c.form.term, line 31, in getTerm Module zope.schema.vocabulary, line 124, in getTerm It'd be nicer if z3c.form would catch the error and return field.missing_value or something like that. As it stands, if this happens with a content object, it's impossible to reach the edit form and fix the value! This is a legacy data problem. Such data need to get migrated by a generation if a value is no longer valid. Otherwise the wrong (not valid) value is still used in the app. It doesn't make sense to just skip invalid values and fallback to missing_value in the vocabulary widget since this value get used by everthing else then the widget. But probably if legacy data are not a problem in some apps, we should implement a vocabulary and widget which can handle such legacy data problems or make it a configurable option. I also was thinking about a widget which allows to define depreated values which are valid but not shown for selecting. this whould allow to skip values fer a future selection. Probably this whould require a enhanced vocabulary implementation which offers a deprecated value list or something like that. What do you think? Whould this fit for you? Regards Roger Ineichen Martin -- Author of `Professional Plone Development`, a book for developers who want to work with Plone. See http://martinaspeli.net/plone-book ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] z3c.form: LookupErrors
On Tuesday 07 April 2009, Roger Ineichen wrote: It'd be nicer if z3c.form would catch the error and return field.missing_value or something like that. As it stands, if this happens with a content object, it's impossible to reach the edit form and fix the value! This is a legacy data problem. Such data need to get migrated by a generation if a value is no longer valid. No, it is not. The legacy data problem is a special case. What if your list of choices depends on constantly changing data? For example, a widget allows you to select a user from a userfolder. Later the user gets deleted. Just because you selected the user before, the form should not fail. I totally agree with Martin that we should use missing_value in those cases. I think this could actually be considered a fairly serious bug. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] z3c.form: LookupErrors
Hi Stephan -Ursprüngliche Nachricht- Von: Stephan Richter [mailto:srich...@cosmos.phy.tufts.edu] Gesendet: Dienstag, 7. April 2009 19:30 An: zope3-users@zope.org; d...@projekt01.ch Cc: 'Martin Aspeli' Betreff: Re: [Zope3-Users] z3c.form: LookupErrors On Tuesday 07 April 2009, Roger Ineichen wrote: It'd be nicer if z3c.form would catch the error and return field.missing_value or something like that. As it stands, if this happens with a content object, it's impossible to reach the edit form and fix the value! This is a legacy data problem. Such data need to get migrated by a generation if a value is no longer valid. No, it is not. The legacy data problem is a special case. What if your list of choices depends on constantly changing data? For example, a widget allows you to select a user from a userfolder. Later the user gets deleted. pang, legacy data created Just because you selected the user before, the form should not fail. and the question is, do you cleanup legacy data or not I totally agree with Martin that we should use missing_value in those cases. Defently not. Such forms will show you a default value and you think this is Ok. But the object devliers still the old stored value. Pang, pang and you will be surprised till you will start debugging and see the real value decorated within the missing_value. That's a horrible scenario! I think this could actually be considered a fairly serious bug. No, defently not, the Choice field defines what are valid values and the widget only handels that. There is no reason why a widget should do more then that. If you remove valid values for a field, you also have to make sure that the system doesn't use them. Doesn't matter if a system can work with different/legacy data or not. I think you are right that a valid missing_value should get used, but that must be implemented at the field level. The field has to return that missing_value. This will make sure that objects value returns the same as the widget does. But that's a kind of auto-mirgation for legacy data. And I'm not sure if this is a good idea. Regards Roger Ineichen Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
Re: [Zope3-Users] Rotating z3.log
On Tuesday 07 April 2009, andrew wrote: Does anyone know of a straightforward way of setting up a Zope3 instance to rotate z3.log ? At the moment I have one big file but this is not great for backups. I suppose I could use logrotate (and will have to if there's no Zope solution), but from a cursory dig into ZConfig it looks like it should be possible. accesslog logfile path access.log max-size 50MB old-files 5 /logfile /accesslog There are more options, but that's what I use. Regards, Stephan -- Stephan Richter Web Software Design, Development and Training Google me. Zope Stephan Richter ___ Zope3-users mailing list Zope3-users@zope.org http://mail.zope.org/mailman/listinfo/zope3-users
