Plone 4.2rc2

Milestone information

Eric Steele
Release registered:
Yes. Drivers can target bugs and blueprints to this milestone.  

Download RDF metadata


Assigned to you:
No blueprints or bugs assigned to you.
No users assigned to blueprints and bugs.
No blueprints are targeted to this milestone.
No bugs are targeted to this milestone.

Download files for this release

After you've downloaded a file, you can verify its authenticity using its MD5 sum or signature. (How do I verify a download?)

File Description Downloads
download icon Plone-4.2rc2-lion.dmg (md5, sig) Plone 4.2rc2 OS X Binary Installer for Lion 76
last downloaded 33 weeks ago
download icon setup-plone42-4.2.0-5350-win32.exe (md5) Windows installer 86
last downloaded 33 weeks ago
download icon Plone-4.2rc2-UnifiedInstaller.tgz (md5, sig) Unified Installer for Plone 4.2rc2; source kit for Linux/BSD/OS X/Unix 210
last downloaded 5 days ago
Total downloads: 372

Release notes 

This release does not have release notes.


View the full changelog

collective.recipe.omelette: 0.13 → 0.15

distribute: 0.6.24 → 0.6.27

Products.Archetypes: 1.7.14 → 1.8

- PEP 8 (ignoring W602, W604, E231, E241, E301, E302, E501 and E701).
- Remove remaining hard-coded required markers. The 1.7.14 change only got
  one of them.
- Moved form help from a div after form field labels to a span within. The
  purpose is to semantically associate the label to the form help so that
  it's more useful to a screen reader user.
  Note that sunburst's public.css and classic's form.css.dtml were
  simultaneously changed to assure block display of help in normal
  Closes, an accessibility ticket.
- Deprecated aliases were replaced on tests.

Products.CMFPlacefulWorkflow: 1.5.6 → 1.5.7

- Fixed a few test failures in combination with

Products.PasswordResetTool: 2.0.7 → 2.0.8

- Be less sensitive for white space differences in tests.

Products.PluggableAuthService: 1.7.8 → 1.8

- Added export / import support for the ChallengeProtocolChooser plugin's
  label - protocols mapping.

Products.ResourceRegistries: 2.1.1 → 2.1.2

- Fix test failure under Plone 4.2.
- using hashlib.md5 (fixing a deprecation warning)

archetypes.kss: 1.7.1 → 1.7.2

- 1.7.2 (2012-05-25)

diazo: 1.0 → 1.0.1
------------------ 1.5.1 → 1.5.2

- Deprecated aliases were replaced on tests.
- Keep the acquisition context of the blob in index_html, as otherwise
  we cannot get the http__etag method.
- Move download implementation (the index_html method) to the blob
  wrapper class. The wrapper object is now directly viewable via the
  Zope 2 publisher.

  This change adds support for publishing of the original image data
  for any image field via the scaling view (even for fields that have
  been added via schema extension).

  Previously, if the blob wrapper was published for a content object
  that did not derive from the provided image class, Plone's default
  index_html template would be used, rendering an HTML page
  instead of the image.
  [malthe] 1.0.3 → 1.1

- Use zope.browserresource instead of
- Deprecated methods aliases were replaced on tests.
- Fix possible test failures by logging in with the user name.
  Note that user id and user name (login name) can differ.
  [maurits] 2.0.10 → 2.0.11
---------------------------------- 2.2.4 → 2.2.5

- Move form help inside field labels to improve accessibility.
- Updated zope.formlib imports.
- Avoid hard dependency on Archetypes.
- Add missing condition in usergroups template.
- Add .gitignore.
- Fix component lookup error during startup.
  [pjstevns] 2.1.5 → 2.1.6

- Add Site Administrator role to Review comments permission.
- Fix excessive JS comment deletion.
- No longer depend on packages.
  [hannosch] 2.0.5 → 2.1

- Remove hard-coded required markers. Replaced by CSS in Plone 4.2.x.
- Depend on zope.formlib rather than
  [davisagli] 1.3.1 → 1.3.2
------------------------------------ 1.7 → 1.7.1

- Remove hard dependency on Archetypes.
  [davisagli] 0.5.8 → 0.6

- Remove hard-coded ■ (box) markers from required labels to match
  changes made in sunburst/public.css and archetypes. Fixes double required
  markers in Plone 4.2rc1.
- Pull form help inside label tag and make it a span rather than a div. The
  purpose is to improve accessibility by making the semantic connection between
  label and help. Related to
- Use ViewPageTemplateFile from zope.browserpage.

plone.outputfilters: 1.2 → 1.3

- Fixed testing error by moving the part of README.rst to
- Small pep8 update

plone.resource: 1.0 → 1.0.1

- Make sure text/html files imported as persistent files will be
  served with a utf-8 encoding. This fixes

plone.uuid: 1.0.2 → 1.0.3

- Use zope.browserpage.
- Defensive UUID assignment in addAttributeUUID() handler: keep existing
  UUID value if handler called more than once, except in case of object
  copy event, where original and destination should have distinct UUID.

plonetheme.classic: 1.2.1 → 1.2.2

- added styling on the eventlisting, that was changed from a table into headings/paragraphs
  for accessibility reasons. Styling uses the classic dtml style to minimize visual changes.
- Set "display: block" on .formHelp in forms.css.dtml to assure that field
  help displays as a block even if it is formatted as a span for accessibility.

plonetheme.sunburst: 1.2.4 → 1.2.5

- For event view template, changed headerless table to headings and divs for better accessibility. See bug #13181
- define class .breadcrumbSeparator, which is referred to in
  and, but wasn't in Sunburst. Set a color on it, because
  the separator character was changed (see
  The color chosen is WCAG2.0 compliant in contrast.
- Set "display: block; font-weight:normal" on .formHelp in forms.css.dtml to
  assure that field help displays well even if it is formatted as a span
  inside the label for accessibility.
- Change form tab style selectors from '#content' to '#content-core' so form
  tabs work in both content and overlays.
- Fix vertical alignment of listing table cells when content type icons are

0 blueprints and 0 bugs targeted

There are no feature specifications or bug tasks targeted to this milestone. The project's maintainer, driver, or bug supervisor can target specifications and bug tasks to this milestone to track the things that are expected to be completed for the release.

This milestone contains Public information
Everyone can see this information.