On a fresh clone the celeryd executable is not present. This is because
of the celery version migration to celery 4.x. As per celery's
documentation at http://docs.celeryproject.org/en/latest/whatsnew-4.0.html,
celeryd is no longer shipped in this version.
The admin panel headers are white by default, making them almost
unreadable on the light background used in the Airy theme. Make the
headers dark, like text elsewhere in the theme.
Make the batchaddmedia command look for a 'collection-slug' column, that
for each row may specify the slug of a collection that the media should
be added to. This matches the '--collection-slug' argument of the
addmedia command.
Prior to this commit, using a Unicode character in a configuration
string would result in a `UnicodeDecodeError` being raised. Supporting
Unicode characters is especially useful in user-facing configuration
strings, such as `html_title`.
Commit c0ea2bad changed the expected location column header of csv files
used by the batchaddmedia command from 'media:location' to 'location'.
This change updates the docs to match.
Add a unit test to verify that the change introduced in 07c535c no
longer resulst in a zero divide error when gps data contains no divisor.
This commit includes a test image created by Andrew Browning. Andrew
Browning dedicates this image to the public domain under the CC0 license.
This field is required to store the progress of the default
resolution of the media. So, we now store the total progress of transcoding
the video in 'transcoding_progress' and progress of transcoding the default
resolution in 'main_transcoding_progress'.
Re-arrange code to check whether a collection has been selected prior
to checking whether an item already exists in the selected collection.
This fixes a regression introduced in 0f3bf8d.
Modify the @get_media_entry_by_id decorator to return media regardless
of processing state. Separately modify all view functions that use the
@get_media_entry_by_id decorator to require that the media be in the
processed state, other than for the media_confirm_delete view. This
allows blog post drafts to be deleted without returning a 404. Further,
it adds the ability to delete unprocessed media in the future, which
would be a nice addition to the user processing panel.