| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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).
|
|/ |
|
|
|
|
| |
It was not being caught by rerun_dbic_loader.pl otherwise.
|
| |
|
|
|
|
|
|
| |
Update database to store an array of IDs rather than only one;
consequential changes to the admin and the dashboard to allow
selection.
|
| |
|
|
|
|
|
|
|
| |
If set then when the user creates a new body report it will prefill the
report title and description with some basic text.
For mysociety/freshdesk#23
|
|
|
|
|
|
|
| |
If a user has this permission then the report_as dropdown will
default to reporting as the body.
For mysociety/freshdesk#23
|
|
|
|
|
|
|
|
| |
Allows user's to see the inspector panel to mark reports as Private, and
also to view those non-public reports. Useful for call centre staff who
want to record private reports but don't need to other permissions.
Fixes mysociety/fixmystreet-commercial#1213
|
|
|
|
| |
disable, enable and delete for user alerts on user_edit page
|
|
|
|
|
|
|
| |
Add a count of currently active alerts on new updates for a report to
the admin page.
Fixes #669
|
| |
|
|
|
|
|
|
| |
Use a HashRefInflator wherever all_sorted is used, with consequential
changes to deal with it now not being an object (e.g. add some with_*
functions for manual fetching of extra data).
|
|
|
|
|
| |
If an admin with the user_edit permission but not user_assign_body
edited a user with from_body set, the from_body field was lost.
|
|
|
|
| |
Fixes mysociety/fixmystreetforcouncils#275
|
|
|
|
|
|
|
|
|
| |
Add a button to the user edit page that sends a login token email to the
user. Helpful for user support situations where someone is having
trouble logging in. Also for situations where you have added a user and
want to get them logged in.
Fixes #2041
|
|
|
|
| |
The User model now also has a created column.
|
|
|
|
|
|
|
|
| |
Display fields that are automatically filled in the contact editing form
otherwise the data is lost. Also include the automated field in the
form.
Fixes #2136
|
| |
|
|
|
|
|
| |
Both filter categories and new report category lists went through mappings
to different data structures, which doesn't seem to be needed.
|
|
|
|
|
|
|
|
| |
Instead of just a Yes/No display a formatted list of values in extra.
Has special handling for known fields otherwise just prints them out
dumbly.
Fixes #1809
|
|
|
|
|
|
| |
UI to update the fetch_all_problems setting in extra for a body. This also
adds handling for extra body values in the Admin in a similar manner to the
way other body params are handled.
|
| |
|
| |
|
|
|
|
|
| |
If you rotated a photo, updates and the category list weren't loaded. If you
changed a report's state, the map pin colour was derived from the old state.
|
|
|
|
|
|
|
| |
Previously this would force phone_verified to false for all user edits,
as well as forcing email_verified to true - which would be the wrong thing
to do if the user had been created/verified via the ‘report as another user’
flow.
|
| |
|
| |
|
|
|