SCORE v1.4

Recommended Release of SCORE v1.4 is 1.4.32.0

Scaffolding:

1.4.2.0

This is an early release that only includes two features of the full 1.4 scope. We have been piloting it with a few projects. We don't recommend upgrading to it from 1.3 unless you need one of these two features.

  • [Feature]: SCORE-246: Implementation of GetLookupSourceItem rules - allow user to change the context node of a query for source field queries (SCORE University video)
  • [Feature]: SCORE-258: Patch to support MVT with MVC in Sitecore 7.2 (more details)

1.4.2.1

  • [Fix]: SCORE-329: Core dump (Stack Overflow) in Score.Custom.Handlers.PreserveScoreMetadata.EnsureScoreMetadata during .update package install with/over an item with not properly formatted __Renderings. As part of this fix all item:saving and item:saved event handlers were silences during .update package install.

1.4.2.2

  • [Fix]: SCORE-312. Link dialog customizations allow to store OnClick handler and No Follow settings but doesn't render it back on subsequent opening of the dialog. Saving the link again will erase previously specified OnClick / No Follow setting. As part of the fix we also disabled the SPEAK overrides to bring back the original XML dialogs. One reason to doing so was a known issue in Sitecore 8 where the link dialog would write "Active Browser" value into the link's target attribute (details)

1.4.23.0

  • [Feature]: SCORE-224: Component Datasource Location Rules  - allow users to define rules to map shared content folders to tenant websites (SCORE University video)
  • [Feature]: SCORE-23: Language Tools (Documentation)
  • [Fix]: SCORE-281: Reference fields render a GUID when administrator first selects a value from page editor
  • [Feature]: SCORE-282: Add distinctive marking for no color selection for color picker fields to distinguish from other colors on gray background
  • [Feature]: SCORE-292: Tested with Sitecore7.2 Update 3. SCORE is confirmed not to conflict and nicely accompany the now out-of-the-box support for query: syntax in Datasource Location field.

  • [Feature]: SCORE-292: As part of ensuring full support and no conflict with 7.2 rev. 141226 we also extended Score-based implementation of query: support in the Datasource Location field to return multiple datasource roots in case a query returns more than a single item (previously only the first item in the list would be returned)

  • [Feature]: SCORE-299: Add new UFFO for Sitecore Checklist field
  • [Feature]: SCORE-321: All data templates that represent datasource items for renderings (e.g. Content Spot) were marked as Bucketable which allows putting them into an item bucket. An example would be a rather large site having hundreds of various highlights in its site shared content and converting the ./Content/Highlight under the site shared content into an item bucket 

  • [Feature]: SCORE-235: Ensure snippets are multi-lingual ready
  • [Fix]: SCORE-266: Scope cascading placeholders feature to only kick in on SCORE pages (directly or indirectly inheriting from the Base Page template) and snippets 

  • [Fix]: SCORE-306: If a snippet item has an "and" (or other query-sensitive special symbols) in its name opening it in Page Editor will throw an exception (YSOD). 

  • [Fix]: SCORE-307: Make sure SEO friendly name handler processes Redirect Pages (Link Only template) as well as content pages (Base Page template)

  • [Fix]: SCORE-300: Make sure duplicate name prevention handler only works in active HttpContext when it can communicate with the Sheer UI (also see SCORE-329 in 1.4.2.1)

  • [Fix]: SCORE-257: Refactor, unit test, and fix some of the business rules conditions that power Placeholder Settings Business Rules, namely those that count renderings in a given placeholder

  • [Fix]: SCORE-298: Make snippet container more resilient to issues with the test context item (e.g. points to an item that no longer exists in Sitecore)

  • [Fix]: SCORE-298: Removed obsolete Publish Score Site and Insert Child Item commands. If upgrading to 1.4 from earlier versions of SCORE you will still have the extension ribbon button for Publish Score Site but it won't do anything. You can go ahead and remove it from the core database 
  • [Fix]: SCORE-267: MVC model email validator fails to perform client side validation. As part of this fix all custom Sitecore-aware MVC model validators were refactored and re-tested for proper client-side and server-side validation with both MVC4 (Sitecore 7.1) and MVC5 (Sitecore 7.2+)

  • XML Generation sitemap pipeline was renamed from <generateScoreXmlSitemap> to <score.generateXmlSitemap>

  • [Demo]: SCORE Demo video - Elastic Renderings
  • [Demo]: SCORE-283: SCORE Demo video - Building a page with components
  • [Demo]: SCORE Demo Video - User Friendly Field Object and Custom Fields
  • [Tutorial]: SCORE-254: SCORE University video for Visual Studio Solution Scaffolding (Getting Started with SCORE - Part 1)
  • [Tutorial]: SCORE-255: SCORE University video for Sitecore Site Scaffolding (Getting Started with SCORE - Part 2)
  • [Tutorial]: SCORE-274: SCORE University video for GetLookupSourceItem rules 
  • [Tutorial]: SCORE-275: SCORE University video for Component Datasource Location rules

1.4.25.0

  • [Fix]: SCORE-305: Script tag stripped out on the Scripts fields if modified in Page Editor

1.4.26.0

  • [Fix]: SCORE-369: Pages that have item names that match Sitecore Query axes (e.g. child, ancestordescendant. etc.) break the Page Editor ribbon

1.4.29.0

  • [Feature]: Support (and release packages) for 7.2 Update 4

1.4.30.0

  • [Fix]: SCORE-371: Custom control (dialog) that allows editing SCORE's Geo Location field was not moving the pointer on the map after google places auto-complete search due to a JS error. It's really a conflict with an older version of prototype.js that appeared in Sitecore starting with 7.2 Update 3 as well as in 7.5 and 8. More details on the issue can be found here. Fixed by upgrading the google maps API to a latest stable v3 version.

1.4.32.0

  • [Feature]: SCORE-411: Change all Single Line Text field in SCORE and SCORE Bootstrap UI components to use Raw Text field that behaves just like the Single Text but also support arbitrary markup (e.g. &copy;, (TM), (R), etc.)
  • [Fix]: SCORE-312. Link dialog customizations allow to store OnClick handler and No Follow settings but doesn't render it back on subsequent opening of the dialog. Saving the link again will erase previously specified OnClick / No Follow setting. As part of the fix we also disabled the SPEAK overrides to bring back the original XML dialogs. One reason to doing so was a known issue in Sitecore 8 where the link dialog would write "Active Browser" value into the link's target attribute (details)
  • [Fix]: SCORE-363: Page Meta Data rendering would sometimes duplicate the <meta> description and og:description. After the fix there will always be one <meta> description and one og:description and the two will display the same thing with open graph value taking precedence if defined