CMS7-6070: 'Remember me' cookie max-age should be properly setted and to be configurable - Updated the configuration to have: -# Added 'rememberme.cookie.maxage' attribute to the login plugin repository configuration which controls the max-age of the cookie in a configurable way - Updated code to take that into account and also to have a default value for backward compatibility, so if the attribute is not there this default value is used
CMS7-5216 Remove the warning message displayed in CMS log-in screen for chrome - Updated supported browser values Safari >= 5 and Chrome >= 7
HREPTWO-4739: copying hippo-ecm projects to hippo-cms7
HREPTWO-4597: move layout/skin and mostly cms configuration to cms project
HREPTWO-3953: remove layout plugins from cms-static Work in progress; goal is to remove as much as possible of the configuration, moving the wireframes configuration into java classes, only to be overridden for customization.
HREPTWO-3335: bulk merge of revisions 20254 thru 20460 of 2.09 branch
HREPTWO-3175: up the frontend namespace version Removed all xml namespace declarations for jcr namespaces, except the builtin JCR ones.
HREPTWO-949: blindly merging from trunk: THANKS FOR THE CONFLICTS
HREPTWO-2415: bump version number of namespaces to allow upgrading with explicit remodel
HREPTWO-530: preliminary use the remember me login plugin
HREPTWO-2205: use repository configured login plugin application, rather than a hard-coded programmatic one. I've DELIBERATELY removed the skin attribute from the programmatic configuration of the login plugin in the JavaConfigService. This because it should be VERY noticeable that not the proper login box as specified by the repository based configuration of the login application is used. Only then a disfunctional configuration of the login application will be noticed. By default, with a working repository, the configuration is used as specified in the repository. The programmatic configuration is used only as a fall back, otherwise there is no application at all to show. The alternative is to show a "not available" application or to remove it all together (getting a error status code from the application container). But letting the programmatic configuration of the login behave just like the repository configuration is NOT AN OPTION.
This form allows you to request diffs between any two revisions of this file. For each of the two "sides" of the diff, enter a numeric revision.