From 4eea8bfe5793915741c9e4eb591c4bdf633daf5c Mon Sep 17 00:00:00 2001 From: Tom Byers Date: Wed, 1 Jul 2020 14:24:27 +0100 Subject: [PATCH] Add variant page for service-settings/name Includes correction of class used for bulleted list. --- app/main/views/service_settings.py | 6 ++++++ app/templates/views/service-settings/name-local.html | 4 ++-- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/app/main/views/service_settings.py b/app/main/views/service_settings.py index ef8a78117..9aa2257e8 100644 --- a/app/main/views/service_settings.py +++ b/app/main/views/service_settings.py @@ -104,6 +104,12 @@ def service_name_change(service_id): session['service_name_change'] = form.name.data return redirect(url_for('.service_name_change_confirm', service_id=service_id)) + if current_service.organisation_type == 'local': + return render_template( + 'views/service-settings/name-local.html', + form=form, + ) + return render_template( 'views/service-settings/name.html', form=form, diff --git a/app/templates/views/service-settings/name-local.html b/app/templates/views/service-settings/name-local.html index 782183810..58cece252 100644 --- a/app/templates/views/service-settings/name-local.html +++ b/app/templates/views/service-settings/name-local.html @@ -17,7 +17,7 @@ ) }}

Your service name should tell users what the message is about as well as who it’s from. For example:

-