Score Bootstrap UI v1.3

Owned by Pavel Veller (Unlicensed)
Last updated: Jan 23, 2015

Recommended release for Scoe Bootstrap UI 1.3 is 1.3.17

Scaffolding:

1.3.3

  • Initial public version

1.3.4

  • [Feature]: SCORE-199: Support for MVC areas for rendering (view and controller rendering alike). Link to documentation and usage guide: Specifying the MVC Area For Renderings
  • [Feature]: SCORE-215: Add score-component class to content components that typically require vertical spacing
  • [Fix]: SCORE-191: Refactor content components and use controller renderings for dynamic components (e.g. navigation spiders). Rendering items GUIDs were preserved.

Web.config under /Areas/ScoreBootstrapUI/Views was modified. When you deploy this release into your Sitecore (local or remote) Sitecore won't overwrite the config file (default Sitecore behavior). When upgrading to this version (or newer) please make sure new Web.config is in effect (you would need to inspect that Views folder and rename the modified version brought in with the new .update package to replace the original from the previous version of SCORE Bootstrap UI). You don't have to do it if you're installing 1.3.4 into a Sitecore that is not running an earlier version of SCORE Bootstrap UI.

1.3.5

(These issues were introduced in 1.3.4)

  • [Fix]: SCORE-203: Center Text component reports an error when used on a page
  • [Fix]: SCORE-204: Left Text component reports an error when used on a page
  • [Fix]: SCORE-205: Right Text component reports an error when used on a page

1.3.10

  • [Feature]: SCORE-221 Update Twitter Bootstrap to 3.3.1 https://github.com/twbs/bootstrap/releases/tag/v3.3.1

    This update affects the scaffolding solution as well - the less files, bootstrap.min.js, and the fonts are all updated

  • [Feature]: SCORE-150: /scorebootstrapui/about/version now reports the Sitecore version it was built against as well as the currently running Sitecore version
  • [Fix]: SCORE-211: NuGet powershell sometimes times out when deploying large packages (e.g. Score.BootstrapUI.TDS.Master). 
    Timeout for the web service proxy was increased to 5 minutes

  • [Fix]: SCORE-198: NuGet powershell script would sometimes report cached HTTP result "thanks" to IE caching that Invoke-WebRequest is using. Timestamp GET parameters were added to cache-sensitive GET request to avoid cache interference.

  • [Fix]: SCORE-228: Fix Area Name field on the Renderings Folder with Area for Bootstrap UI to match the most recent SCORE data template structure

    If you are installing Score 1.3.12+ and Bootstrap UI 1.3.8+ into a Sitecore instance that didn't have priror versions of Score with MVC Area support you don't need to do anything special. If you are upgrading to 1.3.12+ and 1.3.8+ you might need to delete the MVC section from the Rendering Folder with Area under /sitecore/templates/Score/Renderings as it's been moved into MVC Area Name Base template.

    Also make sure your Web.config under /Areas/ScoreBootstrapUI/Views has been updated after the deploy of the new version. NuGet's powershell only commits configuration files in the App_Config and system-level configs like Web.config should be updated manually.

  • [Fix]: SCORE-231: Bootstrap UI vertical navs should not include nav-pills in the class. 

  • [Fix]: SCORE-233: Remove the image width and height attributes from all BootstrapUI renderings so that image sizes can be responsive

1.3.15

  • [Feature]: SCORE-241: Update editing experience of the carousel panels, stripes, and similar components (if any) that use 40% for fields editing. Both components now use full screen width for the panel editing and render the editable fields above the panel (not to the left of it like it was in previous releases)
  • [Feature]: Re-enable functionality to allow custom CSS class to be specified as a rendering parameter to a specific instance of a rendering

1.3.17

  • [Fix]: Stripe component had predefined caching settings on the rendering definition item (was marked as Cacheable with VaryByData). This fix removed the default caching settings and the component is not cached by default