Recent Version:
The biggest feature of SCORE 1.5 is full support for Sitecore 8.0. |
Scaffolding: |
If you are using SCORE 1.5 with Sitecore 8.0 Updae 1 or 2 please be aware of a known issue with the SPEAK ribbon and use the workaround offered by the Sitecore Support team. If you are using Update 3 or newer you don't need to do anything. |
[Feature]: SCORE-225. Refactor cascading placeholders and annotations (aka sticky notes) to use new page fields introduced by the SCORE's Page Base. This architecture performs better and has no interference from layout manipulations. It also nicely integrates with the new final layouts in Sitecore 8.
If you have used cascades or sticky notes with SCORE 1.3 and 1.4 you will need to use a migration script to move metadata from where it used to be stored prior to 1.5. Please contact scoresupport@brainjocks.com |
[Feature]: SCORE-380. SCORE UI Layer was extracted from SCORE Bootstrap UI to stimulate reuse and enforce implementation patterns across various component layers (e.g. the upcoming SCORE Foundation UI as well as custom component layers built by SCORE clients)
New Rendering Parameter templates for Score UI components: Accordion, Lead, Content Spot, Tab Set
New "Highlight Header" field added to the Score UI Highlight datasource item template.
Web.config
files under /Areas/*/Viewschild
, ancestor
, descendant
. etc.) break the Page Editor ribbon (ported over from 1.4.26)[Fix]: SCORE-312. Link dialog customizations allows 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 dialog 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 |
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 definedComponent DOM classes have been normalized for naming consistency. The following DOM classes have been re-named:
1.4 class name | 1.5 class name |
---|---|
score-component | score-content |
pageWrapper | page-wrapper |
score-button-menuitem | score-button-menu-item |
score-carouselpane | score-carousel-pane |
score-carouselpane-body | score-carousel-pane-body |
score-centertext | score-center-text |
score-contentspot | score-content-spot |
score-righttext | score-right-text |
score-documentheader | score-document-header |
score-documentheader-with-subtitle | score-document-header-with-subtitle |
score-fullwidth-jumbotron | score-full-width-hero |
score-highlight-button-wrapper | score-call-to-action |
score-jumbotron | score-hero |
score-leftext | score-left-text |
score-mainmenu | score-main-menu-spider |
score-progress | score-progress-area |
score-stylebox | score-style-box |
score-tab-pane | score-tab-panel |
score-youtubevideo | score-youtube-video |
score-sectionnav | score-section-menu |
score-sectionheader | score-section-header |
score-siblingsnav | score-siblings-menu |
score-menulist-divider | score-menu-list-divider |
score-imagelink | score-image-button |
score-sitemap | score-site-map |
score-menu-link-item | score-menu-list-item |
score-menu-image-link | score-menu-list-image |
null
to args.PlaceholderRenderings
. Pipelines up the chain will stumble upon it. Now our actions are more defensive and only add a not-null rendering items. The issue as described would surface if a placeholder settings rule referred to a rendering that has been deleted.Anchorable
so that component layers (e.g. SCORE Bootstrap UI) could support deep linking for collection components (e.g. Tab Set)content-site:query:./*[@@templateid = '{...}'
)Sitecore Developer
role.__Standard Values
item) results in "404 layout not found" in Sitecore 8 Update 6. This is due to the fix that Sitecore applied to handling of standard values in Experience Editor to ensure proper delta calculation on their end. We now needed to account for it in the SCORE's feature that supports Shared layout modifications via Experience Editor. This particular SCORE defect (and the fix for it) only applies to Sitecore 8.0 Update 6. Users of earlier versions of 8.0 are not affected.[Fix]: SCORE-789 Generic Link does not support subject for mailto: links
[Fix]: NamedAnchor partial view contains rogue "invisible" character that causes spacing issues when rendered on a web page