| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| |/
|
|
|
|
|
|
|
|
|
| |
This builds on the response templates in the Zürich cobrand:
- Allow response templates to be assigned to categories
- Also adds a auto_response flag, which will be used to automatically create
updates when reports are made.
- Include response templates select box on update form
For mysociety/fixmystreetforcouncils#31
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
- Harmonise two-column sidebar with .with-notes convention
`body.mappage.twocol` is now `body.mappage.with-actions` to make it
more obvious that it’s just a special case like `.with-notes`.
- Make sidebar padding-bottom work with floated children
- Display a.btn elements correctly in Safari
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
If the form is submitted and reshown, due to an error or logging in, the
image preview is loaded from the server, rather than the client. We need
to get the image source data to get the Exif data out of it.
|
| |
|
|
|
|
|
|
| |
This refactors the moderation JS into a fixmystreet.set_up function, and
ensures the button handlers are attached when a new report is loaded
over AJAX. A side effect of bringing it into fixmystreet.js instead of
its own moderate.js file is the few extra kb each user will have to
download, but hopefully gzip and caching will help ameliorate this.
|
| |
|
|
|
|
| |
When the form is shown via JavaScript, we need the email box to start
off editable as it is if you hadn't used JavaScript, and we also need
the change() to be fired on the right field.
|
| | |
|
| |
|
|
|
| |
e.g. if a report is pulled in to the page via JavaScript, we need this
to run on the entry in the update form.
|
| |
|
|
|
|
| |
A user with the appropriate permission can add/remove reports from their
list of planned reports using a button on a report page. The list can be
viewed at /my/planned.
|
| |
|
|
| |
This makes sure the correct dropdown is shown.
|
| |
|
|
|
|
| |
The map JavaScript assumes that the permalink div already exists.
[Bristol] Make sure the control is added.
|
| |
|
|
|
| |
Remove unused code that is same as upstream (it was added when the map
middle didn't match the visible middle), and the world button.
|
| |
|
|
|
| |
No need to use old OpenLayers PanZoom defaults, or load images we don't
want to use.
|
| | |
|
| |
|
|
| |
This was originally fixed in c36a425b, but lost again in c87f28e.
|
| | |
|
| |
|
|
| |
Even though it is empty.
|
| |
|
|
| |
Prevent possible infinite loops during internal hashref change.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
No need for a special no-map case in the filters case, as all pages now
have fixmystreet.page set if needed.
|
| | |
|
| | |
|
| |
|
|
|
| |
We only need html5shiv for <IE9, and we only use yepnope on the front
page.
|
| |
|
|
|
| |
Otherwise subsequent report views set the Back link to a report URI, so
clicking it goes back to the list but with an incorrect address.
|
| |
|
|
|
| |
Problems nearby should load the /around page from those pages, rather
than act like "Back to all reports" but changing to an incorrect URL.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This allows users who have the correct permissions to add reports on
behalf of the body or another user.
We enable editing of the email box by default, so that if JavaScript
isn't available, someone can still change the email for the 'another
user' option.
For mysociety/fixmystreetforcouncils#10 and
mysociety/fixmystreetforcouncils#11
|
| |
|
|
|
|
| |
Temporarily removes the councils page as the information was out of date.
Replaces it with a holding page. New page is on the way.
|
| | |
|
| |
|
|
| |
Email themes for Oxfordshire, Bromley, Warwickshire, and Greenwich.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
pushState stores the title at the time for e.g. the Back dropdown.
|
| |
|
|
|
| |
This is so form valdation and the 'log in by email' button are set up
appropriately if pulled in via JavaScript.
|
| | |
|
| |
|
|
|
| |
Have 'Get updates' displaying correctly on a report page again,
fix some navigational problems.
|
| |
|
|
|
|
| |
Record the original page we're at, so that when we go back to it,
we go back to the right one (the only difference between /around
and /reports being the full screen map of /around).
|
| | |
|
| |
|
|
|
| |
This prevents scrolling when we're on the full screen map, and makes
sure the map is back in view when it is shown.
|
| |
|
|
|
| |
Some older browers will fire a popstate event at page load, which can
cause an issue if we assume it's only fired due to a history event.
|
| |
|
|
|
|
|
| |
Don't stringify pin problem ID, as get_marker_by_id assumes it will be
an integer; only activate the bounding box strategy if it exists; make
sure a refresh of the markers happens when going back to the list; set
the Back link on a pulled-in report to the current URL.
|
| |
|
|
| |
Use $.each rather than .forEach.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Having them as SDK-included buttons causes issues with the ajax
report pull-ins, plus Firefox doesn't like them being hidden.
|
| | | |
|
