Releases

Documents what has changed in each release and what you need to do to upgrade.

Respond 6.3.0

What's New

The big feature of the Respond 6.3.0 release is the inclusion of the Angular CLI into the build process.  This separates the UI for the application into its own repository at https://github.com/madoublet/respond-ui.  The release also includes support for search on the pages screen and a single sign in URL.  This allows you to login to any site at the /login URL without having to specify the site's name.  

How to Upgrade

You can upgrade by following the standard upgrade instructions.  If you want to develop for Respond, new documentation is available under Developer Installation.

You will also need to specify a new LOGO URL in the .env file as this is now stored to the respond-ui repository.

LOGO_URL=/assets/resources/respond-logo.png

Respond 6.2.0

What's new

The Respond 6.2.0 release focuses on making meta data for pages better.  It introduces a new page settings UI that gives you full control of the meta data on your page and adds new syntax options for pushing data into your templates.  The new tags are documented here on the Creating Themes page.  

The release also adds some much needed usability fixes in the editor.  Now, when you delete all the text in a text block, you do not lose the ability to edit that block.

how to upgrade

Below is a sample of how your new templates should look after the upgrade.  Note the new {{page.element}} syntax for all the meta data and OG tags.  This should be updated for all your custom themes, and for your existing sites.  This can be done by going to Code > Templates in the Respond UI.

<!DOCTYPE html>
<html lang="en" dir="ltr">
  
  <head>
    <title>{{page.title}}</title>
  
    <!-- meta -->
    <meta charset="utf-8">
    <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
    <meta name="description" content="{{page.description}}">
    <meta name="keywords" content="{{page.keywords}}">
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
    <meta name="viewport" content="initial-scale=1, maximum-scale=1, user-scalable=no, width=device-width">
  
    <!-- set base -->
    <base href="../">
  
    <!-- open graph -->
    <meta property="og:url" content="" />
    <meta property="og:type" content="website" />
    <meta property="og:title" content="" />
    <meta property="og:description" content="" />
    <meta property="og:image" content="" />
  
    <!-- icons -->
    <link theme-icon href="resources/icon.png" rel="icon">
    <meta theme-color content="#888" name="msapplication-TileColor">
    <meta theme-color content="#888" name="msapplication-TileImage">
    <link theme-icon href="resources/icon.png" rel="apple-touch-icon">
  
    <!-- font -->
    <link href='http://fonts.googleapis.com/css?family=Quicksand:300,400,700' rel='stylesheet' type='text/css'>
    <link type="text/css" href="//netdna.bootstrapcdn.com/font-awesome/4.0.2/css/font-awesome.css" rel="stylesheet">
  
    <!-- css -->
    <link type="text/css" href="css/site.min.css" rel="stylesheet">
  
    <!-- google maps -->
    <script src="https://maps.googleapis.com/maps/api/js?sensor=false"></script>
  
    {{page.customHeader}}
    
  <body>
  
  ...
  
  </body>
  
  <!-- js -->
  <script src="js/site.all.js"></script>
  
  {{page.customFooter}}

</html>