| Commit message (Collapse) | Author | Age | Lines |
|---|
| ... | |
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | | |
Still broken on update pages, haven’t gotten to the bottom of that yet.
|
| |/ / |
|
| | |
| |
| |
| | |
Requires the OpenLayers build to include Strategy.Filter.
|
| | |
| |
| |
| |
| | |
The handler function may want to perform differing actions based
on the selected feature’s attributes.
|
| | |
| |
| |
| |
| | |
set a last_road value so we can run code to do things like remove ui
elements if the layer is no longer active
|
| | |
| |
| |
| |
| | |
Default to setting or unsetting single_body_only but if there is an
action defined in the layer then call that instead
|
| | |
| |
| |
| |
| | |
Allow clicking on a road asset to set the only body to send the report
to.
|
| | |
| |
| |
| |
| |
| | |
Add a single_body_only form value to reports that contains the name of
the only body to send the problem to. If the name doesn't match any of
the valid bodies for the report then send to all.
|
| | |
| |
| |
| |
| | |
test to check creating a new report for a category for which there are
multiple bodies
|
| | | |
|
| |/
|
|
| |
currently just displays a hard coded message in the map sidepanel
|
| |\ |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
- Removes the FixaMinGata Geocode module
- Surround bounds coordinates with quotes
- Return a different bounding box for Öckerö and other places
- Specifies specific GPS coordinates for certain OpenStreetMap relations
- Removes a comment
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| | |
For controlling if reports pulled in via Open311 should have the
position converted from Easting/Northing to lat/long.
|
| | |
| |
| |
| |
| |
| |
| | |
When pulling reports in over Open311 it's sometimes useful to be able to
accept reports with Easting/Northing rather than latitude/longitude.
This adds an option to GetServiceRequests to convert them as they
come in.
|
| |/
|
|
|
|
|
| |
Comments added offline by an inspector set the time in JavaScript using
a UTC epoch. We need to add the FMS timezone to this so it's in the
timezone the database expects for timestamps otherwise it's incorrect
when we fetch it back out
|
| |
|
|
|
|
| |
Hides the empty “Help <council> resolve your problem quicker” section of
the new report form if report metas for the selected category are all
hidden fields.
|
| |
|
|
|
|
| |
Displays the category’s email address (service code, for Open311) as
a tooltip. This makes it easier to identify the right category when
editing response templates, for example.
|
| | |
|
| | |
|
| |
|
|
|
| |
Rather than associating an asset layer with a single category use an
array so we can use a layer with multiple sub-categories
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
If the Open311 endpoint provides the external_status_code field
in servicerequestupdates.xml output, it’s stored in each comment’s
extra field as well as the problem’s extra field. This will make it
possible to trigger response templates based on this value.
|
| |
|
|
|
|
|
|
| |
The Cypress docs suggest putting machine-specific config into a
`cypress.env.json` file at the same location as `cypress.json`.
(For example, if you want to disable video recording of test sessions
on your machine, but not everyone else’s.) Since this file will be
machine-specific, we don’t want it tracked in Git.
|
| |
|
|
| |
Fixes mysociety/fixmystreet-commercial#943.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
dcc5926 simplified the HTML email layout and styling, but introduced a
bug in Mac and iOS Mail (both of which use Safari to render emails)
where the central "column" of the layout would expand beyond its 620px
maximum width if your window/screen was big enough to let it.
As far as I can tell, this is a bug in Safari – it treats empty table
cells as if they aren’t there, meaning, in our layout, they no longer
"pushed" against the sides of the central column, allowing it to expand
to the full width of the parent (the window).
Adding a non-transparent background-color to the cells forces Safari to
handle them correctly, so we set a background-color that matches the
body background, to effectively make the cells invisible, while still
giving them enough "layout" to trick Safari into rendering them.
A fun quirk here is that, with the background-color hack in place,
Safari will no longer allow the cells to occupy zero width. Even when
the screen is the same width as (or narrower than!) our central column,
Safari ensures that the spacer cells maintain at least a 1px width,
resulting in a 1px dark grey "border" down the sides of the email.
Seems Safari won’t let you have it both ways – either the cells are
there or they aren’t ;-)
To avoid this "border", we only apply the background-color when we know
the window is wider than 620px. That way, the spacer cells will collapse
to zero width on narrow screens (because of the Safari bug) and will
expand to occupy the space you’d expect on wider screens (because of our
background-color hack).
Fixes #1928 (again).
|
| |
|
|
|
|
|
|
|
|
| |
fixmystreet.com went down early Sunday morning because the database server had
been upgraded in the past year and was now set to UTC and not local time. This
confused the codebase when it encountered timestamps that could not exist, all
between 1-2am UTC.
Ideally, timestamps in the database should be 'with time zone' or be stored in
UTC, but for now let us set the time zone to the local one upon connection.
|
| |\ |
|
| | |
| |
| |
| |
| | |
Upgrade Test::PostgreSQL, which fixes a bug delaying the end
of test running, and introduces a nicer setup mechanism.
|
