| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes #2180.
Input placeholders are a generally problematic UI convention, and we’ve
accidentally started using them in more and more parts of FMS over the
last few years.
In some cases, the placeholders simply repeated text from the input’s
existing label element. In cases like those, the placeholder attribute
could just be removed.
In other cases, we broke the placeholder text out into a .form-hint
element, between the input and its label, so that the text is easily
accessible and falls into the top-to-bottom reading flow.
Notable changes:
* Form hint on main postcode search form, instead of placeholder.
* Form hint on alert search form, instead of placeholder.
* Form hints in reporting form (problem summary and description),
instead of placeholders.
* Removed placeholders from most login/password inputs.
* The character limit for "Inspector" report updates is no longer
displayed in the textarea placeholder.
* Form hints now `#666` grey, and better spaced when immediately
following a label element.
|
| |
|
|
| |
[fixmystreet.com] Update to use OS OpenMap Local tiles.
|
| | |
|
| |
|
|
| |
Removing this while we sort out the process.
|
| |
|
|
| |
This reverts commit 6bc39892d7075fac79c0f40b2740de095535329d.
|
| | |
|
| |\
| |
| |
| | |
'origin/issues/commercial/1087-dashboard-csv-download-teaser'
|
| | |
| |
| |
| | |
Fixes mysociety/fixmystreet-commercial#1087.
|
| | |
| |
| |
| | |
Fixes mysociety/fixmystreet-commercial#1104
|
| |/ |
|
| |
|
|
|
|
|
|
| |
Users who double click links were seeing an error when visiting the
questionnaire page. This change gives a grace period of two minutes
for revisiting the questionnaire page.
Fixes #2123.
|
| | |
|
| | |
|
| |
|
|
| |
Fixes #2185.
|
| |
|
|
| |
The code thought it was fetching the category extra, which it is not.
|
| | |
|
| |
|
|
| |
Make it customisable by cobrands.
|
| | |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| | |
Add a checkbox to show older reports, plus if we get to the end of the new
reports then instead of a Next button show a "show older" button that will
reload the current page but with older reports also loaded. Wire it all up
into the pushState code as well.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Using `$('.pagination')` everywhere in javascript was causing issues
because that returns two elements. This was especially true when
triggering events as it was triggering two events so the data was being
loaded twice. This was also resulting in resetting the page to the
initial page so clicking the back button would always return to the
first page of results.
This also sets `use_page` when clicking the back button otherwise it
also loads the initial page.
|
| | |
| |
| |
| |
| |
| | |
When moving back through pushState history from a report page to a list
of reports the list of reports wasn't being displayed because code to
redisplay it wasn't called.
|
| |/ |
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Hitherto when creating a body or ward alert on a UK site,
the MapIt area ID has been stored instead of the body ID.
This is okay for www.fixmystreet.com which for historical
reasons does have body IDs that match MapIt area IDs, but
other UK-based sites may well not. The alert lookup looks
for body ID, meaning those alerts will not work. Save the
body ID instead, plus fix some tests that were making the
same assumption.
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Styled to only be visible to staff.
|
| |/
|
|
|
|
|
|
|
|
| |
This optional flag can be used for layers whose features should
set report extra fields when selected, without the features themselves
becoming highlighted and snapping the report pin to their location.
Useful for polygonal asset layers whose features cover a wide geographic
area where the actual location clicked by the user is important, e.g.
parks.
|
| | |
|
| |
|
|
| |
Fixes mysociety/fixmystreetforcouncils#275
|
| |
|
|
|
|
|
|
|
| |
Add a button to the user edit page that sends a login token email to the
user. Helpful for user support situations where someone is having
trouble logging in. Also for situations where you have added a user and
want to get them logged in.
Fixes #2041
|
| |
|
|
| |
Anything smaller seems like it would result in a lot of false negatives.
|
| |\ |
|
| | |
| |
| |
| | |
And there are entries in the defect type dropdown.
|
| | |
| |
| |
| |
| | |
As with priorities, they depend upon the category and so must be
looked up after that has been updated.
|
| |/ |
|
| |\ |
|
| | |
| |
| |
| |
| | |
Categories could contain commas, so splitting on comma is not good enough.
Let’s escape the fields as if it’s a line in CSV. Fixes #2166.
|
| | | |
|
| |\ \ |
|
| | |/ |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Open311 specification has two values for a report's status:
- open: it has been reported.
- closed: it has been resolved.
FixMyStreet previously mapped 'closed' to 'fixed - council', but this
has been causing issues with Open311 endpoints that want to mark a FMS
report as closed but not fixed. The mySociety Open311 additions
introduce extended statuses, some of which represent a 'closed' state
e.g. duplicate, no_further_action, but there are times when a report
should simply be closed without any indication why - for example, if
open311-adapter is being used to integrate with a council system which
has a closed state not represented by the extended statuses. Marking a
report as 'closed' on a council system and displaying that as 'fixed'
on the FixMyStreet front end is not an ideal situation.
This commit changes the mapping of the Open311 'closed' status to the
'closed' FMS state when extended_statuses is enabled.
|
| |
|
|
|
|
|
| |
This allows the mobile app to explicitly detect when a body is
unresponsive and display the category_extra text.
For mysociety/fixmystreet-mobile#266
|
