Silva CMS Changelog

New in version 3.0.2

July 13th, 2013
  • You can no longer create a folder called "index".
  • Expiration date of a version with a date in the future are now kept.
  • Support for customizing HTTP headers on most of the default Silva contents was added.
  • Metadata sets were renamed.
  • A method was added for repairing the order of the ordered container.
  • A user menu was added to the SMI, replacing the user preferences and logout buttons.
  • An "About Silva" popover was added.
  • Preview resolutions are now configurable, for testing on small screens, mobile, and tablets.
  • Tests were improved.

New in version 3.0.1 (March 8th, 2013)

  • A maintenance release with various improvements and fixes.

New in version 3.0 (December 12th, 2012)

  • The new architecture sports a state-of-the-art user interface, entirely Ajax-driven and much more userfriendly, responsive, and performant.
  • Silva 3.0 includes a new content editor running on top of a new document type.
  • Silva News Network has been refactored and provides advanced calendar functionality.
  • On a system level the performance of both frontend and backend has been immensely improved.

New in version 3.0 RC (October 8th, 2012)

  • This major new version sports a completely rebuilt and state-of-the-art user interface. It’s entirely Ajax-driven and much more userfriendly, responsive, and performant. Silva 3.0 also includes a new visual editor running on top of a new Silva Document. For site managers, the Code Sources have been refactored to use references and are maintainable on the file system. Silva News Network has been refactored as well and sports new calendar functionality.

New in version 2.3 (December 22nd, 2010)

  • Support for mobile skins based on browser detection.
  • Robust reference management system that preserves links between resources.
  • Silva now supports WSGI servers.
  • More consistent API and vastly improved testing infrastructure.

New in version 2.3 Beta 1 (August 6th, 2010)

  • Users can select a Gravatar image to appear next to their name in Silva.
  • Silva File and Images have been reviewed, HEAD and HTTP headers are now properly implemented. ExtFile storage is considered legacy, please migrate to Blob storage.
  • References are used to link content: Link, Indexer, Ghosts and links, images in Kupu uses it to refer linked content. XML import / export have been updated to work with thoses.
  • z3c.forms have been replaced with Zeam Forms.
  • Silva now uses Python 2.6 and Zope 2.12.
  • Most of Silva contents now properly triggers Zope event when being added/edited.
  • More parts of the SMI have been replaced by Zope views and forms.
  • Tests now use infrae.testing. Functional tests rely on infrae.wsgi.

New in version 2.2 (March 31st, 2010)

  • A simple PhotoGallery demo view have been added to use on any container.
  • Silva Links now support again relative links.
  • SilvaExternalSources is installed by default, and the toc element in the default created SilvaDocument have been removed.
  • Deprecate Products.Silva.helpers.makeContainerFilter and makeZMIFilter (makeZMIFilter was moved to silva.core.conf.utils). Fix signature checking in Folder.filtered_meta_types.
  • kupu: the link input field in the link toolbox was changed to be a textarea. In 2.2 releases prior to 2.2 final, the input field changed to a textarea on focus and back to an input field onblur, so long urls where easier to view. This caused confusing 'double clicking' behavior in order to manually add or update a link (first to unfocus, second to update)
  • The formulator lookupwindow field changed to a textarea to address the same concerns as the link toolbox in kupu mentioned above.

New in version 2.2 Alpha (November 19th, 2008)

  • This release adds a slew of new features for developers and system administrators, and is a quantum leap with Zope 2.11 and Five/Grok technology. Also the Sphinx-driven docs.infrae.com has gone online.

New in version 2.1 (September 7th, 2008)

  • This release adds a range of features for Author/Editors (such as 'elaborate' Code Sources, an "Editor Comments" toolbox, much more configurable Automatic Table of Contents, preview with public layout, and an improved Lookup Window) and for Site Managers (e.g. a quota subsystem, Zope Pluggable Authentication Service, authentication with OpenID, and a CAPTCHA). It has performance and technical improvements such as functional tests.