| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \ |
|
| | | |
| | |
| | |
| | |
| | | |
We are getting spam submissions of e.g. alert subscribe form,
which causes people to get a confirmation email.
|
| |\ \ \
| |_|/
|/| | |
|
| | |/
| |
| |
| | |
Match the identical code for anonymous reports.
|
| |/ |
|
| |
|
|
|
|
|
|
| |
When compiling the reporting category dropdown, only one instance of
each value was used. But if a value appears twice, from two different
bodies, in different groups, it would then not appear in all the groups
it would be expected to. Make sure we update the list of groups of the
category if we come across another with the same value.
|
| | |
|
| |
|
|
|
|
|
|
| |
Add an interface to enable a category to accept anonymous reports, plus
the code to handle permitting this.
It's only available on single body cobrand sites in the default
configuration.
|
| |
|
|
| |
Include name, email and body rather than just user id.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Shortlist buttons and extended print information
will not appear where not allowed.
|
| | |
| |
| |
| |
| |
| |
| |
| | |
Users with assigned_categories_only will only see staff features on a
report page in their assigned categories.
Users will only see staff features on a report page in a category with
assigned_users_only if it is in their assigned categories.
|
| | |
| |
| |
| |
| | |
Look up user's permissions once at the start, and
use that throughout the report page templates.
|
| |/
|
|
|
|
| |
If you rename an Open311 category when it is not protected, it will only
get reinstated/deleted by the Open311 populate script shortly after, and
can cause issues due to the problem category renaming that occurs.
|
| |
|
|
|
|
| |
The change to join in e16054150 did not include a collapse that the
previous prefetch was doing, so multiple rows per result were being
returned.
|
| |\ |
|
| | | |
|
| |/
|
|
|
| |
Add a tickbox to the category admin, and do not allow reopening on
reports made in the selected categories.
|
| |
|
|
|
| |
Add a tickbox to the category admin, and do not allow updates on
reports made in those selected categories.
|
| |
|
|
|
|
|
|
|
|
|
| |
On admin report lists, and in front-end lists when an inspector, each
row was querying the database for `category_display`. We create a new
relationship for this query, and join/prefetch it wherever we request
this data.
Include staff joins on /around page, copying what happens on /reports
to prevent more lookups there too. Also add some joins for user email
in admin report list.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| | |
The export flow and the admin search request more data
from the database than they need, which slows it down.
|
| | | |
|
| |/
|
|
|
|
| |
If the web param is used, show an error web page rather than the normal
plain text output. Also do the normal remember/show uploaded photos
feature, and hide the inputs better if unneeded.
|
| |\ \
| | |
| | |
| | | |
'2962-pin-move-category-group' and 'move-admin-index-stats-to-stats-page'
|
| | |/
| |
| |
| |
| | |
These stats can take a while to generate, and we don't want to slow
down people mostly coming to the admin index to do something else.
|
| |/
|
|
|
|
|
| |
Adds a new tickbox to the contact editing form that protects the category
and group names from being changed by Open311.
For mysociety/fixmystreet-commercial#1776
|
| |
|
|
|
| |
Restrict cobrand to HE categories. Want to do it by body, not category,
because otherwise there's a "missing" council body.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
On an around page on the HE cobrand, both bodies (HE and council) are
listed and so when you clicked the map (not on a HE road) the not-HE
code did not fire because it wasn't the only body present. But New.pm
calls only return the HE body because they call munge_report_new_bodies.
So it worked when you picked category/ moved pin. Around should call the
munge function too so bodies is set up same as on New.pm.
We need to always use the cobrand package, regardless of if it is a
valid cobrand or not (for e.g. Bromley/Hounslow tests).
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Make it a bit easier to see if any reports have been sitting unsent for
some time
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
If you submit the non-JS image map from an around page with a particular
category selected, that is sent to the server in filter_category and
should be checked to see if we can pre-fill the category dropdown on new
report.
|
| |\ \ |
|
| | |/
| |
| |
| |
| | |
This state will appear when reporting if you are logged in as a staff
member of the relevant body, but otherwise not appear on the site.
|
| | | |
|
| | |
| |
| |
| | |
This saves hammering the FS for every front page request
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
|
|
| |
If a SQLite file exists at `../data/analytics.sqlite` with a table
named `location_searches_with_no_results`, then a row will be created
for each /around search that returns no results.
Could come in useful for anybody running an instance and looking to
better understand how well their geocoder is performing.
|
