- Zope - Zope lists

OFS.Cache.Cacheable.ZCacheable_invalidate and view_name
by Maciej Wisniowski 20 Nov '06

20 Nov '06

Hi Question is, what is view_name supposed to do during invalidation? In OFS.Cache.Cacheable we have: def ZCacheable_invalidate(self, view_name='', REQUEST=None): '''Called after a cacheable object is edited. Causes all cache entries that apply to the view_name to be removed. Returns a status message. ''' c = self.ZCacheable_getCache() if c is not None: ob, view_name = self.ZCacheable_getObAndView(view_name) try: message = c.ZCache_invalidate(ob) (...) and: def ZCacheable_getObAndView(self, view_name): (...) ob = self if not view_name and self.ZCacheable_isAMethod(): # This is a ZClass method. ob = aq_parent(aq_inner(self)) if isCacheable(ob): view_name = self.getId() else: # Both the parent and the child have to be # cacheable. ob = self return ob, view_name As far as I understand this, 'view_name' is useless here, and invalidation always occurs for all cache keys associated with object 'ob'. But this is not what docstring for ZCacheable_invalidate says. Seems strange but maybe I've missed something here? -- Maciej Wisniowski

2 2

Link download zope ?
by Luc Van Tien 20 Nov '06

20 Nov '06

My server is under Sun Solaris 10 sparc. I want to install Zope version 2 newest.(version binary not source code ). Anyone show me link to download. PS : when i install source code zope 2 on sun solaris,always found bugs. But when i install it on redhat ,its works fine. --------------------------------- Hãy ghé qua trang chủ Yahoo! Việt Nam!

4 3

FTP Access to a Windows Zope Instance
by Dennis Schulz 20 Nov '06

20 Nov '06

Hi, how to access the ZODB of a zope instance in windows? All FTP I tried could connect but not list the folder content, I think they expect unix servers? Dennis

2 1

index_object() calls give AttributeError after move from 2.7.5 to 2.8.8
by John Schinnerer 20 Nov '06

20 Nov '06

Aloha, I have just moved some sites with relatively simple custom products from 2.7.5 to 2.8.8. The products enable creation, editing and cataloging of simple folderish objects with some properties and some contained objects. They are built using mxmEasyProduct. I moved (installed) the necessary products in the 2.8.8 instance, then exported site root folders from 2.7.5 instance and imported them to 2.8.8 instance, then re-cataloged the catalogs. All that went fine and the vast majority of everything works, except the object indexing calls in the products! Now all calls in my products to any of the object indexing methods give an AttributeError with the method name as the ErrorValue. For example I have an edit function that updates properties of an object from data in a form submission and then reindexes the object with: self.reindex_object() Worked fine in 2.7.5, in 2.8.8 I get this traceback: ----------- Traceback (innermost last): Module ZPublisher.Publish, line 114, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 40, in call_object Module Products.GTIGalleryItem.GTIGalleryItem, line 52, in editGTIGalleryItem AttributeError: reindex_object ----------- ...line 52 is simply the above line of code, self.reindex_object(). Likewise when adding such an object the call: newObjId.index_object() gives me this traceback: ------------------ Traceback (innermost last): Module ZPublisher.Publish, line 114, in publish Module ZPublisher.mapply, line 88, in mapply Module ZPublisher.Publish, line 40, in call_object Module Shared.DC.Scripts.Bindings, line 311, in __call__ Module Shared.DC.Scripts.Bindings, line 348, in _bindAndExec Module Products.PythonScripts.PythonScript, line 323, in _exec Module None, line 11, in add_GTIGalleryItem - <PythonScript at /growingthroughit.org/add_GTIGalleryItem used for /growingthroughit.org/galleryitems/wg> - Line 11 Module Products.GTIGalleryItem.GTIGalleryItem, line 99, in manage_addAction AttributeError: index_object -------------------- ...line 99 is the above code, newObjId.index_object() Any call to someObject.unindex_object() gives an essentially similar AttributeError. I have zearched zope.org and googled and I cannot find anything relevant...there is no mention of changes to the indexing methods in the CHANGES.txt files for 2.8.x or 2.7.x or anywhere else I can find. I have installed the same mxmEasyProduct in 2.8.8 as in 2.7.5. Any ideas welcome...why do I suddenly get an AttributeError here? thanks, John S. -- John Schinnerer - MA, Whole Systems Design ------------------------------------------ - Eco-Living - Whole Systems Design Services People - Place - Learning - Integration john(a)eco-living.net http://eco-living.net

1 1

Traversal bug in 2.10 ?
by Godefroid Chapelle 20 Nov '06

20 Nov '06

Hi, I am working on integration of last Selenium version in Zelenium. I obviously want this new release to work on 2.10 When traversing to a zuite, it is supposed to call its index_html template. This does work on 2.9. On 2.10, I get the following error: Cannot locate object at: http://localhost:8080/zuite/%40%40index_html IOW, it looks like a redirect to '((index_html'. I have no clue about the cause of this error. Any hints ? -- Godefroid Chapelle (aka __gotcha)- BubbleNet http://bubblenet.be

1 0

Zope on Mac OS X Server
by Tom Von Lahndorff 18 Nov '06

18 Nov '06

Hi I'm having trouble setting redirecting port 80 to port 8080 on Mac OS X Server 10.4. I installed Zope via the Plone installer and have a an Instance running in the Applications folder. I can access the ZMI on port 8080 via the machines IP address, but I can't seem to get the Apache rewrite rule to work as shown in the various documentation. I'm curious if anyone has done this before and/or has used OS X Server's Server Admin tool to create an alias or redirect from port 80 to 8080. Thanks in advance. Tom

2 1

ImportError: No module named cPersistence
by Glenn Gillis 18 Nov '06

18 Nov '06

I'm stuck on this error attempting to start Zope 2.9.5 with Python 2.4.3 on a FreeBSD 4.11-RELEASE-p22 box: "ImportError: No module named cPersistence" I've Googled the error message and have found several instances of others receiving this error but no good candidates for resolving the problem. Python 2.4.3 seems to be the recommended version for Zope 2.9.5 according to the release announcement (<http://zope.org/Products/Zope/2.9.5/Zope-2_9_5-released>) and I swear I've installed other 2.9.5 Zopes on this box. The full error message is quoted below, and my etc/zope.conf file is attached. Anyone have any suggestions? Thanks, Glenn Gillis ELAW U.S. Information Technology Manager Environmental Law Alliance Worldwide http://www.elaw.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [glenn@luna:www-dev.elaw.org]$ sudo ./bin/zopectl start Traceback (most recent call last): File "/var/newzope/software-home/Zope-2.9.5-final/lib/python/Zope2/Startup/zopectl.py", line 322, in ? main() File "/var/newzope/software-home/Zope-2.9.5-final/lib/python/Zope2/Startup/zopectl.py", line 280, in main options.realize(args) File "/var/newzope/software-home/Zope-2.9.5-final/lib/python/Zope2/Startup/zopectl.py", line 91, in realize ZDOptions.realize(self, *args, **kw) File "/var/newzope/software-home/zope295/lib/python/zdaemon/zdoptions.py", line 273, in realize self.load_schema() File "/var/newzope/software-home/zope295/lib/python/zdaemon/zdoptions.py", line 321, in load_schema self.schema = ZConfig.loadSchema(self.schemafile) File "/var/newzope/software-home/zope295/lib/python/ZConfig/loader.py", line 31, in loadSchema return SchemaLoader().loadURL(url) File "/var/newzope/software-home/zope295/lib/python/ZConfig/loader.py", line 65, in loadURL return self.loadResource(r) File "/var/newzope/software-home/zope295/lib/python/ZConfig/loader.py", line 159, in loadResource schema = ZConfig.schema.parseResource(resource, self) File "/var/newzope/software-home/zope295/lib/python/ZConfig/schema.py", line 27, in parseResource xml.sax.parse(resource.file, parser) File "/var/newzope/software-home/python243/Lib/xml/sax/__init__.py", line 33, in parse parser.parse(source) File "/var/newzope/software-home/python243/Lib/xml/sax/expatreader.py", line 107, in parse xmlreader.IncrementalParser.parse(self, source) File "/var/newzope/software-home/python243/Lib/xml/sax/xmlreader.py", line 123, in parse self.feed(buffer) File "/var/newzope/software-home/python243/Lib/xml/sax/expatreader.py", line 207, in feed self._parser.Parse(data, isFinal) File "/var/newzope/software-home/python243/Lib/xml/sax/expatreader.py", line 300, in start_element self._cont_handler.startElement(name, AttributesImpl(attrs)) File "/var/newzope/software-home/zope295/lib/python/ZConfig/schema.py", line 99, in startElement getattr(self, "start_" + name)(attrs) File "/var/newzope/software-home/zope295/lib/python/ZConfig/schema.py", line 475, in start_schema keytype, valuetype, datatype = self.get_sect_typeinfo(attrs) File "/var/newzope/software-home/zope295/lib/python/ZConfig/schema.py", line 201, in get_sect_typeinfo datatype = self.get_datatype(attrs, "datatype", "null", base) File "/var/newzope/software-home/zope295/lib/python/ZConfig/schema.py", line 194, in get_datatype return self._registry.get(dtname) File "/var/newzope/software-home/zope295/lib/python/ZConfig/datatypes.py", line 398, in get t = self.search(name) File "/var/newzope/software-home/zope295/lib/python/ZConfig/datatypes.py", line 423, in search package = __import__(n, g, g, component) File "/var/newzope/software-home/zope295/lib/python/Zope2/Startup/datatypes.py", line 20, in ? from ZODB.config import ZODBDatabase File "/var/newzope/software-home/zope295/lib/python/ZODB/__init__.py", line 20, in ? from persistent import TimeStamp File "/var/newzope/software-home/zope295/lib/python/persistent/__init__.py", line 19, in ? from cPersistence import Persistent, GHOST, UPTODATE, CHANGED, STICKY ImportError: No module named cPersistence ############################################################################### # Welcome to Zope 2. ############################################################################### # # This is the Zope configuration file. The Zope configuration file # shows what the default configuration directives are, and show # examples for each directive. To declare a directive, make sure that # you add it to a line that does not begin with '#'. Note that comments # are only allowed at the beginning of a line: you may not add comments # after directive text on the same line. # # Note for Developers # =================== # # This file is *not* auto-generated. If you create a new directive you # very likely want to include an example of how to use the new # directive in this file. # # You shouldn't modify 'zope.conf.in' to change # configuration. Instead, you should make a copy into 'zope.conf' and # modify that to avoid checking in changes to this file by mistake. # ZConfig "defines" used for later textual substitution %define INSTANCE /usr/local/zope/instance-home/www-dev.elaw.org %define ZOPE /var/newzope/software-home/Zope-2.9.5-final # Directive: instancehome # # Description: # The path to the data files, local product files, import directory, # and Extensions directory used by Zope. # # Required (no default) # # Example: # # instancehome /home/chrism/projects/sessions instancehome $INSTANCE # Directive: clienthome # # Description: # The directory in which a running Zope's process identifier files are # placed. # # Default: $INSTANCE/var # # Example: # # clienthome /home/chrism/projects/sessions/var # Directive: path # # Description: # Name of a directory which should be inserted into the # the beginning of Python's module search path. This directive # may be specified as many times as needed to insert additional # directories. The set of directories specified is inserted into the # beginning of the module search path in the order which they are specified # here. Note that the processing of this directive may happen too late # under some circumstances; it is recommended that you use the PYTHONPATH # environment variable if using this directive doesn't work for you. # # Default: $INSTANCE/lib/python # # Example: # # path $INSTANCE/mypymodules # Directive: products # # Description: # Name of a directory that contains additional Product packages. This # directive may be used as many times as needed to add additional # collections of products. Each directory identified will be # added to the __path__ of the Products package. All Products are # initialized in ascending alphabetical order by product name. If # two products with the same name exist in two Products directories, # the order in which the packages appear here defines the load # order. The master Products directory exists in Zope's software home, # and cannot be removed from the products path (and should not be added # to it here). # # Default: $INSTANCE/Products # # Example: # # products /home/chrism/projects/myproducts # Directive: environment # # Description: # A section which can be used to define arbitrary key-value pairs # for use as environment variables during Zope's run cycle. It # is not recommended to set system-related environment variables such as # PYTHONPATH within this section. # # Default: unset # # Example: # # <environment> # MY_PRODUCT_ENVVAR foobar # </environment> # Directive: debug-mode # # Description: # A switch which controls several aspects of Zope operation useful for # developing under Zope. When debug mode is on: # # - The process will not detach from the controlling terminal # # - Errors in product initialization will cause startup to fail # (instead of writing error messages to the event log file). # # - Filesystem-based scripts such as skins, PageTemplateFiles, and # DTMLFiles can be edited while the server is running and the server # will detect these changes in real time. When this switch is # off, you must restart the server to see the changes. # # Setting this to 'off' when Zope is in a production environment is # encouraged, as it speeds execution (sometimes dramatically). # # Default: off # # Example: # # debug-mode on # Directive: effective-user # # Description: # If you intend to run Zope as the "root" user, you must supply this # directive with an effective username or userid number to which Zope # will 'suid' after the server ports are bound. This directive only # has effect under UNIX and if Zope is started as the root user. # # Default: unset # # Example: # # effective-user chrism effective-user zope # Directive: enable-product-installation # # Description: # If this directive is turned on, Zope performs 'product installation' # (the registration of Python modules in various Products directories) # at startup. Turning this off can speed Zope/ZEO startup time, # but it can also cause your Control_Panel Product list to become # desynchronized with the contents of your Products # directories. NOTE: Zope *must* be started at least once with # this directive set to "on" or you will receive an error. If using ZEO, # at least one ZEO client must be run with this directive set to "on" # once, the others can have it turned off. # NOTE: If your main storage is mounted read-only, # you must set this directive to "off". # # Default: on # # Example: # # enable-product-installation off # Directive: locale # # Description: # Enable locale (internationalization) support by supplying a locale # name to be used. See your operating system documentation for locale # information specific to your system. If your Python module does not # support the locale module, or if the requested locale is not # supported by your system, an error will be raised and Zope will not # start. # # Default: unset # # Example: # # locale fr_FR # Directive: datetime-format # # Description: # Set this variable either to "us" or "international" to force the # DateTime module to parse date strings either with # month-before-days-before-year ("us") or # days-before-month-before-year ("international"). The default # behaviour of DateTime (when this setting is left unset) is to # parse dates as US dates. # # Default: us # # Example: # # datetime-format international # Directive: zserver-threads # # Description: # Specify the number of threads that Zope's ZServer web server will use # to service requests. The default is 4. # # Default: 4 # # Example: # # zserver-threads 10 # Directive: python-check-interval # # Description: # Specify an integer representing the Python interpreter "check # interval" This interval determines how often the interpreter checks # for periodic things such as thread switches and signal handlers. The # Zope default is 500, but you may want to experiment with other values # in order to attempt to increae performance in your particular # environment. # # Default: 500 # # Example: # # python-check-interval 1000 # Directive: zserver-read-only-mode # # Description: # If this directive is set to 'on', it will cause Zope to inhibit the # creation of log files and pid files. Access and event log files will # be presented on standard output. Setting this directive 'on' causes # pcgi, fastcgi, and daemon-related directives to have no effect. # # Default: off # # Example: # # zserver-read-only-mode on # Directive: pid-filename # # Description: # The path to the file in which the Zope process id(s) will be written. # This defaults to client-home/Z2.pid. # # Default: CLIENT_HOME/Z2.pid # # Example: # # pid-filename /home/chrism/projects/sessions/var/Z2.pid # Directive: lock-filename # # Description: # The path to a "lock file" which will be locked by Zope while it's # running. This file is used by zopectl.py to determine if Zope is # currently running. This defaults to CLIENT_HOME/Z2.lock. # # Default: CLIENT_HOME/Z2.lock # # Example: # # lock-filename /home/chrism/projects/sessions/var/Z2.lock # Directive: mime-types # # Description: # Tells Zope about additional mime.types files that should be # loaded. The files have the same format as the mime.types file # distributed with Apache. The "mime-types" setting may be given # more than once in the configuration file. # # Example: # # mime-types $INSTANCE/etc/mime.types # Directive: structured-text-header-level # # Description: # Set the default starting HTML header level for structured text # documents. The default is 3, which implies that top-level headers # will be created with an <H3> tag. # # Default: 3 # # Example: # # structured-text-header-level 1 # Directive: rest-input-encoding # # Description: # Specifies the input encoding of re-StructuredText documents # (e.g. 'utf-8', 'iso-8859-15' or any other valid encoding recognized # by Python). The default is your Python's default encoding. # # Default: unset (uses system default) # # Example: # # rest-input-encoding iso-8859-15 # Directive: rest-output-encoding # # Description: # Specifies the output encoding of re-StructuredText documents # (e.g. 'utf-8', 'iso-8859-15' or any other valid encoding recognized # by Python). The default is your Python's default encoding. # # Default: unset (uses system default) # # Example: # # rest-output-encoding iso-8859-15 # Directive: rest-header-level # # Description: # Set the default starting HTML header level for restructured text # documents. The default is 3, which implies that top-level headers # will be created with an <H3> tag. # # Default: 3 # # Example: # # rest-header-level 2 # Directive: rest-language-code # # Description: # Language code used for some internal translations inside of the docutils # package and for DTD bibliographic elements mapping. See # lib/python/docutils/languages/ for a list of supported language codes. # # Default: en # # Example: # # rest-language-code de # Directive: cgi-environment # # Description: # A section which allows a user to define arbitrary key-value pairs for # use as the initial CGI environment variables. This is useful # when you want to proxy requests from another web server to Zserver, # and would like Zserver's CGI environment to reflect the CGI # environment of the other web server. # # Default: unset # # Example: # # <cgi-environment> # HTTPS_SERVER Foobar Server 1.0 # HTTPS_PORT 443 # </cgi-environment> # Directive: dns-server # # Description: # Specify the IP address of your DNS server in order to cause resolved # hostnames to be written to Zope's access log. By default, Zope will # not resolve hostnames unless this is set. # # Default: unset # # Example: # # dns-server 127.0.0.1 dns-server 64.112.226.133 # Directive: ip-address # # Description: # The default IP address on which Zope's various server protocol # implementations will listen for requests. If this is unset, Zope # will listen on all IP addresses supported by the machine. This # directive can be overridden on a per-server basis in the servers # section. # # Default: unset # # Example: # # ip-address 127.0.0.1 ip-address 64.112.226.133 # Directive: http-realm # # Description: # The HTTP "Realm" header value sent by this Zope instance. This value # often shows up in basic authentication dialogs. # # Default: Zope # # Example: # # http-realm Slipknot # Directive: cgi-maxlen # # Description: # Set this value to limit the amount of form data being processed # by Zope to prevent DoS attacks. # # Default: 0 (= no restrictions) # # Example: # # cgi-maxlen 10000 # Directive: http-header-max-length # # Description: # Maximum number of bytes allowed within a HTTP request header. The request # is discarded and considered as a DoS attack if the header size exceeds # this limit. # # Default: 8192 # # Example: # # http-header-max-length 16384 # Directive: automatically-quote-dtml-request-data # # Description: # Set this directive to 'off' in order to disable the autoquoting of # implicitly retrieved REQUEST data by DTML code which contains a '<' # when used in <dtml-var> construction. When this directive is 'on', # all data implicitly retrieved from the REQUEST in DTML (as opposed to # addressing REQUEST.somevarname directly) that contains a '<' will be # HTML-quoted when interpolated via a <dtml-var> or &dtml- construct. This # mitigates the possibility that DTML programmers will leave their # sites open to a "client-side trojan" attack. # # Default: on # # Example: # # automatically-quote-dtml-request-data on # Directive: trusted-proxy # # Description: # Define one or more 'trusted-proxies' directives, each of which is a # hostname or an IP address. The set of definitions comprises a list # of front-end proxies that are trusted to supply an accurate # X-Forwarded-For header to Zope. If a connection comes from # a trusted proxy, Zope will trust any X-Forwarded header to contain # the user's real IP address for the purposes of address-based # authentication restriction. # # Default: unset # # Example: # # trusted-proxy www.example.com # trusted-proxy 192.168.1.1 # Directive: publisher-profile-file # # Description: # Names a file on the filesystem which causes Zope's Python # profiling capabilities to be enabled. For more information, see # the Debug Information - > Profiling tab of Zope's Control_Panel # via the Zope Management Interface. IMPORTANT: setting this # filename will cause Zope code to be executed much more slowly # than normal. This should not be enabled in production. # # Default: unset # # Example: # # publisher-profile-file $INSTANCE/var/profile.dat # Directive: security-policy-implementation # # Description: # The default Zope security machinery is implemented in C. Change # this to "python" to use the Python version of the Zope security # machinery. This setting may impact performance but is useful # for debugging purposes. See also the "verbose-security" option # below. # # Default: C # # Example: # # security-policy-implementation python # Directive: skip-authentication-checking # # Description: # Set this directive to 'on' to cause Zope to skip checks related # to authentication, for servers which serve only anonymous content. # Only works if security-policy-implementation is 'C'. # # Default: off # # Example: # # skip-authentication-checking on # Directive: skip-ownership-checking # # Description: # Set this directive to 'on' to cause Zope to ignore ownership checking # when attempting to execute "through the web" code. By default, this # directive is on in order to prevent 'trojan horse' security problems # whereby a user with less privilege can cause a user with more # privilege to execute dangerous code. # # Default: off # # Example: # # skip-ownership-checking on # Directive: verbose-security # # Description: # By default, Zope reports authorization failures in a terse manner in # order to avoid revealing unnecessary information. This option # modifies the Zope security policy to report more information about # the reason for authorization failures. It's designed for debugging. # If you enable this option, you must also set the # 'security-policy-implementation' to 'python'. # # Default: off # # Example: # # security-policy-implementation python # verbose-security on # Directive: maximum-number-of-session-objects # # Description: # An integer value representing the number of items to use as a # "maximum number of subobjects" value of the # '/temp_folder/session_data' transient object container. # # Default: 1000 # # Example: # # maximum-number-of-session-objects 10000 # Directive: session-add-notify-script-path # # Description: # An optional fill Zope path name of a callable object to be set as the # "script to call on object addition" of the sessioN_data transient # object container created in the /temp_folder folder at startup. # # Default: unset # # Example: # # session-add-notify-script-path /scripts/add_notifier # Directive: session-delete-notify-script-path # # Description: # An optional fill Zope path name of a callable object to be set as the # "script to call on object deletion" of the sessioN_data transient # object container created in the /temp_folder folder at startup. # # Default: unset # # Example: # # session-delete-notify-script-path /scripts/del_notifier # Directive: session-timeout-minutes # # Description: # An integer value representing the number of minutes to be used as the # "data object timeout" of the '/temp_folder/session_data' transient # object container. # # Default: 20 # # Example: # # session-timeout-minutes 30 # Directive: session-resolution-seconds # # Description: # An integer value representing the number of seconds to be used as the # "timeout resolution" of the '/temp_folder/session_data' transient # object container. # # Default: 20 # # Example: # # session-resolution-seconds 60 # Directive: suppress-all-access-rules # # Description: # If this directive is set to on, no access rules in your Zope site # will be executed. This is useful if you "lock yourself out" of a # particular part of your site by setting an improper access rule. # # Default: off # # Example: # # suppress-all-access-rules on # Directive: suppress-all-site-roots # # Description: # If this directive is set to on, no site roots in your Zope site will # be effective. This is useful if you "lock yourself out" of a # particular part of your site by setting an improper site root. # # Default: off # # Example: # # suppress-all-site-roots on # Directive: database-quota-size # # Description: # Set this directive to an integer in bytes in order to place a hard # limit on the size which the default FileStorage-backed Zope database # can grow. Additions to the database will not be permitted once this # filesize is exceeded. # # Default: unset # # Example: # # database-quota-size 1000000 # Directive: read-only-database # # Description: # This causes the main Zope FileStorage-backed ZODB to be opened in # read-only mode. # # Default: off # # Example: # # read-only-database on # Directive: zeo-client-name # # Description: # If you want a persistent ZEO client cache which retains cache # contents across ClientStorage restarts, you need to define a # zeo-client-name. If you use ZEO and you don't set a # zeo-client-name, the client cache is stored in temporary files # which are removed when the ClientStorage shuts down. The value # of zeo-client-name is used to uniquely identify the local cache # files created if this Zope is a ZEO client. # # Default: unset # # Example: # # zeo-client-name zeo1 # Directives: logger # # Description: # This area should define one or more "logger" sections of the # names "access", "event", and "trace". The "access" logger logs # Zope server access. The "event" logger logs Zope event # information. The "trace" logger logs detailed server request # information (for debugging purposes only). Each logger section # may contain a "level" name/value pair which indicates the level # of logging detail to capture for this logger. The default level # is INFO. Level may be any of "CRITICAL", 'ERROR", WARN", "INFO", # "DEBUG", and "ALL". Each logger section may additionally contain # one or more "handler" sections which indicates a types of log # "handlers" (file, syslog, NT event log, etc) to be used for the # logger being defined. There are 5 types of handlers: logfile, # syslog, win32-eventlog, http-handler, email-notifier. Each # handler type has its own set of allowable subkeys which define # aspects of the handler. All handler sections also allow for the # specification of a "format" (the log message format string), a # "dateformat" (the log message format for date strings), and a # "level", which has the same semantics of the overall logger # level but overrides the logger's level for the handler it's # defined upon. XXXX much more detail necessary here # # Default: # # The access log will log to the file <instancehome>/log/Z2.log at # level INFO, the event log will log to the file # <instancehome>/log/event.log at level INFO, and the trace log # will not be written anywhere. <eventlog> level info <logfile> path $INSTANCE/log/event.log level info </logfile> </eventlog> <logger access> level WARN <logfile> path $INSTANCE/log/Z2.log format %(message)s </logfile> </logger> # <logger trace> # level WARN # <logfile> # path $INSTANCE/log/trace.log # format %(message)s # </logfile> # </logger> # Directive: conflict-error-log-level # # Description: # Specifies at which level conflict errors are logged. Conflict # errors, when occuring in small numbers, are a normal part of the # Zope optimistic transaction conflict resolution algorithms. They # are retried automatically a few times, and are therefore usually # not visible by the user. You can specify 'notset' if you don't # want them logged, or use any other logger level (see above). # # Default: info # # Example: # # conflict-error-log-level blather # Directive: warnfilter # # Description: # A section that allows you to define a warning filter. # The following keys are valid within a warnfilter section: # # action: one of the following strings: # # "error" turn matching warnings into exceptions # "ignore" never print matching warnings # "always" always print matching warnings # "default" print the first occurrence of matching warnings # for each location where the warning is issued # "module" print the first occurrence of matching warnings # for each module where the warning is issued # "once" print only the first occurrence of matching # warnings, regardless of location # # message: a string containing a regular expression that the # warning message must match (the match is compiled to # always be case-insensitive) # # category: a Python dotted-path classname (must be a subclass of # Warning) of which the warning category must be a subclass in # order to match # # module: a string containing a regular expression that the # module name must match (the match is compiled to be # case-sensitive) # # lineno: an integer that the line number where the warning # occurred must match, or 0 to match all line numbers # # All keys within a warnfilter section are optional. More than # one warnfilter section may be specified. # # Default: unset # # Example: # # <warnfilter> # action ignore # category exceptions.DeprecationWarning # </warnfilter> # Directive: max-listen-sockets # # Description: # The maximum number of sockets that ZServer will attempt to open # in order to service incoming connections. # # Default: 1000 # # Example: # # max-listen-sockets 500 # Directives: port-base # # Description: # Offset applied to the port numbers used for ZServer # configurations. For example, if the http-server port is 8080 and # the port-base is 1000, the HTTP server will listen on port 9080. # This makes it easy to change the complete set of ports used by a # Zope server process # # Default: # # 0 # # Example: # # port-base 1000 port-base 5000 # Directive: large-file-threshold # # Description: # Requests bigger than this size get saved into a temporary file # instead of being read completely into memory. # # Default: 512K # # Example: # # large-file-threshold 1Mb # Directive: default-zpublisher-encoding # # Description: # This controls what character set is used to encode unicode # data that reaches ZPublisher without any other specified encoding. # # Default: iso-8859-15 # # Example: # # default-zpublisher-encoding utf-8 # Directives: servers # # Description: # A set of sections which allow the specification of Zope's various # ZServer servers. 7 different server types may be defined: # http-server, ftp-server, webdav-source-server, persistent-cgi, # fast-cgi, monitor-server, and icp-server. If no servers are # defined, the default servers are used. # # Ports may be specified using the 'address' directive either in simple # form (80) or in complex form including hostname 127.0.0.1:80. If the # hostname is "left off", the default-ip-address is used as the hostname. # # Port numbers are offset by the setting of port-base. # # To run the monitor-server an emergency user must be defined # (through an 'access' file). # # Default: # # An HTTP server starts on port 8080. <http-server> # valid keys are "address" and "force-connection-close" address 8080 # force-connection-close on </http-server> # Examples: # # <ftp-server> # # valid key is "address" # address 8021 # </ftp-server> # # <webdav-source-server> # # valid keys are "address" and "force-connection-close" # address 1980 # force-connection-close off # </webdav-source-server> # # <persistent-cgi> # # valid key is "path" # path somefile # </persistent-cgi> # # <fast-cgi> # # valid key is "address"; the address may be hostname:port, port, # # or a path for a Unix-domain socket # address somefile # </fast-cgi> # # <monitor-server> # # valid keys are "address" # address 8099 # </monitor-server> # # <icp-server> # # valid key is "address" # address 888 # </icp-server> # Database (zodb_db) section # # Description: # A database section allows the definition of custom database and # storage types. More than one zodb_db section can be defined. # # Default: unset. # IMPORTANT: At least one database with a mount-point of "/" # must be specified for Zope to start properly. <zodb_db main> # Main FileStorage database <filestorage> path $INSTANCE/var/Data.fs </filestorage> mount-point / </zodb_db> <zodb_db temporary> # Temporary storage database (for sessions) <temporarystorage> name temporary storage for sessioning </temporarystorage> mount-point /temp_folder container-class Products.TemporaryFolder.TemporaryContainer </zodb_db> # Other storage examples # # ZEO client storage: # # <zodb_db main> # mount-point / # # ZODB cache, in number of objects # cache-size 5000 # <zeoclient> # server localhost:8100 # storage 1 # name zeostorage # var $INSTANCE/var # # ZEO client cache, in bytes # cache-size 20MB # # Uncomment to have a persistent disk cache # #client zeo1 # </zeoclient> # </zodb_db> # Product configuration (product-config) section(s) # # Description: # Add-on products may need to allow the user to specify policy / # configuration. Such policies may be expressed as a set of # name-value pairs, grouped into a named section (there may # be many such sections, typically one per product). # These sections will be captured in an attribute, 'product_config' # of the top-level config object, under the key corresponding to # the section name. E.g., the sample section below would be # parsed into a dict, {'bar': 'baz'}, available as # config.product_config['foo'] # # Products may also register their own section types, extending # # # Example: # # 1. Simple "bag of strings" section: # # <product-config foo> # bar baz # </product-config> # # 2. Custom section type # # Products/Foo/component.xml: # # <component> # <description> # Some product-specific hackery. # </description> # <sectiontype name="myproduct" implements="zope.product.base"> # <description> # Product-specific configuration. # </description> # <key name="foo" /> # </sectiontype> # </component> # # In zope.conf: # # %import Products.Foo # # <myproduct bar> # foo qux # </myproduct>

4 7

Re: [Zope] migration from 2.9.1 to 2.9.4
by Brian Sullivan 17 Nov '06

17 Nov '06

On 11/17/06, Andreas Jung <lists(a)zopyx.com> wrote: > Should be fixed in 2.9.5 or 2.9.6 (unreleased, grab the related file > from the Subversion if necessary). > OK -- any idea if a 2.9.5/2.9.6 Windows installer is in the works -- I am unsure of how to install on Windows from the .tgz file.

1 0

migration from 2.9.1 to 2.9.4
by Brian Sullivan 17 Nov '06

17 Nov '06

I am having some problems migrating from Zope 2.9.1 to Zope 2.9.4 on my Windows 2003 based Zope setup. Installation of 2.9.4 goes normally -- both servers (2.9.1 and 2.9.4) seem to be running happily (on different ports). My first strategy in migration was to copy the data.fs from 2.9.1 to 2.9.4. That seems to fail as certain "directories" when viewing is attempted from the 2.9.4 ZMI exhibit the following error: Traceback (innermost last): Module ZPublisher.Publish, line 106, in publish Module ZPublisher.BaseRequest, line 275, in traverse Module ZPublisher.BeforeTraverse, line 108, in __call__ Module logging, line 999, in error TypeError: _log() got an unexpected keyword argument 'error' My next strategy was to export to .zexp the critical material from 2.9.1 and import into 2.9.4. All appears to go well -- but attempts to access the imported material from the 2.9.4 ZMI fails with the same message. Any idea what is going on here? Any other strategies for migrating that anyone can think of or things to look at?

4 4

Checking in pages, scripts, and sql methods to SVN
by Sinang, Danny 17 Nov '06

17 Nov '06

Hello, Is there a Zope product out there that would allow me to check into SVN my Zope objects (i.e. TAL pages, Python scripts, and ZSQLMethods) ? If not, can anyone here show me some skeleton code to : 1. Enumerate these objects 2. Reference them as files so I can programmatically check them into SVN ? Regards, Danny

5 4