v1.2.2

Quick patch, that shows redirect URIs in a text box instead of single-line text input.

v1.2.1

Quick patch allows to enter multiple redirect URIs for created OAuth2 apps. Redirect URIs must be separated by space.

v1.2

Introducing support for Social Providers - now you can sign in to GeoKey using your Facebook, Twitter, or any other social account!

To enable social accounts, add any wanted to the installed apps, e.g.:

INSTALLED_APPS += (
    'allauth.socialaccount.providers.google',
    'allauth.socialaccount.providers.facebook',
)

If needed, configure them using the official documentation.

Finally, go to your Superuser tools, and set client IDs and secrets to enable providers.

v1.1.5

Improved serializer for categories and fields, now including "is_displayfield" - to determine whether the field is set as a display field for the category.

v1.1.4

Fixed base settings, now including "static" as a main dir for static files.

v1.1.3

Fixed installing correct version of Django alongside the GeoKey - latest version between version 1.8 and 1.10 (excluding the 1.10 alpha and future releases for now).

v1.1.2

Fixed local settings, now including main static dir when running "collectstatic" from GeoKey installed via PyPI.

v1.1.1

Fixed removing user from a user group.

v1.1

Improvements

• Each category now has ability to set an expiry field, that is used by contributions to set the date (and time) when it should be not available to the public anymore. An expiry field can always be changed or removed as a setting - none of the data is deleted.
• Public API endpoint for getting GeoKey information now includes all extensions added, even those that are installed for use by superusers only. This allows front-ends to decide what functionality can be used if it relies on some extensions.

v1.0.1

Fixed creating a user via the public API.