Magnolia Content Management CMS/ECM/WCM

File Release Notes and Changelog

Release Name: Magnolia CE 3.5.4

Notes:
Magnolia Community Edition v3.5.4

This is a bug-fix release

Please see http://documentation.magnolia.info/docs/releases/3-5-4.html for more details and upgrade instructions.

Fixes in 3.5.4:
    * [MAGNOLIA-1969] - Function to iterate over a node Data that has "checkbox" as control type
    * [MAGNOLIA-2001] - Redundant and unused log4j.dtd files
    * [MAGNOLIA-2011] - Allow setting response headers to allow/deny cache at client side
    * [MAGNOLIA-2020] - activation: /ActivationHandler should be  /.magnolia/activation or similar
    * [MAGNOLIA-2023] - filters: cache should be infront of i18n
    * [MAGNOLIA-2028] - SimpleNavigationTag  : add ability to wrap an anchor element with an html element
    * [MAGNOLIA-2007] - Deploy maven generated site to dev.magnolia.info with a working navigation
    * [MAGNOLIA-1428] - i18n does not work in the templates node
    * [MAGNOLIA-1993] - Inconsistent security checks on activation/deactivation
    * [MAGNOLIA-1994] - Internal virtual uri broken ?
    * [MAGNOLIA-1995] - Default cache implementation ignores compression type from configuration
    * [MAGNOLIA-2004] - update: Secured URIs menu item not removed when updating from 3.0.x
    * [MAGNOLIA-2005] - response status code is always reset to http 200 by rendering filter
    * [MAGNOLIA-2008] - Error when creating Developer Showroom All controls paragraph
    * [MAGNOLIA-2009] - Page title in samples still says "Magnolia 3.0"
    * [MAGNOLIA-2010] - WebContextImpl.include() should use pageContext if available
    * [MAGNOLIA-2015] - VirtualURIFilter: forward to JSP pages does not work anymore
    * [MAGNOLIA-2016] - activation: activation from 3.0 to 3.5 fails
    * [MAGNOLIA-2018] - Failure to initialize filter due may result in filter chain initialization being broken
    * [MAGNOLIA-2019] - deactivation: node is not locked
    * [MAGNOLIA-2021] - activation: security hole if you activate a new item
    * [MAGNOLIA-2022] - MgnlServletDispatcherFilter should be deprecated - it was replaced by ServletDispatcherFilter
    * [MAGNOLIA-2024] - filters: backward compatibility filter must be infront of the cms filter
    * [MAGNOLIA-2025] - taglib: cms:out uuidToLink with value absolute should consider i18n and repository mapping
    * [MAGNOLIA-2026] - ConcurrentModificationException while instantiating  [config:/server/security]
    * [MAGNOLIA-2029] - If anonymous user is not found magnolia can corrupt the user repository
    * [MAGNOLIA-2032] - FactoryUtil.getSingleton should be synchronized
    * [MAGNOLIA-2034] - content2bean: ClassUtil.isSubclass() can fail because LRUMap is not threadsafe 
    * [MAGNOLIA-2035] - Calendar does not work if user has language German
    * [MGNLDMS-117]   - update: UploadZipPage not registered when updating from 3.0.x

Fixes in 3.5.3 :
    * [MAGNOLIA-1814] - Status-Light for nested paragraphs stay green after changements
    * [MAGNOLIA-1900] - problems with FCKEditor and validation (required = true)
    * [MAGNOLIA-1962] - updating with samples: do not update the defaultURI if samples flag in magnolia.properties is set to false (or empty)
    * [MAGNOLIA-1963] - Modules: version number is not updated in repository if version handler does not register a delta for the latest version
    * [MAGNOLIA-1967] - UserManager implementations don't always use their assigned realm name
    * [MAGNOLIA-1970] - uuidLinkType has errors in the tld file
    * [MAGNOLIA-1971] - Mandatory listener check in the install task prevents registration of custom magnolia listeners.
    * [MAGNOLIA-1972] - Can't have a dialog without an associated paragraph
    * [MAGNOLIA-1973] - Dependency to mockrunner in magnolia-taglib-cms is not in test scope !
    * [MAGNOLIA-1975] - Review namespace definition on sample pages
    * [MAGNOLIA-1978] - uuidLinkType does not function properly - returns no results
    * [MAGNOLIA-1980] - update: update fails with a ConstraintViolationException if workflows are in progress
    * [MAGNOLIA-1984] - Mappings for wrapped servlets are not strict enough
    * [MAGNOLIA-1987] - Invalid tld for MainBar, NewBar and EditBar
    * [MAGNOLIA-1988] - Extend activation to support other then basic authentication methods
    * [MAGNOLIA-1991] - Missing jar-library: nekohtml
    * [MAGNOLIA-1992] - comparator in mappings TreeSet (Uri2RepositoryManager) makes entries with same UriPrefix length to override each other
    * [MAGNOLIA-1994] - Internal virtual uri broken ?
    * [MAGNOLIA-1996] - Use of chunked writer in results in corrupted cache
    * [MAGNOLIA-1974] - NPE when realPath can't be obtained.
    * [MAGNOLIA-1976] - Breadcrumb tag should use ">" instead of a plain ">" as default separator
    * [MAGNOLIA-1979] - Magnolia cms:out lacks examples in the tld file
    * [MAGNOLIA-1986] - Magnolia tag libraries lack unit tests
    * [MAGNOLIA-1997] - update: DefaultModuleVersionHandler should also extract module files on update
    * [MAGNOLIA-1999] - Unused test dependencies (nekohtml and rhino)
    * [MAGNOLIA-2000] - taglib: cms:setNode should set a ContentWrapper implementing a Map
    * [MGNLDMS-116]   - DMS module does not update servlet and URI2repository mapping properly

Fixes in 3.5.2 :
    * [MAGNOLIA-1960] - update: EE multiple subscribers update fails

Fixes in 3.5.1 :
    * [MAGNOLIA-1954] - Fixed inability to unset a value in a dialog.
    * [MAGNOLIA-1957] - Fixed Java 1.4 incompatibility.
    * [MAGNOLIA-1955] - Custom repositories in modules when not registered in subscribers for activation.
    * [MAGNOLIA-1956] - The login screen style's now matches the style of the install/update mechanism screens.

About 400 issues as documented in jira have been worked on
for the 3.5 release. We choose to significantly improve the
foundation on which we build the future of Magnolia, which
makes this quite a technology-focused release.

Update / Install
----------------
We added a new installation and updating GUI. The main
feature is the update mechanism, which allows seamless
updates from 3.0.5 to the new and any future versions. The
same mechanism is used for the modules, so custom projects
will highly benefit from that feature, as you can easily
deploy new versions of your custom project/module on the
live servers.

I18N
----
We added a basic mechanism for i18n content if you want a
1:1 structure for all the languages and not completely
separated hierarchies. Custom implementations are now
pluggable and we will improve that feature for the next
versions.

Beans for Configuration
-----------------------
Many parts of the code now use a configuration-to-beans
transformation which allows easy customizations of the many
parts of Magnolia. For example you can reconfigure the
implementation class of the user manager. All properties are
then populated by the configuration (supporting child-beans,
lists, maps). All that is combined with observation and
automates component reloading upon modifications.

Filters
-------
We separated the modules and designed them in a way that
multiple security and cache filters can coexist. All filters
can be bypassed which allows implementing sophisticated
custom solutions. As the filters are using the new
configured beans feature, you can for instance implement
complex virtual uri mappings.

Security
--------
We added the concept of URL protection so URLs can now be
protected independently of the website content. We improved
the concept of supporting the anonymous role and context. We
also added the concept of user realms which allowes us to
create a public user registration module (to be released
soon)

Easier integration with other frameworks
------------------------------------------
We removed many obstacles regarding the integration of
Magnolia and other frameworks.  For example, the web.xml
file has been drastically simplified, and now contains only
two entries: a filter and a context listener. We also
enabled the support for on-forward filter dispatching. This
allows using another framework that forwards/dispatches to a
Magnolia url. (Whatever you pass as request attribute is
then available in the template). To increase the flexibility
we also added paragraph renderers, allowing special
paragraph implementations. (We now have experimental support
for freemarker-based paragraph rendering and a prototype for
cold-fusion rendering)

Activation flexibility
----------------------
Not only is the multiple subscribers feature now available
in the CE edition, we also added support for a more flexible
from/to mapping of activation. The structure of the content
in the subscriber does not need to be a mirror of the
authoring environment anymore.

Jackrabbit
----------
This is actually not our merit but Magnolia 3.5 is delivered
with jackrabbit 1.3, which is much more stable, flexible and
faster than the version delivered with Magnolia 3.0.


Final Notes
----------

Enjoy, and as always we are happy to hear your feedback.
Fire up the blogs, add issues to our issue tracker or
discuss in the forums.

Thank you to the Magnolia development team, our
many contributors and everybody at the Magnolia Group.

Thank you for your interest in Magnolia!

Magnolia International Ltd.

Changes:
http://jira.magnolia.info/browse/MAGNOLIA