Currently themes machinery works in such way that if we rely on
default theme in our branded theme, we have to include them both into
AVAILABLE_THEMES setting, otherwise default theme assets will be
unavailable and the branded theme assets compilation will fail. On
the other hand, mentioning them both leads to theme picker being
shown - which we would like to avoid (per marketing wish).
SELECTABLE_THEMES setting was added to allow limiting the user facing
themes by configuration.
Closes-bug: #1564543
Co-Authored-By: Ivan Kolodyazhny <email address hidden>
Reviewed: https:/ /review. openstack. org/317757 /git.openstack. org/cgit/ openstack/ horizon/ commit/ ?id=958e522d402 615779609b5d660 a545198cfa8a28
Committed: https:/
Submitter: Jenkins
Branch: master
commit 958e522d4026157 79609b5d660a545 198cfa8a28
Author: Diana Whitten <email address hidden>
Date: Tue May 17 15:06:05 2016 -0700
Added SELECTABLE_THEMES setting
Currently themes machinery works in such way that if we rely on THEMES setting, otherwise default theme assets will be
default theme in our branded theme, we have to include them both into
AVAILABLE_
unavailable and the branded theme assets compilation will fail. On
the other hand, mentioning them both leads to theme picker being
shown - which we would like to avoid (per marketing wish).
SELECTABLE_ THEMES setting was added to allow limiting the user facing
themes by configuration.
Closes-bug: #1564543
Co-Authored-By: Ivan Kolodyazhny <email address hidden>
Change-Id: Ic00a9201d2d352 685b1089a37a259 87b75d6636d