Unsplash CEO asked us to stop exposing our key client side (even if it was only in the browser network and previously allowed by their API team leader). After multiple exchange, it has been negociated that: 1. Our non saas user won't be able to apply for a production key and should prefix they Unsplash application name by 'Odoo:'. Their key will remain in test mode. Indeed, Unsplash won't be able to review every Odoo application and ensure it respects the API terms and it is a real application. 2. Our saas user will query Unsplash with a dedicated enterprise key 3. The documentation should explain it all Task-1911345
16 lines
614 B
Python
16 lines
614 B
Python
# -*- coding: utf-8 -*-
|
|
# Part of Odoo. See LICENSE file for full copyright and licensing details.
|
|
{
|
|
'name': 'Unsplash Image Library',
|
|
'category': 'Web',
|
|
'summary': 'Find free high-resolution images from Unsplash',
|
|
'version': '1.1',
|
|
'description': """Explore the free high-resolution image library of Unsplash.com and find images to use in Odoo. An Unsplash search bar is added to the image library modal.""",
|
|
'depends': ['base_setup', 'web_editor'],
|
|
'data': [
|
|
'views/res_config_settings_view.xml',
|
|
'views/web_unsplash_templates.xml',
|
|
],
|
|
'auto_install': True,
|
|
}
|