| Commit message (Collapse) | Author | Age | Lines |
... | |
|
|
|
| |
Fixes a bug with updates not being displayed correctly in the app.
|
|
|
|
|
|
|
|
|
| |
Searches the `id` and `external_id` fields.
This takes you directly to the report if only a single report matches, otherwise
a disambiguation page is shown.
For mysociety/fixmystreetforcouncils#16
|
|
|
|
|
| |
The config page is only accessible by superusers.
The stats page only shows figures for the user’s from_body unless superuser.
|
| |
|
|
|
|
|
|
|
|
| |
The 'user_edit' permission is required to edit users.
The admin pages on UK council cobrands only allow editing of users whose
from_body is the same as the logged-in user, or who have sent reports or updates
to the council.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Design is all Zarino. This adds the ability to send HTML emails,
including attached inline images. When included, this is done as a
multipart/related email containing a multipart/alternative (of plain and
HTML) and any attached images, so that the images are available even if
HTML mail is not.
The alert emails list data has been improved so it can be constructed in
the templates rather than the code. Various templates have been tidied.
Various workarounds for email clients have been made, including:
* <th> is used so that the Android 4.x mail client can give them
`block` styling in the small screen media query.
* Font settings defined on every table cell (<th>) so that sans-serif
fonts are used in Outlook, rather than Times New Roman.
* A three-column wrapper table to create a 620px centred content area
that also shrinks down on narrow screens. (Outlook doesn’t like
max-width, so this is the simplest alternative.)
* Enforcing a sensible (500px) min-width for the main content area,
on clients that don’t support media queries (eg: native Gmail app).
* Giant borders on buttons so Outlook displays them
* Image alignment with align rather than float.
|
|
|
|
|
| |
Also takes the opportunity to fix the incorrectly-encoded sender name which
was appearing to some clients as "Züri Wie Neu".
|
| |
|
|
|
|
|
|
|
|
|
| |
- Adds is_superuser flag to User
- Logged-in user must be a superuser or have from_body set in order to access
anything within /admin
- has_permission_to on a superuser will always return true
- Only superusers can create/grant superusers
- New `createsuperuser` command for creating superusers
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is a concern that excluding district council reports from a two-tier
council's cobrand's /around page might lead to duplicate reports or reports
never being seen.
This commit adds them to the map and the sidebar and displays the destination
council in the report list item. Clicking the pin or the report link leads to
the report on FMS.com.
Reports sent to the a council other than the the active cobrand are shown as
grey pins on the map, and the receiving council's name is shown in the sidebar
list.
|
|
|
|
|
|
|
|
|
| |
When viewing a report on FMS.com whose recipient council has a
FMS cobrand, turns the council name into a link to view the same report
on that council's cobranded site.
Includes methods cribbed from Hakim's Open311 refactor branch from
commit 47daa02420a4f5a4264c31efcf2a2e8611c2f23e.
|
|
|
|
|
| |
Instead of using BASE_URL as the base URL on council cobrands when STAGING is
true, use the UK councils default (which is cobrand name prepended to BASE_URL).
|
|
|
|
| |
For mysociety/FixMyStreet-Commercial#773.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a new Cobrand::Default::categories_restriction method that can be used
to limit what categories are available when making a new report on a per-cobrand
basis.
This is used by Cobrand::Bristol to only show Open311 categories when making a
new report on fixmystreet.bristol.gov.uk but allowing all categories on FMS.com.
Also removes the Hart::hidden_categories and uses the new categories_restriction
method to achieve the same thing.
|
| |
|
|\ |
|
| |
| |
| |
| |
| | |
Tidy up use of absolute URLs when in the admin.
Have the 404 handler spot static files in admin as a fallback.
|
|/ |
|
|
|
|
| |
Default future unknown ones to HTTPS.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This refactors the Map::Zurich module into something that makes it easier
to use custom map tiles for a cobrand.
This also includes some refactoring of the JS & map templates
to make it easier to use a custom WMTS base map in future
cobrands.
|
| |
| |
| |
| | |
For mysociety/FixMyStreet-Commercial#766.
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some UK councils with Open311 integrations (e.g. Bromley) have a custom wording
in the confirmation email sent when updates are left on reports, to make the
user aware that the update is sent to the council in question.
Bromley noticed that some emails were being sent without this wording, leading
at least one user to contact the council directly about the report.
It turns out that although the email template contains an IF clause to use the
appropriate wording for Bromley (and Stevenage) reports, the incorrect template
file was being used when updates were made via the Bromley cobrand.
This commit solves the problem by introducing a new
`Cobrand::Default::path_to_email_templates` method, which is overridden by
`Cobrand::UKCouncils` to include the `templates/email/fixmystreet` path. Paths
returned by this method are used as the `additional_template_paths` param when
templating emails. A regression test is included.
Additionally moves email templates for fixmystreet.com to a directory name
reflecting their purpose, in the same way the web templates are arranged.
|
| |
|
|
|
|
|
|
|
| |
Historically, emails sent offline (alerts, questionnaires, etc) used a
different templating system from those sent by the website (e.g. login
emails), though the newer system was also being used for the site name
and signature of offline emails.
|
|
|
|
| |
And associated, e.g. nothing references fixmystreet-old-box.js any more.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
Store image type along with hash in photo column, and use that when
outputting images / generating URLs. Make sure all public photo URL
generation goes through appropriate functions, and change temp URLs
so the filename can be output directly from the list.
|
|/
|
|
| |
Fixes #574.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
There's no need for the IP->country lookup, only used in JavaScript
to display a banner, to require a call to the FixMyStreet server.
|
| |
| |
| |
| |
| |
| | |
Some img tags were using http://[cobrand].fixmystreet.com/ URLs
when their including page was served over HTTPS, causing mixed
content warnings on IE.
|
| |
| |
| |
| |
| |
| | |
lighting reports
Fixes mysociety/FixMyStreet-Commercial#767
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Angus provide a WFS endpoint for their existing streetlight assets
and known faults.
This commit:
- Displays clickable markers when the 'street lighting' category is selected
on the report a problem page.
- Displays known faults on the map
- Includes a custom OpenLayers build for the Angus cobrand that
includes WFS support
The custom code for adding the layers to the map is within
position_map.js, as this seemed to be currently the best place
for cobrand-specific map logic.
|
| | |
|
|/
|
|
|
| |
This adds a cobrand for Angus Council that fits in with their
existing styling on angus.gov.uk
|
|
|
|
|
|
|
|
| |
Includes a smiley, bright yellow homepage, and updated nav bar and
footer across the entire site; a few content changes; request for
gender information from users.
Fixes #1341.
|
|
|
|
|
|
| |
This adds a new cobrand variable, report_form_extras, which contains a
list of extra fields that will be saved in the 'extra' metadata of the
report. Fields may optionally be marked as required.
|
|
|
|
|
| |
It is currently only used for processing extra fields (the list, not the
metadata hash) which is really only of relevance to Open311.
|
|
|
|
| |
Fixes #1337.
|
|
|
|
|
|
| |
Travis has Cpanel::JSON::XS preinstalled, which means that the build
would fail there, as JSON::MaybeXS would try and upgrade JSON::XS to
version 3 which the snapshot did not contain.
|
|
|
|
|
| |
Remove get_photo_params, which only looked at the first photo,
make explicit when we're doing that using `.first`.
|
|
|
|
|
|
|
|
|
|
|
|
| |
5c79337 simplified a bit too far, as after then a particular cobrand
could in Nearby and My only filter reports to a particular body, not
any other criteria. To fix this, introduce more generic functions in
the default cobrand to allow more flexibility.
Make sure a few tests delete their bodies fully so that new tests
pass when run as part of the suite.
Fixes #1289.
|
|\ |
|