Releases: themeum/kirki
Releases · themeum/kirki
4.2.0
4.1.0
- New: Settings page to allow users to clear the Kirki font cache.
- Tweak: Bundled all individual packages into the main repository, reducing the number of repositories used in development. This simplifies development by eliminating the need to work on multiple repositories.
4.0.24
control-react-colorful package
Bugfixes:
- Fix issue where uppercase color was failed to be saved
- Fix the layout issue of the swatches (removing
justify-content: space-between;
) - Fix the swatches layout issue when it contains a lot of colors.
- Allow clearing picker's color by clearing the input field value.
compatibility package
Bugfixes:
- Fix notice error: Undefined index of 'transport' as reported in #2476
- Fix code that called URL class without it's namespace
- control-repeater:
"alpha" => true
choice didn't work as reported in issue #2469 - module-css:
KIRKI_NO_OUTPUT
didn't work in the front area
module-webfonts package
Finetuning:
- Stop preconnecting to https://fonts.gstatic.com/ . It was related to issue #2478.
module-postMessage package
Bugfix:
- Fix multicolor output issue on customizer preview where the CSS property was appended with its assigned choice.
4.0.23
Bugfixes:
- control-repeater:
"alpha" => true
choice didn't work as reported in issue #2469 - module-css:
KIRKI_NO_OUTPUT
didn't work in the front area
New Filter:
- New
kirki_inline_styles_id
filter to filter the ID of the inline style tag. The default id iskirki-inline-styles
(module-css)
New Constant:
- New
KIRKI_NO_GUTENBERG_OUTPUT
constant. Since we get rid of Kirki config usage in Kirki 4, then new constant is necessary. DefineKIRKI_NO_GUTENBERG_OUTPUT
constant totrue
to disable Gutenberg support (module-editor-styles).
4.0.22
Bugfix:
- module-css & module-postmessage: Fix bug where CSS output didn't work when
'option_type' => 'option'
and'option_name'
is provided. This fixed issue 2466 and issue 2465
4.0.21
Bugfixes
- control-react-colorful: Fix warning as reported in WordPress support forum
- control-base: Fix the RTL issue as reported in WordPress support forum
- module-css: Fix issue #2448 where it didn't check for callable as the value type of
active_callback
and missing validation for callable & string. This might also fix some css output issue. - module-css: Fix issue #2449 where there was notice caused by accessing non-existing property
- module-css: Remove
:root
selector when inside gutenberg post editing. This fixes issue #2461 - module-postmessage: Handle the wrong formatted "output" argument. Suggested in issue #2462
- control-react-select: Fix issue where
'multiple' => false
didn't work (as reported in #2458) and selection limit didn't work - control-react-colorful: Fix issue where
palettes
choice didn't work as mentioned in issue #2455 - control-react-colorful: Fix issue where suffix wasn't implemented as reported in WordPress support forum
- field-multicolor: Fix issue where
palettes
didn't work in multicolor as mentioned in issue #2455 - field-multicolor: Fix issue where the CSS output class wasn't executed due to the missing of
parent_type
choice in the Generic field. This fixes issue #2460 - field-typography: Fix bug where defining an array of google font names inside google's choice didn't work as reported in issue #2459
4.0.20
Patch for warning reported in WordPress support
4.0.19
Improvement:
module-tooltips
: Adjust the tooltip positioning to handle the dynamic content height and to respect the control's section height.
Bugfix:
control-palette
(notcontrol-color-palette
): it was missingcontrol-react-colorful
: CSS output on instant preview (postMessage) didn't work whenproperty
is not set in theoutput
argument's item.