Change Log

Event Stream Module Update

 
Addded new font icons in conjuction with the Event Stream Module update for sendgrid inlcuded in Insites Components v2.7.0
 
New Icons
 

• icon-email-delivered
• icon-email-open
• icon-email-bounce
• icon-email-click
• icon-email-deferred
• icon-email-dropped
• icon-email-processed
• icon-email-spam
• icon-email-unsubscribe

Improvement

• Error handling for ElasticSearch indexing issues caused by casting errors

New Feature

• New engine to automatically escape HTML when outputting variables. Disabled by default for backwards compatibility. Learn more about [improving the way we sanitize input] in Github Issues.

Bug Fix

• Submitting form using GraphQL with spam protection enabled
• Issue with asset copy when raw_url is used

Improvement

• upgrade the Liquid enigne to the newest version (mainly performance optimizations)
• do not cache Page by default when creating a new Page via the admin_page_create mutation

New Feature

• possibility to add [app/config.yml] to configure feature flags per Instance for backwards compatiblity. Currently, the only supported config is escape_output_instead_of_sanitize which takes no effect, as the new feature will be deployed separately.
• new [digest] filter

Bug Fix

• gracefully handle invalid bcrypt hash instead of raising 503
• issue with importing users when invoking multiple instance copy
• gracefully handle socket error when using API call notifications
• gracefully handle invalid recipient when using email notifications

###New Features

• New attributes for ins-thumbnail, button-label, button-color, button-icon and button-type
   
   

Improvements

• Cropping in ins-image-picker is now optional
• Removed duplicate font icons
• Remove inner shadow of Data Entry components in mobile view
   
   

Bug Fixes

• Fixed broken styles of ins-tab, ins-input-multiple and ins-input-tel
• Fixed ins-table pagination display when there is no data
• Fixed ins-sidebar logo rendering in mobile view
• Fixed touch highlight style in mobile view

Improvement

• description for GraphQL PropertyFilterInput
• possibility to sort admin_pages via the content_updated_at property
• deleted models will return the correct model_schema_name instead of "DELETED" (unless model_schema is also deleted)

Bug Fix

• empty model_schema yml is no longer skipped during export/deploy

Improvement

• [EXPERIMENTAL] New routing engine, which allows you to use named parameters in slug. For more information, visit [routing improvements details]
• properties with the type array will have the default value of [] instead of null
• allow to undelete Page

Bug Fix

• edge case scenario when the legacy slug user property was changed even if first_name and last_name were not
• asset_update mutation failing in some edge case scenarios
• hash_assign failing without proper description in case of syntax error
• admin_pages GraphQL query when handler field was included in the result set
• sorting by property in GraphQL queries will put null values correctly at the beginning/at the end

Bug Fix

• fixed casting ids in the old importer
• better handling of the exception when trying to move non-existing asset
• fixed ordering when a property contains null values (nulls will be last)
• fixed passing false value to thelog tag

###New Features

• New API for ins-input-tel getValues()
   
   

Improvements

Improved validation and error handling of ins-input-tel

Improvement

• do not automatically cascade destroy children models when destroying User

Bug Fix

• fix issue with displaying layout when dynamic cache was enabled for Page
• fix issue with accessing layout metadata when using background tag in the Page
• handling wrong credentials for sending emails
• handling scenario when multiple deprecated imports were run in parallel/operations were invoked while running import
• session_create_field mutation will take immediate effect instead of after Page reload

Bug Fix

• issue with invoking different GraphQL queries within a loop
• edge case scenario when sign up with the same email exception is not gracefully handled
• gracefully handle scenario when array operators are used against properties with null values