Andi Dittrich

please check the docs – sounds like your using legacy shortcodes or a weak 3rd party plugin

still active and maintained.

did you enabled the frontend integration ? see https://github.com/EnlighterJS/documentation/blob/master/wordpress/TinyMCE.md for details

this is the Enlighter support forums, nothing related to any mega menu

same file, copy the keyword regex or customize it

it’s the correct file. just add your custom regex rules and run the build script. finally replace the enlighterjs.min.js file and purge the cache

there is no public release available atm. some features are still missing

the collapse feature is available for EnlighterJS but no configurable in the community edition of Enlighter WordPress Plugin. adding the css class manually is the only possibility. feature is part of the pro/enterprise edition

The “Customizer” is just a easy way to start your customization. Advanced settings should be made editing the css directly (use the generated css as starting point and create a custom external theme as mentioned in the docs).
To identify the elements/css classes just use the DOM element inspector of firefox or chrome.

Since all of your support requests are related to css settings you will get the same answer ??

it’s not possible by css only…you have to modify the language support file and add some custom tokens.

Hi,

just create a custom theme and modify the font-family: https://github.com/EnlighterJS/EnlighterJS/blob/master/src/themes/atomic.less#L14

The base font of the customizer are the same as used by the themes: https://github.com/EnlighterJS/EnlighterJS/blob/master/src/themes/core/fonts.less

you can simply export/import the settings directly from the database (enlighter* prefix) and click “save changes” after import

the pro and enterprise editions are still in development (no eta, sry)

it’s not an Enlighter issue… the whole html is messed up (doesn’t contain whitespaces). you should talk to the plugin authors (BetterDocs) whats going on – i would assume the conversion has had an issue and needs a fix or some kind of optimization plugin is enabled (which is also weak…).

atm i assume that you’ve to repeat the migration after a fix to BetterDocs have been applied by the authors

directly via css. use the dom inspector of chrome/firefox to identify the related classes

technically possible but this would require a lot of infrastructure and quite expensive enterprise subscriptions