| Commit message (Collapse) | Author | Age | Lines |
|\ |
|
| |
| |
| |
| | |
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.
|
| | |
|
| | |
|
|/
|
|
| |
(VERSION disappears in some recent version.)
|
|
|
|
|
| |
Also takes the opportunity to fix the incorrectly-encoded sender name which
was appearing to some clients as "Züri Wie Neu".
|
|\ |
|
|/ |
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
This improves create_user_ok to work more like create_body_ok where extra params
can be passed in and set on the model.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
- 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
|
|\ |
|
| |
| |
| |
| | |
This also updates the body column to match the category.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
If a category had eg. a double space, the use of the filter meant it
was output in the HTML with only a single space and so woudn't match
the database entry. Switch to more explicit template space chomping.
|
| | |
|
|/
|
|
| |
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.
|
|
|
|
|
| |
Missed this from 8a8b34, and it was causing a crash on certain /reports/ pages
when trying to display the list of problems.
|
|
|
|
| |
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.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Previously, pressing the mobile menu icon would change the location
hash, which fired a history popstate event with an empty state object,
causing trouble for our map page JavaScript.
Now, pressing the mobile menu icon triggers a pushState, instead of
changing the location hash. This means our map page popstate logic is
unaffected, but mobile users can still use their browser's Back button
to escape out of the mobile menu.
|
| |
| |
| |
| |
| | |
Update the URL whenever location of pin is updated (first time, drag, or
reclick), make sure it works when clicking back.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Include URL changing, using history.pushState.
Show a larger marker icon for the selected report.
Make sure title is updated, and correct sub_map_links are shown.
The /report/new template is now wrapped in a <div id="side-form">
rather than <div id="side"> for consistency with the /around page,
which keeps display_all_reports_in_area() simpler, because it can
always assume "#side" means "list of reports".
|
| |
| |
| |
| |
| | |
On mobile, the notes in `#report-a-problem-sidebar` are hidden by
default, and can be toggled using the `.rap-notes-trigger`.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Split big functions into smaller more descriptive ones.
|
| | |
|
|\ \ |
|