Hi, im using plone4.3. the problem is that i am trying to upload an image in the body.
i click on add image from TinyMCe but when i choose to upload and image nothing happens it takes the pic but the ok button remains fade due which the pic can be shown in the body.
secondly i have added carousel in it. i have added one pic successfully but does not allow me to add second pic. only one pic is available on front end.
Please help.
the long error 
`
Here is the full error message:
Display traceback as text
Traceback (innermost last):
Module ZPublisher.Publish, line 138, in publish
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module Products.CMFPlone.FactoryTool, line 478, in call
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module Products.CMFFormController.FSControllerPageTemplate, line 91, in call
Module Products.CMFFormController.BaseControllerPageTemplate, line 28, in _call
Module Products.CMFFormController.ControllerBase, line 232, in getNext
Module Products.CMFFormController.Actions.TraverseTo, line 38, in call
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module Products.CMFFormController.FSControllerPythonScript, line 107, in call
Module Products.CMFFormController.ControllerBase, line 232, in getNext
Module Products.CMFFormController.Actions.TraverseTo, line 38, in call
Module ZPublisher.mapply, line 77, in mapply
Module ZPublisher.Publish, line 48, in call_object
Module Products.CMFFormController.FSControllerPythonScript, line 105, in call
Module Products.CMFFormController.Script, line 145, in call
Module Products.CMFCore.FSPythonScript, line 127, in call
Module Shared.DC.Scripts.Bindings, line 322, in call
Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec
Module Products.PythonScripts.PythonScript, line 344, in _exec
Module script, line 1, in content_edit
<FSControllerPythonScript at /Biztech-Resources/content_edit used for /Biztech-Resources/portal_factory/Image/image.2016-05-27.3177348243>
Line 1
Module Products.CMFCore.FSPythonScript, line 127, in call
Module Shared.DC.Scripts.Bindings, line 322, in call
Module Shared.DC.Scripts.Bindings, line 359, in _bindAndExec
Module Products.PythonScripts.PythonScript, line 344, in _exec
Module script, line 8, in content_edit_impl
<FSPythonScript at /Biztech-Resources/content_edit_impl used for /Biztech-Resources/portal_factory/Image/image.2016-05-27.3177348243>
Line 8
Module Products.CMFPlone.FactoryTool, line 321, in doCreate
Module Products.CMFCore.PortalFolder, line 292, in invokeFactory
Module Products.CMFCore.TypesTool, line 833, in constructContent
Module Products.CMFCore.TypesTool, line 311, in constructInstance
Module Products.CMFCore.TypesTool, line 552, in _constructInstance
Module plone.app.blob.content, line 71, in addATBlobImage
Module plone.app.blob.content, line 60, in addATBlob
Module Products.ATContentTypes.content.base, line 122, in initializeArchetype
Module Products.Archetypes.BaseObject, line 439, in setDefaults
Module Products.Archetypes.Schema, line 498, in setDefaults
Module Products.Archetypes.utils, line 130, in mapply
Module archetypes.schemaextender.field, line 40, in mutator
Module plone.app.blob.subtypes.image, line 21, in set
Module plone.app.blob.field, line 262, in set
Module transaction._manager, line 101, in savepoint
Module transaction._transaction, line 260, in savepoint
Module transaction._transaction, line 257, in savepoint
Module transaction._transaction, line 690, in init
Module ZODB.Connection, line 1123, in savepoint
Module ZODB.Connection, line 623, in _commit
Module ZODB.Connection, line 669, in _store_objects
Module ZODB.blob, line 286, in _uncommitted
Module ZODB.blob, line 271, in _create_uncommitted_file
Module ZODB.utils, line 224, in mktemp
Module tempfile, line 308, in mkstemp
Module tempfile, line 239, in _mkstemp_inner
OSError: [Errno 2] No such file or directory: '/opt/plone/zeocluster/var/blobstorage/tmp/tmpUhIUw4'`
Looks like you might have a zeoserver configuration issue.
Can you share your zeoserver and client buildout configurations? Maybe /opt/plone/zeocluster/var/blobstorage/tmp is not created or something is misconfigured.
ya sure i can.
`############################################
#
# Buildout Configuration File for Plone
# -------------------------------------
#
# ALWAYS back up all Plone/Zope data and components
# before changing configuration.
#
# Running "bin/buildout" will update your installation,
# installing missing components as necessary.
#
# This will update the add-on products you've added in the eggs= lines.
# This will not, however, upgrade Plone itself (or anything else you've
# pinned with a version specification). To upgrade Plone itself, see the
# comments in "Plone Component Versions".
#
# Tutorial instructions for using zc.buildout for
# configuration management are available at:
# http://plone.org/documentation/tutorial/buildout
# Full details at http://pypi.python.org/pypi/zc.buildout
#
############################################
[buildout]
############################################
# Plone Component Versions
# ------------------------
# This version of the Unified Installer has the components of Plone 4
# preloaded so that it can install without an Internet connection.
# If you want to update, uncomment the "http://..." line below,
# edit it to point to the current version URL, comment out the
# "versions.cfg" line and run "bin/buildout" while attached to the
# Internet. Generally, you only want to do that as part of a planned migration.
# Note that if you are updating components, you should also check the versions
# section at the end of this file, since recipes or components other than
# those of Zope and Plone may need updating at the same time.
#
extends =
base.cfg
versions.cfg
# http://dist.plone.org/release/4.3.6/versions.cfg
# If you change your Plone version, you'll also need to update
# the repository link below.
find-links +=
http://dist.plone.org/release/4.3.6
# If you try to start Zope as root, it will change user id to run as
# the effective user specified here. This user id must own the var directory
# of your buildout.
effective-user = plone_daemon
# This user will own the rest of the installation, and should be used to
# run buildout.
buildout-user = plone_buildout
# A flag to tell the Unified Installer whether or not to document sudo use.
need-sudo = yes
############################################
# Eggs
# ----
# Add an indented line to the eggs section for any Python
# eggs or packages you wish to include in your Plone instance.
#
# Note that versions may be specified here or in the [versions]
# section below. You should always specify versions that you know
# are compatible with the Plone release and at an acceptable
# development level.
#
# If you update to a later version of Plone, remove the hotfix.
#
eggs =
Plone
Pillow
Products.Carousel
############################################
# ZCML Slugs
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. This is increasingly rare.
zcml =
# plone.reload
############################################
# Development Eggs
# ----------------
# You can use paster to create "development eggs" to
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.
#
# Provide the *paths* to the eggs you are developing here:
develop =
# src/my.package
############################################
# var Directory
# -------------
# Sets the target directory for the "var" components of the install such as
# database and log files.
#
var-dir=${buildout:directory}/var
############################################
# Backup Directory
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but ideally
# this should be on a separate volume or backup server.
#
backups-dir=${buildout:var-dir}
############################################
# Initial User
# ------------
# This is the user id and password that will be used to create the initial
# user id that will allow you to log in and create a Plone site. This only
# sets the initial password; it will not allow you to change an already
# existing password. If you change the admin password via the web interface,
# the one below will no longer be valid.
# If you find yourself locked out of your Zope/Python installation, you may
# add an emergency user via "bin/plonectl adduser".
user=admin:admin
############################################
# Debug Options
# -------------
# Start Zope/Plone instances in "fg" mode to turn on debug mode;
# this will dramatically slow Plone.
#
# Add-on developers should turn deprecation warnings on
deprecation-warnings = off
# change verbose-security to "on" for useful security errors while developing
verbose-security = off
############################################
# Parts Specification
#--------------------
# Specifies the components that should be included in the buildout.
# Most are defined in the base.cfg extension; you may add your
# own if you need them at the end of this file.
parts =
zeoserver
client1
client2
backup
zopepy
unifiedinstaller
precompiler
setpermissions
############################################
# Major Parts
# ----------------------
# These common parts make use of sane base settings from
# base.cfg. To customize a part, just add whatever options
# you need. Read base.cfg for common settings.
[zeoserver]
<= zeoserver_base
recipe = plone.recipe.zeoserver
zeo-address = 127.0.0.1:8100
[client1]
<= client_base
recipe = plone.recipe.zope2instance
zeo-address = ${zeoserver:zeo-address}
http-address = 8080
[client2]
<= client_base
recipe = plone.recipe.zope2instance
zeo-address = ${zeoserver:zeo-address}
http-address = 8081
############################################
# Versions Specification
# ----------------------
# Version information supplied here will "pin" Python packages to a particular
# version number, even when you use the "newest" flag running buildout.
# Specifying versions for all packages is a good idea and can prevent
# accidental changes when you add new packages to your buildout.
# Note that versions specified here will override those specified earlier
# in the configuration, including those from the Plone and Zope version
# config files.
#
[versions]
buildout.sanitycheck = 1.0b1
Cheetah = 2.2.1
collective.recipe.backup = 2.20
Pillow = 2.6.1
plone.recipe.command = 1.1
plone.recipe.unifiedinstaller = 4.3.2
Products.DocFinderTab = 1.0.5
setuptools = 7.0
zc.buildout = 2.2.5
ZopeSkel = 2.21.2
zopeskel.dexterity = 1.5.4.1
zopeskel.diazotheme = 1.1
Can you put it in a code block so it doesn't format all crazy?
Other things:
blobstorage has nothing. its empty.
############################################
Buildout Configuration File for Plone
-------------------------------------
ALWAYS back up all Plone/Zope data and components
before changing configuration.
Running "bin/buildout" will update your installation,
installing missing components as necessary.
This will update the add-on products you've added in the eggs= lines.
This will not, however, upgrade Plone itself (or anything else you've
pinned with a version specification). To upgrade Plone itself, see the
comments in "Plone Component Versions".
Tutorial instructions for using zc.buildout for
configuration management are available at:
http://plone.org/documentation/tutorial/buildout
Full details at zc.buildout · PyPI
############################################
[buildout]
############################################Plone Component Versions
------------------------
This version of the Unified Installer has the components of Plone 4
preloaded so that it can install without an Internet connection.
If you want to update, uncomment the "http://..." line below,
edit it to point to the current version URL, comment out the
"versions.cfg" line and run "bin/buildout" while attached to the
Internet. Generally, you only want to do that as part of a planned migration.
Note that if you are updating components, you should also check the versions
section at the end of this file, since recipes or components other than
those of Zope and Plone may need updating at the same time.
extends =
base.cfg
versions.cfg
# http://dist.plone.org/release/4.3.6/versions.cfg
# If you change your Plone version, you'll also need to update
# the repository link below.
find-links +=
http://dist.plone.org/release/4.3.6
# If you try to start Zope as root, it will change user id to run as
# the effective user specified here. This user id must own the var directory
# of your buildout.
effective-user = plone_daemon
# This user will own the rest of the installation, and should be used to
# run buildout.
buildout-user = plone_buildout
# A flag to tell the Unified Installer whether or not to document sudo use.
need-sudo = yes
############################################
# Eggs
# ----
# Add an indented line to the eggs section for any Python
# eggs or packages you wish to include in your Plone instance.
#
# Note that versions may be specified here or in the [versions]
# section below. You should always specify versions that you know
# are compatible with the Plone release and at an acceptable
# development level.
#
# If you update to a later version of Plone, remove the hotfix.
#
eggs =
Plone
Pillow
Products.Carousel
############################################
# ZCML Slugs
# ----------
# Some eggs need ZCML slugs to tell Zope to
# use them. This is increasingly rare.
zcml =
# plone.reload
############################################
# Development Eggs
# ----------------
# You can use paster to create "development eggs" to
# develop new products/themes. Put these in the src/
# directory.
# You will also need to add the egg names in the
# eggs section above, and may also need to add them
# to the zcml section.
#
# Provide the *paths* to the eggs you are developing here:
develop =
# src/my.package
############################################
# var Directory
# -------------
# Sets the target directory for the "var" components of the install such as
# database and log files.
#
var-dir=${buildout:directory}/var
############################################
# Backup Directory
# ----------------
# Sets the target directory for the bin/backup and bin/snapshotbackup
# commands. Default is inside this project's var directory, but ideally
# this should be on a separate volume or backup server.
#
backups-dir=${buildout:var-dir}
############################################
# Initial User
# ------------
# This is the user id and password that will be used to create the initial
# user id that will allow you to log in and create a Plone site. This only
# sets the initial password; it will not allow you to change an already
# existing password. If you change the admin password via the web interface,
# the one below will no longer be valid.
# If you find yourself locked out of your Zope/Python installation, you may
# add an emergency user via "bin/plonectl adduser".
user=admin:admin
############################################
# Debug Options
# -------------
# Start Zope/Plone instances in "fg" mode to turn on debug mode;
# this will dramatically slow Plone.
#
# Add-on developers should turn deprecation warnings on
deprecation-warnings = off
# change verbose-security to "on" for useful security errors while developing
verbose-security = off
############################################
# Parts Specification
#--------------------
# Specifies the components that should be included in the buildout.
# Most are defined in the base.cfg extension; you may add your
# own if you need them at the end of this file.
parts =
zeoserver
client1
client2
backup
zopepy
unifiedinstaller
precompiler
setpermissions
############################################
# Major Parts
# ----------------------
# These common parts make use of sane base settings from
# base.cfg. To customize a part, just add whatever options
# you need. Read base.cfg for common settings.
[zeoserver]
<= zeoserver_base
recipe = plone.recipe.zeoserver
zeo-address = 127.0.0.1:8100
[client1]
<= client_base
recipe = plone.recipe.zope2instance
zeo-address = ${zeoserver:zeo-address}
http-address = 8080
[client2]
<= client_base
recipe = plone.recipe.zope2instance
zeo-address = ${zeoserver:zeo-address}
http-address = 8081
############################################
# Versions Specification
# ----------------------
# Version information supplied here will "pin" Python packages to a particular
# version number, even when you use the "newest" flag running buildout.
# Specifying versions for all packages is a good idea and can prevent
# accidental changes when you add new packages to your buildout.
# Note that versions specified here will override those specified earlier
# in the configuration, including those from the Plone and Zope version
# config files.
#
[versions]
buildout.sanitycheck = 1.0b1
Cheetah = 2.2.1
collective.recipe.backup = 2.20
Pillow = 2.6.1
plone.recipe.command = 1.1
plone.recipe.unifiedinstaller = 4.3.2
Products.DocFinderTab = 1.0.5
setuptools = 7.0
zc.buildout = 2.2.5
ZopeSkel = 2.21.2
zopeskel.dexterity = 1.5.4.1
zopeskel.diazotheme = 1.1
base.cfg
######################################################
# Base Configuration; this provides sane defaults
# for commonly used parts.
# ---------------------------------------------------
#
# Buildout instructions in this file are
# usually only changed by experienced developers.
#
# Beyond here there be dragons!
[buildout]
eggs-directory=../buildout-cache/eggs
download-cache=../buildout-cache/downloads
# Don't download new things unless needed to satisfy dependencies.
# Override this on the command line with the "-n" flag.
newest = false
# pick final releases over newer development releases
prefer-final = true
show-picked-versions = true
versions = versions
# Add additional egg download sources here. dist.plone.org contains archives
# of Plone packages.
find-links =
http://dist.plone.org
http://download.zope.org/ppix/
http://download.zope.org/distribution/
http://effbot.org/downloads
# buildout.sanitycheck makes sure you're not running buildout
# as root.
extensions =
############################################
# Environment Variables
# ---------------------
# Some of the behavior of your Zope/Plone instances are controlled with OS
# environment variables. You may set those here in a key / value format.
# Some common settings:
# * TZ allows you to set a time zone for systems where it's not
# automatically available.
# * zope_i18n_compile_mo_files allows for automatic compilation of
# missing translation files (may slow startup).
# * zope_i18n_allowed_languages allows you to limit the available
# translations.
# * PYTHON_EGG_CACHE determines where zipped python packages are unpacked
# for use.
# * PYTHONHASHSEED determines initial seed for hashes. "random" causes a
# pseudo-random value is used to seed the hashes of str, bytes and datetime
# objects.
environment-vars =
zope_i18n_compile_mo_files true
PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs
# PYTHONHASHSEED random
# TZ US/Eastern
# zope_i18n_allowed_languages en es de fr
[instance_base]
# Use this section to install and configure a Zope operating
# instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
# The line below sets only the initial password. It will not change an
# existing password.
user = ${buildout:user}
# if we try to start as root, Zope will switch to the user below
effective-user = ${buildout:effective-user}
# change debug-mode to "on" to run in development mode.
# starting in foreground (fg) mode is a better way to do this.
debug-mode = off
# change verbose-security to "on" for detailed security
# errors while developing
verbose-security = ${buildout:verbose-security}
# change deprecation-warnings to "on" to get log warnings
# for deprecated usages.
deprecation-warnings = ${buildout:deprecation-warnings}
# storage locations
var = ${buildout:var-dir}
blob-storage = ${:var}/blobstorage
# Comment the next four lines out if you don't need
# automatic log rotation for event and access logs.
event-log-max-size = 5 MB
event-log-old-files = 5
access-log-max-size = 20 MB
access-log-old-files = 5
# If you want Zope to know about any additional eggs, list them here.
# e.g. eggs = ${buildout:eggs} my.package
eggs =
${buildout:eggs}
# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml = ${buildout:zcml}
products = ${buildout:directory}/products
# You may also control the environment variables for the instance.
environment-vars = ${buildout:environment-vars}
[zeoserver_base]
# Use this section to install and configure a Zope
# Enterprise Objects server.
# For options see http://pypi.python.org/pypi/plone.recipe.zeoserver
#
# If we try to start as root, Zope will switch to the user below
effective-user = ${buildout:effective-user}
# Set storage
var = ${buildout:var-dir}
blob-storage = ${buildout:var-dir}/blobstorage
# Put the log, pid and socket files in var/zeoserver
zeo-log = ${buildout:var-dir}/zeoserver/zeoserver.log
pid-file = ${buildout:var-dir}/zeoserver/zeoserver.pid
socket-name = ${buildout:var-dir}/zeoserver/zeo.zdsock
[client_base]
# Use this section to install and configure a ZEO client
# instance.
# For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
# The line below sets only the initial password. It will not change an
# existing password.
user = ${buildout:user}
# if we try to start as root, Zope will switch to the user below
effective-user = ${buildout:effective-user}
# change debug-mode to "on" to run in development mode.
# starting in foreground (fg) mode is a better way to do this.
debug-mode = off
# change verbose-security to "on" for detailed security
# errors while developing
verbose-security = ${buildout:verbose-security}
# change deprecation-warnings to "on" to get log warnings
# for deprecated usages.
deprecation-warnings = ${buildout:deprecation-warnings}
# base locations
var = ${buildout:var-dir}
blob-storage = ${:var}/blobstorage
# Comment the next four lines out if you don't need
# automatic log rotation for event and access logs.
event-log-max-size = 5 MB
event-log-old-files = 5
access-log-max-size = 20 MB
access-log-old-files = 5
# If you want Zope to know about any additional eggs, list them here.
# e.g. eggs = ${buildout:eggs} my.package
eggs =
${buildout:eggs}
# If you want to register ZCML slugs for any packages, list them here.
# e.g. zcml = my.package my.other.package
zcml = ${buildout:zcml}
products = ${buildout:directory}/products
# You may also control the environment variables for the instance.
environment-vars = ${buildout:environment-vars}
zeo-client = true
# shared blobs are much faster if we're on the same server.
# if not, turn it off.
shared-blob = on
# defer early binding to port; may improve load balancer behavior on restarts
http-fast-listen = off
# Put the log, pid, lock files in var/client1
event-log = ${buildout:var-dir}/${:_buildout_section_name_}/event.log
z2-log = ${buildout:var-dir}/${:_buildout_section_name_}/Z2.log
pid-file = ${buildout:var-dir}/${:_buildout_section_name_}/${:_buildout_section_name_}.pid
lock-file = ${buildout:var-dir}/${:_buildout_section_name_}/${:_buildout_section_name_}.lock
[repozo]
# This recipe builds the repozo script for non-zeo installations.
recipe = zc.recipe.egg
eggs = ZODB3
scripts = repozo
[backup]
# This recipe builds the backup, restore and snapshotbackup commands.
# For options see http://pypi.python.org/pypi/collective.recipe.backup
recipe = collective.recipe.backup
location = ${buildout:backups-dir}/backups
blobbackuplocation = ${buildout:backups-dir}/blobstoragebackups
snapshotlocation = ${buildout:backups-dir}/snapshotbackups
blobsnapshotlocation = ${buildout:backups-dir}/blobstoragesnapshots
datafs = ${buildout:var-dir}/filestorage/Data.fs
blob-storage = ${buildout:var-dir}/blobstorage
[setpermissions]
# This recipe is used to set permissions for root mode installs
# For options see http://pypi.python.org/pypi/plone.recipe.command
recipe = plone.recipe.command
command =
# Dummy references to force this to execute after referenced parts
echo ${backup:location} ${unifiedinstaller:need-sudo} > /dev/null
chmod 600 .installed.cfg
# Make sure anything we've created in var is r/w by our group
find ${buildout:var-dir} -type d -exec chmod 770 {} \; 2> /dev/null
find ${buildout:var-dir} -type f -exec chmod 660 {} \; 2> /dev/null
# but not the egg cache
chmod -R g-w ${buildout:directory}/var/.python-eggs
find ${buildout:backups-dir} -type d -exec chmod 770 {} \; 2> /dev/null
find ${buildout:backups-dir} -type f -exec chmod 660 {} \; 2> /dev/null
chmod 754 ${buildout:directory}/bin/*
update-command = ${:command}
[zopepy]
# installs a zopepy python interpreter that runs with your
# full Zope environment
recipe = zc.recipe.egg
eggs = ${buildout:eggs}
interpreter = zopepy
scripts = zopepy
[unifiedinstaller]
# This recipe installs the plonectl script and a few other convenience
# items.
# For options see http://pypi.python.org/pypi/plone.recipe.unifiedinstaller
recipe = plone.recipe.unifiedinstaller
user = ${buildout:user}
effective-user = ${buildout:effective-user}
buildout-user = ${buildout:buildout-user}
need-sudo = ${buildout:need-sudo}
[precompiler]
# This recipe is used in production installs to compile
# .py and .po files so that the daemon doesn't try to do it.
# For options see http://pypi.python.org/pypi/plone.recipe.precompiler
recipe = plone.recipe.precompiler
eggs = ${buildout:eggs}
compile-mo-files = true
extra-paths = ${buildout:directory}/products
any idea so far???? 
I don't think you ever pasted your base.cfg file. I see buildout.cfg in both posts.
I'd double check permissions on /opt/plone/zeocluster/var and /opt/plone/zeocluster/var/blobstorage specifically.
here you go with the base file
> ######################################################
> # Base Configuration; this provides sane defaults
> # for commonly used parts.
> # ---------------------------------------------------
> #
> # Buildout instructions in this file are
> # usually only changed by experienced developers.
> #
> # Beyond here there be dragons!
> [buildout]
> eggs-directory=../buildout-cache/eggs
> download-cache=../buildout-cache/downloads
> # Don't download new things unless needed to satisfy dependencies.
> # Override this on the command line with the "-n" flag.
> newest = false
> # pick final releases over newer development releases
> prefer-final = true
> show-picked-versions = true
> versions = versions
> # Add additional egg download sources here. dist.plone.org contains archives
> # of Plone packages.
> find-links =
> http://dist.plone.org
> http://download.zope.org/ppix/
> http://download.zope.org/distribution/
> http://effbot.org/downloads
> # buildout.sanitycheck makes sure you're not running buildout
> # as root.
> extensions =
>
> ############################################
> # Environment Variables
> # ---------------------
> # Some of the behavior of your Zope/Plone instances are controlled with OS
> # environment variables. You may set those here in a key / value format.
> # Some common settings:
> # * TZ allows you to set a time zone for systems where it's not
> # automatically available.
> # * zope_i18n_compile_mo_files allows for automatic compilation of
> # missing translation files (may slow startup).
> # * zope_i18n_allowed_languages allows you to limit the available
> # translations.
> # * PYTHON_EGG_CACHE determines where zipped python packages are unpacked
> # for use.
> # * PYTHONHASHSEED determines initial seed for hashes. "random" causes a
> # pseudo-random value is used to seed the hashes of str, bytes and datetime
> # objects.
> environment-vars =
> zope_i18n_compile_mo_files true
> PYTHON_EGG_CACHE ${buildout:directory}/var/.python-eggs
> # PYTHONHASHSEED random
> # TZ US/Eastern
> # zope_i18n_allowed_languages en es de fr
> [instance_base]
> # Use this section to install and configure a Zope operating
> # instance.
> # For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
> # The line below sets only the initial password. It will not change an
> # existing password.
> user = ${buildout:user}
> # if we try to start as root, Zope will switch to the user below
> effective-user = ${buildout:effective-user}
> # change debug-mode to "on" to run in development mode.
> # starting in foreground (fg) mode is a better way to do this.
> debug-mode = off
> # change verbose-security to "on" for detailed security
> # errors while developing
> verbose-security = ${buildout:verbose-security}
> # change deprecation-warnings to "on" to get log warnings
> # for deprecated usages.
> deprecation-warnings = ${buildout:deprecation-warnings}
> # storage locations
> var = ${buildout:var-dir}
> blob-storage = ${:var}/blobstorage
> # Comment the next four lines out if you don't need
> # automatic log rotation for event and access logs.
> event-log-max-size = 5 MB
> event-log-old-files = 5
> access-log-max-size = 20 MB
> access-log-old-files = 5
> # If you want Zope to know about any additional eggs, list them here.
> # e.g. eggs = ${buildout:eggs} my.package
> eggs =
> ${buildout:eggs}
> # If you want to register ZCML slugs for any packages, list them here.
> # e.g. zcml = my.package my.other.package
> zcml = ${buildout:zcml}
> products = ${buildout:directory}/products
> # You may also control the environment variables for the instance.
> environment-vars = ${buildout:environment-vars}
> [zeoserver_base]
> # Use this section to install and configure a Zope
> # Enterprise Objects server.
> # For options see http://pypi.python.org/pypi/plone.recipe.zeoserver
> #
> # If we try to start as root, Zope will switch to the user below
> effective-user = ${buildout:effective-user}
> # Set storage
> var = ${buildout:var-dir}
> blob-storage = ${buildout:var-dir}/blobstorage
> # Put the log, pid and socket files in var/zeoserver
> zeo-log = ${buildout:var-dir}/zeoserver/zeoserver.log
> pid-file = ${buildout:var-dir}/zeoserver/zeoserver.pid
> socket-name = ${buildout:var-dir}/zeoserver/zeo.zdsock
> [client_base]
> # Use this section to install and configure a ZEO client
> # instance.
> # For options see http://pypi.python.org/pypi/plone.recipe.zope2instance
> # The line below sets only the initial password. It will not change an
> # existing password.
> user = ${buildout:user}
> # if we try to start as root, Zope will switch to the user below
> effective-user = ${buildout:effective-user}
> # change debug-mode to "on" to run in development mode.
> # starting in foreground (fg) mode is a better way to do this.
> debug-mode = off
> # change verbose-security to "on" for detailed security
> # errors while developing
> verbose-security = ${buildout:verbose-security}
> # change deprecation-warnings to "on" to get log warnings
> # for deprecated usages.
> deprecation-warnings = ${buildout:deprecation-warnings}
> # base locations
> var = ${buildout:var-dir}
> blob-storage = ${:var}/blobstorage
> # Comment the next four lines out if you don't need
> # automatic log rotation for event and access logs.
> event-log-max-size = 5 MB
> event-log-old-files = 5
> access-log-max-size = 20 MB
> access-log-old-files = 5
> # If you want Zope to know about any additional eggs, list them here.
> # e.g. eggs = ${buildout:eggs} my.package
> eggs =
> ${buildout:eggs}
> # If you want to register ZCML slugs for any packages, list them here.
> # e.g. zcml = my.package my.other.package
> zcml = ${buildout:zcml}
> products = ${buildout:directory}/products
> # You may also control the environment variables for the instance.
> environment-vars = ${buildout:environment-vars}
> zeo-client = true
> # shared blobs are much faster if we're on the same server.
> # if not, turn it off.
> shared-blob = on
> # defer early binding to port; may improve load balancer behavior on restarts
> http-fast-listen = off
> # Put the log, pid, lock files in var/client1
> event-log = ${buildout:var-dir}/${:_buildout_section_name_}/event.log
> z2-log = ${buildout:var-dir}/${:_buildout_section_name_}/Z2.log
> pid-file = ${buildout:var-dir}/${:_buildout_section_name_}/${:_buildout_section_name_}.pid
> lock-file = ${buildout:var-dir}/${:_buildout_section_name_}/${:_buildout_section_name_}.lock
> [repozo]
> # This recipe builds the repozo script for non-zeo installations.
> recipe = zc.recipe.egg
> eggs = ZODB3
> scripts = repozo
> [backup]
> # This recipe builds the backup, restore and snapshotbackup commands.
> # For options see http://pypi.python.org/pypi/collective.recipe.backup
> recipe = collective.recipe.backup
> location = ${buildout:backups-dir}/backups
> blobbackuplocation = ${buildout:backups-dir}/blobstoragebackups
> snapshotlocation = ${buildout:backups-dir}/snapshotbackups
> blobsnapshotlocation = ${buildout:backups-dir}/blobstoragesnapshots
> datafs = ${buildout:var-dir}/filestorage/Data.fs
> blob-storage = ${buildout:var-dir}/blobstorage
> [setpermissions]
> # This recipe is used to set permissions for root mode installs
> # For options see http://pypi.python.org/pypi/plone.recipe.command
> recipe = plone.recipe.command
> command =
> # Dummy references to force this to execute after referenced parts
> echo ${backup:location} ${unifiedinstaller:need-sudo} > /dev/null
> chmod 600 .installed.cfg
> # Make sure anything we've created in var is r/w by our group
> find ${buildout:var-dir} -type d -exec chmod 770 {} \; 2> /dev/null
> find ${buildout:var-dir} -type f -exec chmod 660 {} \; 2> /dev/null
> # but not the egg cache
> chmod -R g-w ${buildout:directory}/var/.python-eggs
> find ${buildout:backups-dir} -type d -exec chmod 770 {} \; 2> /dev/null
> find ${buildout:backups-dir} -type f -exec chmod 660 {} \; 2> /dev/null
> chmod 754 ${buildout:directory}/bin/*
> update-command = ${:command}
> [zopepy]
> # installs a zopepy python interpreter that runs with your
> # full Zope environment
> recipe = zc.recipe.egg
> eggs = ${buildout:eggs}
> interpreter = zopepy
> scripts = zopepy
> [unifiedinstaller]
> # This recipe installs the plonectl script and a few other convenience
> # items.
> # For options see http://pypi.python.org/pypi/plone.recipe.unifiedinstaller
> recipe = plone.recipe.unifiedinstaller
> user = ${buildout:user}
> effective-user = ${buildout:effective-user}
> buildout-user = ${buildout:buildout-user}
> need-sudo = ${buildout:need-sudo}
> [precompiler]
> # This recipe is used in production installs to compile
> # .py and .po files so that the daemon doesn't try to do it.
> # For options see http://pypi.python.org/pypi/plone.recipe.precompiler
> recipe = plone.recipe.precompiler
> eggs = ${buildout:eggs}
> compile-mo-files = true
> extra-paths = ${buildout:directory}/products