KDA Custom Editor Buttons

Use the standard WordPress mce_css filter in your theme, or the plugin filters kda_ceb_snippet_css / kda_ceb_highlight_css . The plugin does not store custom CSS.

Yes, with the PHP filter kda_ceb_asset_base in your theme (it works for built-in, Prism.js and Highlight.js). The earlier kda_ceb_prism_base and kda_ceb_highlightjs_base filters still work and run on top of the universal one. See the Documentation tab in the settings screen or docs/adding-a-button.en.md / .ru.md .

English is the source language. Translations are managed on translate.wordpress.org. The full user guide is in docs/adding-a-button.en.md and docs/adding-a-button.ru.md , and is also rendered inside the plugin under Settings → KDA Editor Buttons → Documentation in the admin language.

Yes. Open Settings → KDA Editor Buttons → Customization , set a folder path (must start and end with / , relative to the site root). Use the Copy select to pick Built-in, Prism.js, Highlight.js, or All libraries , then add one of these snippets to wp-config.php :

// short form: path comes from the setting above define( ‘KDA_CEB_CUSTOM_ASSETS’, true );

The tab shows a green “Custom assets: active” badge when the constant is on. The plugin creates the destination folder if it doesn’t exist, and surfaces a clear error when the web server can’t write there. The tab reminds you to re-copy after a plugin update.

Yes. Define KDA_CEB_HIGHLIGHT_ENGINE ( builtin | prism | highlightjs ) and KDA_CEB_HIGHLIGHT_THEME ( light | dark ) in wp-config.php . When set, they override the settings screen and the corresponding fields become read-only. Use this together with KDA_CEB_CUSTOM_ASSETS to pin the entire asset configuration in code:

define( ‘KDA_CEB_CUSTOM_ASSETS’, true ); define( ‘KDA_CEB_CUSTOM_PATH’, ‘/wp-content/themes/your-child/kda-ceb/’ ); define( ‘KDA_CEB_HIGHLIGHT_ENGINE’, ‘prism’ ); define( ‘KDA_CEB_HIGHLIGHT_THEME’, ‘dark’ ); `