| Commit message (Collapse) | Author | Age | Lines |
| |
|
|
|
|
|
| |
If an extra field on a category has a protected flag then do not
overwrite or remove it when populating categories.
|
|
|
|
|
|
|
| |
Only parses as multiple groups if cobrand is configured to handle them
to stop issues with existing groups with commas in them.
Groups are parsed as CSV so as to allow commas in group names.
|
|
|
|
|
| |
Rather than have a method in the Cobrand module use the COBRAND_FEATURES
section of the config file.
|
|
|
|
|
|
|
|
|
| |
This allows the Open311 endpoint to include ‘private’ in the ‘keywords’ field
of a service definition in order for it to be marked as non_public on FMS.
NB existing categories may be updated to become non_public, but non_public
categories will never have their non_public flag unset by PopulateServiceList.
This is so any existing Open311 categories on FMS don’t suddenly become public.
|
|
|
|
|
| |
After the change in 1cff2a0e, we need to make sure this is set
so that the relevant fields are not shown in the front end.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Without doing this, a call to e.g. $contact->set_extra_fields(@meta)
in PopulateServiceList.pm, with an unchanged meta that contains some
Unicode values, can write to the database (and cause an unneeded row
in the history table), because the column from the database is UTF-8
decoded, whilst the new text is UTF-8 encoded.
It looks like an attempt was made in filter_from_storage to fix this
issue, but the column comparison for marking a column as dirty takes
place without this being called.
|
|
|
|
|
|
|
|
| |
This adds a question to check whether a flytipping report concerns
flytipping on a road or not. Client-side, it is asked when a road is
selected and destination adjusted according to the answer; server side
it uses the answer to direct any both-tier submissions (from e.g.
non-JavaScript or phone app).
|
| |
|
|
|
|
|
|
|
| |
- Group wasn’t being set correctly by open311-populate-service-list as cobrand attribute
not being updated for each body.
- Extra metadata was being persisted to the DB every time even if nothing had changed,
causing lots of duplicate entries in contacts_history.
|
| |
|
| |
|
|
|
|
|
| |
We do need to store them, so that the sending knows which fields are being
requested, but we do not want them output to the client at all.
|
|
|
|
|
|
| |
This is part of the integration with our open311-adapter. The automated
property indicates that it's an expected value but either it's going to
be set by the server, or appear as a hidden field.
|
| |
|
|
|
|
|
| |
A new 'state' column replaces confirmed and deleted, allowing
categories to be unconfirmed, confirmed, deleted or inactive.
|
|
|
|
| |
This means that the tests can be run in parallel.
|
|
|
|
|
| |
Parse the XML in such a way other parts of the code do not have to worry
about single-value folding or the like.
|
|
|
|
| |
Command line scripts don't need a full blown app, just database.
|
|
|
|
|
| |
This override is not used anywhere, it dates from a very old long-gone
test script, and causes issues with database query planning.
|
|
|
|
|
|
|
|
|
| |
Historically, the extra field has been used in two different ways by
different cobrands, both as a list (e.g. Open311 category fields) and a
hash (e.g. the Zurich cobrand).
This commit consolidates usage, adding an API to make use of the field
easier and always returning a hash for the code to use. Fixes #1018.
|
|
|
|
|
| |
Call the necessary boilerplate in each script so you can call them
directly. Remove boilerplate from files that don't need it.
|
|
|
|
|
| |
Uses LWP::Protocol::PSGI to avoid having to spawn external processes
in order to test these end to end.
|
|
|
|
| |
Add some comments to the top of the open311 bin scripts.
|
|
|
|
| |
than one body.
|
| |
|
|
|
|
| |
Add foreign key constraint from contacts to body.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
udpate service code for contact with same category
|
| |
|
|
|