diff options
| author | Dave Arter <davea@mysociety.org> | 2018-01-18 12:02:00 +0000 |
|---|---|---|
| committer | Dave Arter <davea@mysociety.org> | 2018-01-23 15:46:09 +0000 |
| commit | b3d26a80a0728e49d857c0fe5cbc2966512561ff (patch) | |
| tree | d8a58f095fbd0268c5b8d328ed2cc16b564fee74 /t/cobrand | |
| parent | 6e415f3c6d9355312b9fb84e4ecdb68f96cff618 (diff) | |
Hide 'updates not sent' message on reports sent via Open311
The 'updates are not sent to the council' message was incorrectly being
shown on reports where updates would in fact be sent. This was affecting
non-Bromley/Stevenage reports on fms.com and all cobrands using Open311.
This commit moves the logic out of the template and adds the
Problem->updates_sent_to_body method which inspects the receiving body's
Open311 configuration to determine whether updates will be sent.
The duplication of the Lewisham/Oxfordshire logic between Problem.pm and
send-comments isn't ideal but hopefully there won't be any new Open311
bodies that only send and don't receive updates. If there are we'll have
to look at refactoring that list.
Diffstat (limited to 't/cobrand')
| -rw-r--r-- | t/cobrand/bromley.t | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/t/cobrand/bromley.t b/t/cobrand/bromley.t index a3a807bb1..41e351dea 100644 --- a/t/cobrand/bromley.t +++ b/t/cobrand/bromley.t @@ -49,7 +49,7 @@ $mech->content_contains( 'State changed to: No further action' ); subtest 'testing special Open311 behaviour', sub { $report->set_extra_fields(); $report->update; - $body->update( { send_method => 'Open311', endpoint => 'http://bromley.endpoint.example.com', jurisdiction => 'FMS', api_key => 'test' } ); + $body->update( { send_method => 'Open311', endpoint => 'http://bromley.endpoint.example.com', jurisdiction => 'FMS', api_key => 'test', send_comments => 1 } ); my $test_data; FixMyStreet::override_config { STAGING_FLAGS => { send_reports => 1 }, |