| Commit message (Collapse) | Author | Age | Lines |
| |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
There is a concern that excluding district council reports from a two-tier
council's cobrand's /around page might lead to duplicate reports or reports
never being seen.
This commit adds them to the map and the sidebar and displays the destination
council in the report list item. Clicking the pin or the report link leads to
the report on FMS.com.
Reports sent to the a council other than the the active cobrand are shown as
grey pins on the map, and the receiving council's name is shown in the sidebar
list.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When viewing a report on FMS.com whose recipient council has a
FMS cobrand, turns the council name into a link to view the same report
on that council's cobranded site.
Includes methods cribbed from Hakim's Open311 refactor branch from
commit 47daa02420a4f5a4264c31efcf2a2e8611c2f23e.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When viewing on FMS.com a report made via a council cobrand, this
adds a link to the FMS for Councils page for more info.
This works by breaking out the report meta line ('Reported in the
Street lighting category by Joe Bloggs at 09:51, Tuesday 1 March 2016')
into its own template which can be overridden for the fixmystreet.com cobrand.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The message shown to the user if the report was sent to a
council other than the cobrand owner was confusing so the wording
has been clarified. Also added a call to action to view the report
on FMS.com or the cobranded FMS.
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
Instead of using BASE_URL as the base URL on council cobrands when STAGING is
true, use the UK councils default (which is cobrand name prepended to BASE_URL).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Replaced duplicate code blocks that are responsible for sending
confirmation of problem email with a function. Should make it
easier to do two-tier conditional messages later on. Also fixes a
minor bug where the wrong confirmation email would be sent for
reports from the mobile app to unresponsive councils.
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
For two-tier authorities, it is possible to send a report
from a cobrand to an authority other than the cobrand's owner.
If this is the case, then highlight it on the confirmation message
along with a link to view the problem report on the main fixmystreet.com
site.
The Hart-specific template is no longer required.
|
| |
| |
| |
| | |
For mysociety/FixMyStreet-Commercial#773.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This adds a new Cobrand::Default::categories_restriction method that can be used
to limit what categories are available when making a new report on a per-cobrand
basis.
This is used by Cobrand::Bristol to only show Open311 categories when making a
new report on fixmystreet.bristol.gov.uk but allowing all categories on FMS.com.
Also removes the Hart::hidden_categories and uses the new categories_restriction
method to achieve the same thing.
|
| |
| |
| |
| | |
The tests were running slowly because of gaze.mysociety.org's rate-limiting.
|
|\ \ |
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Use new `getLocation95` method for geocoding addresses
- Replace Coordinates::CH1903 with Coordinates::CH1903Plus
- Refactor Map::Zurich to use WMTSBase instead of duplicating code
- Slightly refactor map templates to make using custom WMTS tiles easier
- Use correct sizes for marker pins on maps
Closes mysociety/FixMyStreet-Commercial#769.
Closes mysociety/FixMyStreet-Commercial#768.
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The title in the OpenGraph header was not being properly escaped, and
the hide pins/all pins links were using single quotes which were able
to be broken out of.
Also remove the single quotes around rss_feed_uri, though this is not
a vulnerability as its contents were sanitised (postcode or co-ords).
|
| | |
|
| |
| |
| |
| |
| |
| | |
If you had no session cookie, started reporting a problem, logged in
through that process, you would then get a CSRF error as the token
had been created before the session was.
|