R206 - System update

Thursday, July 30, at 11:00 UTC, we'll  update the new version of Business Catalyst service to fix some minor issues.  Please find below the detailed list of changes included in the update:

Updates

• _System/Apps folder and it's content is now filtered in the manage site interfaces (all screens inside Manage tab)
• Ressources under _System/Apps folder are accessible only from the app domain while authenticated

Bug fixes

• 3997908 - we have upgraded the USPS integration for Canada to use IntlRateV2. The new USPS API version require products to  have the product dimensions filled in. Once the new integration goes live USPS will not process any orders containing products with blank product dimensions. For more details, read the Updates to the USPS shipping blog post
• 4015525 - Fixed an issue with the email campaign editor which displayed the visual editor only even when the "New visual editor for campaigns" setting in partner portal was OFF
• 4007285 - fixed an issue on v3 customer APIs which prevented developers from doing partial updates on customers when the customer last name was not set
• 4026529 - fixed an issue with the ICE editor which caused anchor links to open in new window when clicked in ICE (or IBE) and attached click event handlers don't execute.

Other notes

For the next release (R207), we will be pushing live a major update that will enable all modules to set their data using the appropriate data type.

• We have already updated modules to correctly set the type for date time data at the beginning of 2015 and with the next release we'll also update modules to correctly set the type for boolean and numeric data. This means that  filters and comparison operators will work as expected on all numeric data in all cultures.
• All numeric values will be  displayed by default using the dot '.' as the decimal separator and with no group separator. This happens regardless of the site's culture and should make the output from numeric values much more predictable. As an example, for a shopping cart with a total invoice value of 1050.00, the output of {{ invoiceTotal }} is always 1050.00. This is a backwards compatibility breaking update for sites that use cultures where comma is used as the decimal separator, as for them we previously displayed numbers in their localized representation by default.
• Numeric values can be localized using the already existent Number and Money filters. On top of the existing functionality, Number and Money will support an additional parameter for controlling the output format. Just as we previously did with the Date filter, we use the format strings from .Net, which are available here and here. By default, if no format string is specified, we use the "N2" format which displays numbers using two decimals and which also includes the group separator if necessary. Number and Money filters always output data using the site's culture. Below is are a few examples of how the filters work:   
  • cultures that use dot '.' as the decimal separator ($ is used as a sample currency):            
    • {{ invoiceTotal | number }}: 1,050.00
    • {{ invoiceTotal | number: "N2" }} 1,050.00
    • {{ invoiceTotal | number: "N4" }} 1,050.0000
    • {{ invoiceTotal | number: "F2" }} 1050.00
    • {{ invoiceTotal | money }} $1,050.00
    • {{ invoiceTotal | number: "F2" }} $1050.00
  • cultures that use comma ',' as the decimal separator (EUR is used as a sample currency):            
    • {{ invoiceTotal | number }}: 1.050,00
    • {{ invoiceTotal | number: "N2" }}: 1.050,00
    • {{ invoiceTotal | number: "N4" }}: 1.050,0000
    • {{ invoiceTotal | number: "F2" }}: 1050,00
    • {{ invoiceTotal | money }}: EUR1.050,00
    • {{ invoiceTotal | number: "F2" }}: EUR1050,00
• Round filter will work on all cultures. It previously worked only for cultures that use the dot '.' as the decimal separator.
• We'll update  all boolean tags to output "true" and "false" instead of "1" or "0". To prepare for the release, you should update your sites before the release and apply a convert filter to the tag (ex: {{ myBool | convert: “number” }})

Additionally, for consistency reasons, with the next release (R207) we'll also remove the following liquid date tags:

• in module_blogpostlist:    
  • day, month, monthnumeric, year liquid tags - as they are covered by the date liquid tag
• in module_news (or module_announcements):    
  • fromDateDay, fromDateMonth, fromDateMonthNumeric, fromDateYear liquid tags - as they are covered by the fromDate liquid tag
  • toDateDay, toDateMonth, toDateMonthNumeric, toDateYear liquid tags - as they are covered by the toDate liquid tag
• in module_booking:    
  • weekday, day, monthName, month, year tags – as they are covered by the date liquid tag

If you are using these tags, please update your sites to make use of the date tag and corresponding date filters. The legacy BC tags will not be impacted by the change.