| Commit message (Collapse) | Author | Age | Lines |
|
|
|
|
|
| |
Since we require the user to enter their full name Buckinghamshire have
asked us to change the text to "Full name" to make it clearer that the
full name is required to complete the form.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this change, you can safely add the TfL body to other councils
(namely the ones surrounding London that include TfL bus stops);
clicking in those councils on other cobrands will have no change, as the
TfL body will be fully ignored on a non-London council, but on the TfL
cobrand it will allow it for e.g. the selection of bus stops outside
London.
It removes the body rather than just all its categories to prevent a "We
do not have details of the other body covering this area" message
appearing.
|
| |
|
|
|
|
|
| |
Because trees now allow you to click on a highway as well as a tree it's
simpler to switch the tests to a different type
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
I want to change the `updateUSRNField` method so that it can accept an
array of objects in the `usrn` key, but before doing that I want to add
a test to ensure the existing behaviour is tested, to ensure I'm not
breaking anything.
|
|
|
|
|
|
| |
As there are two category drop-downs in this situation (one in the
hidden reporting form, one in the inspect form), the correct entry
needs to be specified.
|
|
|
|
|
|
|
| |
If the duplicates.js file is loaded, then its mechanisms come into play,
and it fetches duplicates and hides the reporting form if there are any.
So we only want this to happen in the same situations as it being loaded
elsewhere, on a relevant cobrand and not just after signing in.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
Configured to allow:
- updates only from original reporter
- close updates from fetch reports
- use OSM geocoder
|
|
|
|
|
| |
The question was being asked for even when it should not, because
the error key had been changed to start with an 'x' in 120b57d1.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This should make it easier to add browser tests as you won't have to
get the click precisely on the right pixel in order to have it match
the correct area.
|
|
|
|
|
| |
Due to refactoring in 12d2346, this was loading prior
to the main asset code and thus not activating.
|
|
|
|
|
|
|
| |
This makes it clearer that all details for a report made in a private
category will not be shown publicly.
Fixes mysociety/fixmystreet-commercial#1405
|
|
|
|
|
| |
Allow users on narrow screens to filter the pins displayed on the
map page, using the regular `.report-list-filters`.
|
|\ \ |
|
| | | |
|
| |/
|/| |
|
| | |
|
|/
|
|
|
|
|
|
|
| |
There is a small bug where if you go to a two-tier location, pick a
category that is sent to one of the two ("These will be sent to" text
updates to only show that one), then click elsewhere on the map, the
"These will be sent to" text resets to show both bodies. This happens
because fixmystreet.bodies is reset after the text has been correctly
set by the category change() setup (called on pin move also).
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add the hosts config option, from
https://github.com/cypress-io/cypress/issues/1488#issuecomment-396435553
to the cypress config so we can access *.locahost. Then use those in the
cobrand tests, as well as allowing them as cobrands by default in the
FixMyStreet server setup.
NB: need to set fixmystreet.localhost as the FixMyStreet BASE_URL
otherwise form submissions can go to localhost and then you get a
cypress cross origin security error.
|
| |
|
|
|
|
|
|
| |
A few bits weren't being correctly hidden, as the code didn't account
for someone going directly from a report page to a reporting page via
the Report another problem here button.
|
| |
|
|
|
|
|
|
| |
Fixes #2242.
Co-authored-by: Matthew Somerville <matthew@mysociety.org>
|
|
|
|
| |
Dropped Kerbs and Skips in a Licensing group.
|
| |
|
|
|
|
|
|
| |
This is so front-end tests will not try and send email, or
call Gaze. Various co-ordinates have to be updated because
the default zoom level of the map has now changed.
|
|
|
|
|
|
|
|
|
| |
With the recent login changes, the user form was being hidden after
logging in while leaving an update, meaning you had to click "Continue"
to see the thing it was asking you to check. Refactor the update flow
slightly in this area to be more like reporting, showing the relevant
bit of the user form immediately (and thus also not having it within a
hidden section).
|
| |
|
|
|
|
|
|
| |
When a report is pulled in via ajax, it means there are then two sets of
login flow buttons on the page, and the JS setup only attaches to the
first of these.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves the email input from `user_loggedout.html` closer to the
password inputs in `user_loggedout_{by_email,password}.html`, because
we want to emphasise the connection between your login email/username
and your password, and, now that only one "Yes I have an account / No
I do not have an account" fieldset is displayed at a time, there was
no reason to ask for the email/username up front.
This, however, now means the form includes two username inputs, so:
* `Report/New.pm` and `Report/Update.pm` now pick the first non-empty
username param and use that.
* `user_loggedout_email.html` now expects a `name` parameter, so that
we can give the two username inputs unique ids in the markup.
Also:
* The "optional" phone and email inputs in user_loggedout_by_email.html
are printed *after* the main username input if SMS login is enabled
(since one or other of them is unhidden by javascript, based on
whether you entered a phone number or and email address into the
"username" input, and it would look weird to have an input become
unhidden *above* the input you’re currently editing).
|
|
|
|
| |
Co-authored-by: Zarino Zappia <zarino@mysociety.org>
|
|
|
|
|
|
|
| |
If set then when the user creates a new body report it will prefill the
report title and description with some basic text.
For mysociety/freshdesk#23
|
| |
|
|
|
|
|
| |
Previously if there was a mix of groups and top-level categories
they weren’t sorted together.
|
| |
|
|
|
|
| |
Check selecting a category and selecting a sub category
|
|
|
|
|
|
| |
Add options to set the cobrand plus related options for co-ordinates,
name and area id to the browser test command. Set BASE_URL to same as
test server, as that is used in e.g. list link output.
|
|
|
|
|
| |
rather than hardcoding a postcode pull it from ENV to make testing a bit
more flexible for use in cobrand testing
|
|\ |
|
| |
| |
| |
| |
| |
| | |
replace_query_parameter() was stringifying select multiples, meaning
they were incorrectly recorded by the pushState and thus breaking on
navigation.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Including testing the filters, viewing a report, and pushState.
Plus a mock MapIt handler for returning a GeoJSON outline, to make the
page load. The BASE_URL is also set to the same as the test server, as
that is used in list link output.
|