| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
Closes reports that meet the following criteria:
* status is action scheduled
* in a category with a fixed - council auto response template
* over n days in action scheduled state (n is an argument)
Reports matching these criteria are marked as fixed - council and the
relevant response template text is added as a comment.
Fixes mysociety/fixmystreet-commercial#1955
|
| |
|
|
|
|
|
|
| |
Given the user, we can infer the name if not provided, and the extra
data if a staff user. We can also provide defaults for various other
fields. Always have superuser take precedence over from_body.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The change in cc2b8f54 made a typo in the default argument.
|
|
|
|
|
|
|
|
|
| |
B&NES have sent us a spreadsheet with a list of reports along with their
IDs that they want marking as "No further action" along with a specific
update.
This script takes a comma-separated list of report IDs and closes those
reports, leaving the appropriate comment text.
|
| |
|
|
|
|
| |
This means the code can assume it should be trying to send a report.
|
|
|
|
|
| |
Use verbose for all log output, and debug only for
overriding the should_skip check.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Without the brackets the user's name was interpreted as a separate
recipient.
Fixes #2935
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
If report made on .com, `body->get_cobrand_handler` does not return TfL
as it covers many bodies. Now we have the body handler, we can use that
instead.
|
|
|
|
|
|
| |
For an email to somewhere for which the report has a body handler, we
want to use that cobrand's domain for the link - we already are using
their cobrand for the email template, after all.
|
| |
|
| |
|
|
|
|
|
| |
This was passing the cobrand object so the checks in State::display that
were relying on the moniker were not working.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update:
* Catalyst
* Specify Catalyst::DispatchType::Regex explicitly
* Remove Catalyst::Plugin::Unicode::Encoding
* Catalyst::Plugin::SmartURI
* Specify URI::SmartURI explicitly
* Catalyst::Plugin::Static::Simple
* CGI
* Class::Load
* DateTime
* DateTime::TimeZone
* DBD::Pg
* DBIx::Class
* DBIx::Class::EncodedColumn.
* Email::Address.
* Email::MIME
* ExtUtils::MakeMaker
* ExtUtils::ParseXS (for Params::Classify upgrade)
* File::ChangeNotify
* Image::Size
* IO::Socket::SSL
* local::lib
* Moo
* Moose (and some related others due to deprecations)
* namespace::autoclean
* Net::Server
* Net::SSLeay
* Number::Phone
* Plack
* Starman
* Template
* Test::PostgreSQL
* Test::WWW::Mechanize::Catalyst
* Text::CSV
* YAML
carton install was run on a wheezy box, the oldest that is supported, to
make sure the required minimal vesions of core modules weren't removed
from the snapshot. Cpanel::JSON::XS, Devel::GlobalDestruction::XS, and
MooseX::NonMoose were then put back in the snapshot, in case another
system needs them (e.g. system Perl on Mac looks for MooseX::NonMoose).
|
| |
|
|
|
|
|
|
|
| |
->first, as used in cd8a5702, uses the iterator, so ->next will then
only return the second onward. Instead, do the needed thing in the
first iteration of the loop. Also check the option is set as some
scripts do not set it.
|
|\ |
|
| | |
|
|/
|
|
|
|
| |
Previously if no reports were closed with an email this meant that the
lang setup never ran and you got an error when _ was called in
close_problems. So, we call the lang setup in close_problems too.
|
|
|
|
|
| |
It can be hard to see where one error stops and a new one begins in the
send reports error emails so put in a more obvious break between them.
|
|
|
|
| |
Fixes #1957
|
| |
|
|
|
|
|
|
|
|
| |
As perlsyn says, "NOTE: The behaviour of a `my`, `state`, or `our`
modified with a statement modifier conditional or loop construct (for
example, `my $x if ...`) is undefined. The value of the `my` variable
may be `undef`, any previously assigned value, or possibly anything
else."
|
| |
|
|
|
|
| |
Fixes mysociety/fixmystreet-freshdesk#24.
|
| |
|
| |
|
|
|
|
| |
So we can use this in collideoscope
|
|
|
|
|
| |
So we can use it for collideoscope which does not use a fixed end
period.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Hitherto when creating a body or ward alert on a UK site,
the MapIt area ID has been stored instead of the body ID.
This is okay for www.fixmystreet.com which for historical
reasons does have body IDs that match MapIt area IDs, but
other UK-based sites may well not. The alert lookup looks
for body ID, meaning those alerts will not work. Save the
body ID instead, plus fix some tests that were making the
same assumption.
|
|\ |
|