app/templates/partials/check/message-too-long.html

{% from "components/banner.html" import banner_wrapper %}

<div class="bottom-gutter">
  {% call banner_wrapper(type='dangerous') %}
    <h1 class='banner-title'>
      Message too long
    </h1>
    <p>
      Text messages cannot be longer than {{ SMS_CHAR_COUNT_LIMIT }} characters.
      Your message is {{ template.content_count }} characters.
    </p>
  {% endcall %}
</div>
add other send notification error branches and tests 2017-06-29 16:06:36 +01:00			`{% from "components/banner.html" import banner_wrapper %}`

add template partials for some notification checks also move out some from the check.html page. This is going to help with sharing templates between single notifications and csv files. 2017-06-29 12:23:42 +01:00			`<div class="bottom-gutter">`
			`{% call banner_wrapper(type='dangerous') %}`
			`<h1 class='banner-title'>`
			`Message too long`
			`</h1>`
			`<p>`
Replace can't with cannot 2019-09-12 16:51:49 +01:00			`Text messages cannot be longer than {{ SMS_CHAR_COUNT_LIMIT }} characters.`
make partials source-agnostic they're currently expecting a RecipientsCSV object - but we won't always have that available if we're handling a single notification. So make the partials take generic variables, and then use a jinja with block to pass in the correct values from either the check csv page or the check notification page. Additionally set the notification check page to show errors nicely - hide the send button if there were problems, and replace the header 2017-06-29 15:33:31 +01:00			`Your message is {{ template.content_count }} characters.`
add template partials for some notification checks also move out some from the check.html page. This is going to help with sharing templates between single notifications and csv files. 2017-06-29 12:23:42 +01:00			`</p>`
			`{% endcall %}`
			`</div>`