Composite C1 4.2 (4.2.5249.32246)Write a review for this release
- help us improve, recommend us.
If you are new to Composite C1 and want to install it: http://docs.composite.net/Getting-started
You can upgrade to version 4.2 from earlier Composite C1 releases - see guide lines below.
What's new in 4.2?
Most important of all the 4.2 release enable users to build much richer web experiences - this is possible thanks to a simplified interface for changing C1 Function settings and 'pixel perfect' previews of C1 Functions in the Visual Editor, making it very easy to locate elements you need to update.
The list of changes below is not exhaustive, but contains the highlights of this release.C1 Functions embedded in the Visual Editor show a "perfect preview" of the function output.Editing C1 Functions from the Visual Editor is a lot more user friendlyNew responsive starter site "Venus" - see a preview on http://venus.c1.composite.net/The Visual Editor canvas width is now set to match the width of the content placeholder in the actual rendered template. If you update the template or CSS the width will follow.Content editing on iPad functionalServer Log (moved to System perspective) contains login auditing, present stack traces much better and more. If verbose logging is enabled the log will also contain auditing info about major actions (like page edits) and user access changes.Google Chrome issues in the C1 Console fixed.ASP.NET Razor 3.1.1 now defaultNew UI widget for selecting glyphicons and similar font based icons New security permission type 'Configure' added - actions like adding a new website and managing meta data / page folders now require this (or admin) permission.
This release also contain a great number of minor new features, performance/stability/ux improvements and fixes, please see https://compositec1.codeplex.com/SourceControl/list/changesets
for more details.
You may not get the visual previews for C1 Functions if you run in certain hosting environments. In those cases you will get a generic representation of the C1 Function like previously.
This is the case on Windows Azure Web Sites (WAWS) - this is due do blocks in the IP stack on this platform.
You can upgrade manually (copy files, modify xml in config files etc.) or you can automate the procedure using an Upgrade Package.Manual Upgrade
The manual upgrade guidelines are posted "gratis" on CodePlex when available. They are intended for the tech savvy DIY developers and organizations. Easy Upgrade
The Upgrade Package is a paid service that provide you with upgrade support and a simple and painless upgrade path - you can upgrade directly from the web interface with a few clicks. Beside from making continuous upgrades easy you help fund the development of Composite C1, which is a super awesome thing to do.
for details.Upgrading from earlier Composite C1 4.2 releases
If you are among the awesome people who helped us test the beta releases of 4.2, you get the easy upgrade free of charge:
- Make a backup of your website.
- In the C1 Console, go to "Packages" on the System perspective
- Browse down "Composite.Updates" and click "Package Info" on the 4.2 upgrade
- In the Package Info view, click install
- Complete the wizard
After upgrading you should immediately see the new features - no configuration needed.