| Commit message (Collapse) | Author | Age | Lines |
... | |
| |
| |
| |
| |
| | |
To allow us to infer additional stats changes requirements such
as in mysociety/FixMyStreet-Commercial#459 better in future.
|
| |
| |
| |
| | |
to allow a wider range of action logging.
|
| |
| |
| |
| |
| | |
This was causing previous test failures when config != Zurich, due
to expected logic not getting triggered.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
First test that this page is only available to superuser.
Then test that the moderated and fixed stats are doing something that
is (hopefully) the spec in mysociety/FixMyStreet-Commercial#459
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
see mysociety/FixMyStreet-Commercial#459 the new requirement is for
"Innerhalb von fübeitstagen abgeschlossen" - a report is dealt with
(abgeschlossen) as soon as the public state is Beantwortet (db: fixed -
council or closed) or Unsichtbar (en: Invisible, db: hidden).
Have added this as {closed_overdue} but have retained the logic for
{subdiv_overdue} logged in the %extra hash for now, in case it is
needed.
Note: as per Matthew "as with confirmed/in progress this should be 6 -
it's five days from moderation so is most simply just done as being six
since creation"
|
| | |
|
| |
| |
| |
| |
| |
| | |
- is set to 0 on state change within time-limit
- is set to 1 on state change after time-limit
- only marks overdue on first time
|
| |
| |
| |
| |
| |
| |
| | |
mysociety/FixMyStreet-Commercial#459 - we move "confirmed" to being
a moderated-but-not-complete state, and run the check for ->overdue
also on changing status from 'unconfirmed' (but only the first time,
so only if $extra->{moderated_overdue} isn't already set.
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
see mysociety/FixMyStreet-Commercial#459 - "a report is moderated as
soon as its state has changed for the first time from Erfasst (en:
Submitted / db: unconfirmed) to any other state."
Thus we move 'confirmed' problems from the 1-day moderation SLA, to
a 5-day one, with $include_parent unset (e.g. as with 'planned' it
is with the DM, so doesn't need to be sent to the parent body also.)
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| | |
Omitted the credits and links to further information.
|
| | |
|
| |
| |
| |
| |
| | |
Use the internal hash URL of the photo so that it can still be seen in
the admin interface.
|
| | |
|
|/
|
|
|
|
| |
Reduce magic numbers by switching fixed width to a margin elsewhere.
This has the added bonus of making the 'middle-width' .content
have a pleasing right margin.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a body has been marked as deleted (currently only exposed in the
Zurich cobrand's admin) the categories for that body should not be
available on the report_new form.
Prior to this change there was an error running the
'zurich-overdue-alert' script, because it wasn't expecting the
'bodies_str' field to have any entries in the format 'x|y,z', this
prevents this problem from happening in the future (though it doesn't
fix any existing entries with this issue).
|
|
|
|
|
|
|
|
|
| |
If the ALLOWED_COBRANDS configuration variable only contains one entry
(and also work if it's a string rather than a list), always use that
cobrand, no matter what the hostname is.
The example Vagrantfile no longer needs the configuration changes at
all.
|
| |
|
|
|
|
| |
Use a relative URL in the CSS in case it's proxied.
|
|
|
|
| |
Graphic and css from FMT. Fixes #579.
|
| |
|
| |
|
|\ |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
| |
This fixes the map so the centre is offset to the right to account for
the overlayed sidebar on the left.
|
|
|
|
|
| |
The staging banner didn't fit, and .wrapper{position:relative} was breaking things :-(
Easier to keep it simple, drop the header and just set the title in the Cobrand module instead.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
splits emails on comma
WIP
|
|\ \
| | |
| | |
| | | |
https://github.com/andylolz/fixmystreet into andylolz-389-report-search-ref
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
Fixes #389
|
| |/
|/| |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The position:fixed bottom navigation does not stay fixed in Chrome, it
appears to scroll with the content (though the link targets remain and
swapping tabs fixes the display, so I'm pretty sure it's a bug). The bug
is logged in Chrome's tracker at:
https://code.google.com/p/chromium/issues/detail?id=311513
To work around it, the z-index has been removed from .container; this
would mean that the sidebar notes all disappeared under the map, so they
have been jigged to appear on top of the main content div instead.
|
| | |
|