| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
Prevent people from using very long titles.
Fixes mysociety/fixmystreet-commercial#1344
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The previously staff-only fixmystreet.set_up.manage_duplicates() has
been promoted from staff.js to its own file so that we can use it to
display the duplicate suggestions on the `/report/new` form.
render_duplicate_list (the old refresh_duplicate_list) no longer filters
or slices the reports_list returned by the ajax call, since it turns out
the server handles all of that (`sub _nearby_json` in `Report.pm` and
`sub nearby` in `Nearby.pm`).
Since the expandable list items include the "fancybox" image previews,
the fancybox CSS now has to be included in the `/report/new` page head,
hence the addition of "photo-js.html" in `fill_in_details.html`.
The “Get updates” flow reuses the same JavaScript that handles the
submission of the "Get updates" drawer at the bottom of around pages.
|
| |
|
|
|
|
|
|
|
|
|
| |
use the bodies array of reporting_data to check if there is council
specific javascript validation and, if so, load that into the JS
validation rules.
This does mean we reset the validation rules each time you select a
category.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
|
|
|
| |
This removes unnecessary whitespace to reduce the output size.
|
|
|
|
| |
A confirmation code is sent via Twilio to be entered on the site.
|
| |
|
|
|
|
| |
Plus a few new ca_ES strings.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit makes the following parts of the site translatable:
- Social login buttons
- Moderation UI
- Offline glitch page & offline caching UI
- Dashboard
It also fixes a bug in the nget parser, stops some Oxfordshire bits
being translated for the moment, and brings the translation file up
to date.
|
|
|
|
|
|
|
|
| |
This improves usability on mobile devices, allowing users to pan around
the problem and see the area in more detail.
I've also changed the CSS around a bit, so we can use the
`map-fullscreen` class in other places.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Users with the `report_inspect` permission can click a new 'inspect' button on a
report page to input more detailed problem information into a new form that
appears in a column alongside the report detail.
- Inspector data is stored in problem's 'extra' field
- Report category/state can be edited
- Location can be changed by dragging the pin or HTML5 geolocation
(Factored out Zurich admin pin drag into own function)
For mysociety/fixmystreetforcouncils#22
|
| |
|
|
|
|
|
| |
No need for this to be generated via a template, it only differs
occasionally by cobrand.
|
| |
|
|
|
|
| |
Makes the flow more like new reporting.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Three file inputs, progressively enhanced with dropzone.
This moves the photo input higher up, so that photos can upload while
you're filling out the form. It standardises and improves photo error
handling.
[fixmystreet.com] Guidance for what photos should and shouldn’t include.
|
| |
|
|
This should reduce confusion with the Default cobrand and override order.
|