| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| | |
So version 2.4.1 has no translation changes, putting back straight after.
|
|/
|
|
|
| |
Adds some div wrappers round the non category bit of the form so we can
then hide easily.
|
| |
|
| |
|
|
|
|
| |
Fixes #2263.
|
|
|
|
|
| |
The change to web/js/front.js was required because Oxfordshire has no
`.report-a-problem-btn`, so the front.js shouldn’t assume it’s there.
|
|
|
|
|
|
|
|
| |
The reference number is a) the FMS report id which is irrelevant and b)
we don't get an OCC reference number back immediately so could not show
it anyway.
Related to mysociety/fixmystreet-commercial#1193
|
|
|
|
|
| |
OCC uses the customer reference from extra to store the enquiry
reference so use that on the report page rather than external_id.
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
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).
|
|/
|
|
| |
For mysociety/fixmystreet-freshdesk#16.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now that the "Report a problem" link in the nav bar links, more often
than not, to the reporting form rather than the homepage, it could be
challenging to actually start a new report in a location *other* than
the one currently on screen.
Rather than adding a link to the homepage, this change hopefully adds
a link right at the moment the user expects it – right on the "Report
a problem" form.
It also gave us an opportunity to reword the "Wrong location" message
and give it an icon more suitable for high-dpi displays.
Fixes #2238.
|
|
|
|
| |
Fixes #2235.
|
|
|
|
|
| |
Provides a template override for cobrands to show if updates aren't
allowed on the problem.
|
|
|
|
|
|
|
|
| |
if a web parameter is passed to /import then display the email
confirmation sent page rather than a SUCCESS message. Enables this page
to be used for creating partial reports from a web page.
For mysociety/collideoscope#17
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
|\ \ |
|
| |/ |
|
| | |
|
|/
|
|
|
|
| |
Add by_category output to the /report/new/ajax call, containing all the data
that /report/new/category_extras returns for one category. Then alter the JS
to use that data immediately when needed.
|
| |
|
|\ |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Previously, if you didn’t want a hint to appear under the main "details"
textarea on the new report form, you had to override the entire
`form_report.html` template, or leave the hint element in the markup but
hide it with CSS.
Now, you can set `form_detail_placeholder` to a falsey value, and the
template won’t output the hint element at all. It also amends the
`aria-describedby` attribute on the textarea so it doesn’t end up
referencing a hint element that doesn’t exist.
|
|
|
|
| |
Lincolnshire uses ‘division’ instead of ‘ward’ as well as Oxfordshire.
|
| |
|
| |
|
|
|
|
| |
confirmation page
|
| |
|
| |
|
|
|
|
| |
This was causing layout issues on the Lincolnshire cobrand.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #2016.
When you load a page that includes either a problem report, or is
centered on a location, the "Report a problem" button in the nav bar
(that normally takes you to the homepage) becomes a "Report a(nother)
problem here" button, that leads directly to the new report form
for the location in question.
On full map pages (/around and any /report/<id> pages loaded via it)
the reporting form will be rendered client-side, avoiding a full page
reload.
On pages lacking the full map (eg: missing fixmystreet.bbox_strategy),
namely /reports/<area> and any /report/<id> page that hasn’t been
client-side loaded via /around, we fall back to a server-side page load.
Finally, as you’d expect, the text and URL for the button dynamically
update as you move around the map, or switch between the different
client-side states of the reporting flow.
We also hide the button entirely when you’re reporting a problem,
which was something suggested a long time ago.
|
|/
|
|
|
|
|
| |
Part of #2012.
Should make it much quicker to report multiple problems in the same
location, one after the other.
|
|
|
|
| |
Fixes #2197.
|
|
|
|
|
|
|
|
| |
add a do_not_send parameter to reports which allows the front end to specify a
comma separated list of bodies that reports should not be sent to even if
there is a valid contact match. This enables asset layers to override backend
body processing, e.g. if a body only accepts reports that are on a road this
allows the front end to specify that.
|
|
|
|
| |
currently will show even if it's only appropriate for one body
|
|
|
|
|
|
|
| |
Also add body name to layer defaults, so they are only used where appropriate.
Switch mapit area javascript calls to GeoJSON, so we can drop KML support in
OpenLayers.wfs.js which saves a small amount of bandwidth.
|