| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| | |
This brings in my new format_for_country function which allows
for nicer display of phone numbers to people.
|
| |/
|
|
| |
Though when running tests, decrease it for speed.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The 'updates are not sent to the council' message was incorrectly being
shown on reports where updates would in fact be sent. This was affecting
non-Bromley/Stevenage reports on fms.com and all cobrands using Open311.
This commit moves the logic out of the template and adds the
Problem->updates_sent_to_body method which inspects the receiving body's
Open311 configuration to determine whether updates will be sent.
The duplication of the Lewisham/Oxfordshire logic between Problem.pm and
send-comments isn't ideal but hopefully there won't be any new Open311
bodies that only send and don't receive updates. If there are we'll have
to look at refactoring that list.
|
| |/
|
|
|
| |
When more than one photo has been uploaded, allow each one to
be published/not independently.
|
| |
|
|
| |
And use the existing ones more.
|
| | |
|
| | |
|
| |
|
|
|
| |
Include actual times, not just human-readable ones, and
make sure state is translated correctly.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Create a comment on a problem when the admin is used to change the state
of the problem. If only the state is changed then create a comment with
blank text. If the category and state are changing then include details
of the category change in the comment.
Not all the state changes are displayed at the template level by
default.
Fixes #1846
|
| | |
|
| |
|
|
|
| |
We have no way of knowing whether a +1 geographic number is fixed
line or mobile, so accept them all as potentially mobile.
|
| |
|
|
|
|
| |
This expands the 'change email' functionality to work with phone
number also, allow addition of missing details, and verifying of
unverified details.
|
| | |
|
| |
|
|
|
|
|
| |
This includes search/flagging users, editing user on the report
and update edit pages, and user adding/editing itself.
Add some more tests for user adding/editing.
|
| |
|
|
|
|
| |
This includes stopping some emails being sent (moderation, alert,
questionnaire), dealing with Open311/email report sending, and
tokenised_url.
|
| |
|
|
|
| |
These are so we can state whether a user's email address or phone number
have been verified by confirmation email/text.
|
| |
|
|
|
|
|
| |
If we've stored the nearest address then display that at the top of the
inspector panel.
Fixes mysociety/fixmystreetforcouncils#234
|
| |
|
|
|
| |
For temp URLs there was not already a query string, and
so "?" needs to be used rather than "&" when appending.
|
| | |
|
| |
|
|
|
|
|
| |
Adds a Ward column to the council dashboard CSV export with the name of
the ward.
Fixes mysociety/fixmystreetforcouncils#220
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
State display names are now got from the database wherever they are
displayed, including admin dropdowns, list filters, and update meta
statements. This also covers the open/closed/fixed 'groups'.
This also fixes a bug whereby if e.g. an update has problem_state
investigating, the next update has no problem_state, and the last
update has investigating again, it was previously showing a state
change to investigating on that third update.
|
| | |
| |
| |
| |
| | |
We keep the internal states hardcoded, plus the core open (confirmed)
and closed ones, but the remainder are moved to the database.
|
| | | |
|
| |/
|
|
| |
If set to 1, this restricts all pages on the site to logged-in users.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
Create a comment entry for all updates to reports regardless of whether
there is any text part. Also adds an entry to extra if a defect was
raised and includes that in the update status line.
Fixes mysociety/fixmystreetforcouncils#201
|
| |
|
|
|
|
|
| |
- Also provides an editor for the extra Open311 fields on contacts.
- Adds .btn--small class for small buttons
Fixes #1743.
|
| |
|
|
|
|
| |
This avoids the need to search the whole table to find a report's
duplicates. And is easier than constructing an index or upgrading
PostgreSQL.
|
| | |
|
| |
|
|
|
|
| |
Calling the function 'translate' causes gettext-extract to add the
string to the .po file. Also, we no longer need an admin 'updated'
message as the main form has its own success message.
|
| |
|
|
|
|
| |
As category is used both for display and as a link between Problem and
Contact tables, add `category_display` for use whenever a category is
displayed.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
A recent change doubled the size of the pin images, which meant the static
maps included in report emails had the pin in the wrong place because the
compositing code made assumptions about the pin size which were wrong. This
commit ensures the pin image is of a known size before compositing, putting
the pins back in the right place.
|
| | |
|
| |
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Historically in UK cobrands, bodies have had IDs the same as the MapIt
area ID they cover. This can be confusing (if you are setting up a dev
environment, say) and should not be necessary. This commit removes the
requirement entirely, by switching any ID checks to either the name of
the body, or the actual area it covers.
One note: the body name in the test has to match so that we do not get
two bodies both covering 2237 created. This will not be necessary when
the tests are compartmentalized in the next commit.
|
| |
|
|
| |
Add hook so that cobrands can change pin hover title.
|
| | |
|
