Zopeskel

Latest version: v2.21.2

Safety actively analyzes 630962 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 8

2.11

-------------------------

* Make the Plone 3 buildout default to Plone 3.2.1, and pick up
${versions:zope2-url} for Plone > 3.1
[MatthewWilkes]

* added a version requirement for Cheetah (>1.0)
[tarek]

* fix zopeskel/docs/localcommands.txt
[yboussard]

* Modify zopeskel/templates/plone/+namespace_package+/+package+/tests.py_tmpl
to init egg as product if it is a Zope2 product.
[yboussard]

* Modify plone3_buildout template to ask for a Plone version. If the version
is 3.0 or 3.1 it uses the plone install recipe, otherwise it uses the Plone
egg from the cheeseshop.
[MatthewWilkes]

* Link to appropriate PyPI pages for recipes used.
[MatthewWilkes]

* Add a Zope 2 without Plone buildout template.
[evilbungle]

* Reconciling HISTORY.txt to mirror what can be found at the following:
http://pypi.python.org/pypi/ZopeSkel/2.10. Release of 2.10 was clobbered
due to what looks like a merge at r74790.
[andrewb]

* Update plone2.5_template's buildout.cfg_tmpl to use Zope 2.9.10. This
release incorporates Hotfix-2008-08-12. Defaulting to a known insecure
Zope seems unwise for people that may be updating legacy environments into
buildout, since they're likely to forget to include the hotfix. Url to
2.9.10 hard-coded (as opposed to the more elegantly self-aware
plone.recipe.plone approach) per the practice of a plone.recipe.distros
plone part.
[andrewb]

* Nearly at the end of the creation of a ZopeSkel template, the local
commands available for that template are displayed.
[jaraco, markvl]

* The Plone template now has local commands. (Basically moved them
from the archetype templates to plone templates and made them
available for both.
[markvl]

* Added base test setup to the archetype template. Added wiring code that
runs README.txt as a doctest.
[esartor]

* Added tests to the addcontent contenttype command. These ammend the
README.txt file for each content type providing basic tests for creating,
editing and removing instances of the added content type.
[esartor]

2.10

Not secure
---------------------------

* Fixed a small bug that made most templates create a package that was
* showing twice in the Plone quick
installer is the top level namespace package was called 'Products'. Bug
was fixed in the 'plone' template (since version 1.5), now in other ones
where needed too.
[davconvent]

2.9

Not secure
-------------------------

* Update silva buildout to reflect changes in Silva 2.1 as stable
version, and 2.2 as development: SilvaLayout is not shipped anymore
as an extra distribution but integrated in Silva all. Remove
question, and update buildout.cfg template.
[thefunny]

2.8

Not secure
-------------------

* Generate logrotate configuration file using collective.recipe.template
so it does not need to contain absolute paths. This makes it possible
to move the generated buildout around, or install it on other machines
with different filesystem layouts.
[wichert]

* Also rotate instance1-Z2.log.
[wichert]

* Update documentation for hosting template to note that logrotate needs
to be told where to put its status file.
[wichert]

2.7

Not secure
-------------------

* Hosting template:

- Switch default Plone version to 3.1.4.
[wichert]

- Corrected a typo in the logrotate template, which prevented the zeo log
to be rotated.
[hannosch]

2.6.2

Not secure
---------------------

* Hosting template:

- Corrected even more references of instance to instance1 in proxy support
and logrotate handling.
[hannosch]

Page 4 of 8

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.