Originally from del.icio.us/tag/plone by
Originally from del.icio.us/tag/plone by DoctorEternal
Originally from del.icio.us/tag/plone by naro
I’ve updated the experimental Plone 3.0 setuptools distribution and
ploneenv today a bit and fixed some bugs along the way.
Here are some small recipes that show you how ploneenv works, and how
you can make use of it.
A requirement for all of these recipes is that you have ploneenv
installed, which you can install like this:
sudo easy_install ploneenv
The recipes will also assume that you have two shell variables set.
One is MKZO, the path to the mkzopeinstance.py script of your
Zope 2.10 installation. The other is INSTANCE_HOME, the folder
where you want your Zope instance to go into. This is an example of
setting those variables:
MKZO=~/lib/Zope-2.10/bin/mkzopeinstance.py INSTANCE_HOME=~/myplone3.0
You want to create a pure Zope instance, in which you can use tools
like easy_install and yolk to manage Python packages and install
Products the usual way.
Calling ploneenv with –no-dependencies will create a blank Zope
instance that’s also a workingenv. This method of installation is
perfectly compatible with Plone 2.5 or other Products!
To install packages from the Cheese Shop, you must first activate
the environment and then use easy_install, like this:
source $INSTANCE_HOME/bin/activate easy_install yolk
This will install yolk, a tool that provides a lot of useful functions
for querying the metadata of installed setuptools packages and
querying the Cheese Shop. For example, if you want a list of all
packages that are installed in your Zope instance, run:
yolk -l
You want to try out Plone’s latest development version straight from
Subversion.
Follow the steps from Create a pristine Zope instance and then,
after having activated the instance’s environment via source
$INSTANCE_HOME/bin/activate, do:
easy_install Plone==dev
This will download and install Plone’s current development version.
This way you can experience the latest and greatest (and potentially
most unstable) Plone.
You want to create a Zope instance with the latest Plone 3 release in
it.
This will install the latest Plone version from the Cheese Shop.
Right now this is 3.0-r12165, an experimental and arbitrary
snapshot of Plone 3 dating back to the 4th of February. Note that
it’s not related to the real Plone 3.0a2 release, which is the
latest official release of Plone 3 and what you normally want to use.
You want to develop a package for Plone 3.0. We’ll call this package
yourpackage.
Follow the steps in Create an instance with Plone 3 from Subversion
in it.
Install ZopeSkel and create your package if you haven’t one already:
easy_install ZopeSkel paster create -t plone_core mypackage
Activate your instance’s environment if you haven’t yet and install
your package in development mode:
source $INSTANCE_HOME/bin/activate cd mypackage python setup.py develop
You are encouraged to create your new Plone 3 modules outside of the
Products directory/package. ZopeSkel helps you with quickly setting
up a distribution.
Invoking python setup.py develop inside of your newly created
project will install your package in development mode.
There are good reasons to still use Products. When you develop a
Product, just link it into your instance’s Products directory as
usual.
Note that you can override Products or packages that come with Plone
this way, which enables you to develop parts of Plone itself.
Plone 3.0, ploneenv and the Plone egg distribution are under heavy
development still. Therefore you might encounter errors while trying
out these recipes. Please report
those!
There is one known problem with ploneenv, where easy_install
attempts to compile Script (Python) files and spews a lot of error
messages. However, those error messages are not critical, and the
installation succeeds nevertheless.
If you’re developing Plone 3 itself, you might want to go for
ploneout, which is the mechanism used by most Plone developers who
actively develop Plone.
My previous blog on ploneenv has some more pointers and info.
Daniel Nouri: ploneenv recipes
Originally from Planet Plone
Originally from del.icio.us/tag/plone by jluvsu2
Plone helps you manage your content.
Originally from del.icio.us/tag/plone by ischnura
Error References â plone.org
Originally from del.icio.us/tag/plone by caussourd
i wouldn’t worry quite so much about the W3C parser, and more about how Plone performs in the browsers you are using.
Nabble - CSS errors (also in plone.org)
Originally from del.icio.us/tag/plone by onmountain
Using Forms Forms are an integral part of any site, and almost everyone needs to create a method for creating and altering forms in your Plone site.
6. Introducing Advanced Plone Templating and Scripting â PloneDocs
Originally from del.icio.us/tag/plone by onmountain
A solution to get PloneGlossory to work on Plone 2.5.x
gmane.comp.web.zope.plone.archetypes.general
Originally from del.icio.us/tag/plone by keesT