| Commit message (Collapse) | Author | Age | Lines |
|---|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This functionality allows a cobrand to replace the /contact form
with a form that creates hidden reports which are sent via Open311.
The form also allows file uploads in addition to photos.
This functionality is currently enabled for the Hounslow cobrand and
others cobrands can enable it by defining setup_general_enquiries_stash
which primarily sets up the appropriate categories and default values
for the report.
|
| | |
|
| |
|
|
| |
(This might well have been done client-side by Dropzone.)
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
If we're chugging through a list of reports, this save on a lot of
pointless statting of the upload directory which we know is there.
|
| |
|
|
|
|
|
| |
The list code was checking the photo ID given in the database existed on
disk – this shouldn't ever not be the case, and if it was, all that
would happen would be a broken image when the full photo code looks for
it (this is only for e.g. lists of reports).
|
| |
|
|
|
| |
If they are absolute already, do nothing.
Switch a couple of uses to Path::Tiny as well.
|
| |
|
|
| |
(VERSION disappears in some recent version.)
|
| |
|
|
| |
This should improve performance when there are a lot of cached photos.
|
| |
|
|
|
| |
It was possible that rotating an update photo did not remove its cached
copy.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Store image type along with hash in photo column, and use that when
outputting images / generating URLs. Make sure all public photo URL
generation goes through appropriate functions, and change temp URLs
so the filename can be output directly from the list.
|
| |
|
|
| |
Fixes #1337.
|
| |
|
|
|
| |
Remove get_photo_params, which only looked at the first photo,
make explicit when we're doing that using `.first`.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Use a separate attribute for data direct from a database row when
creating a PhotoSet, so that data will always contain one or more
photo IDs.
|
| |
|
|
| |
Command line scripts don't need a full blown app, just database.
|
| |
|
|
|
|
|
|
|
|
|
| |
The new Zurich app has to base64 encode some images into a multipart
request so that it can (ab)use Phonegap's FileTransfer plugin to send
more than one image in a single request to /report/new/mobile.
Catalyst's Request::Upload module doesn't look at the
Content-Transfer-Encoding header inside multipart requests to do
this automatically, so we perform the decoding manually when we
process the images in the PhotoSet model.
|
| |
|
|
| |
Required by Zurich for mysociety/FixMyStreet-Commercial#675
|
|
|
For Zurich, see mysociety/FixMyStreet-Commercial#664.
This commit includes a new PhotoSet class (NB: called Model:: though not
really a model), should handle binary data (e.g. old style photos in
database), fileids (40-char hash), and Catalyst::Upload objects.
|
