BUG: Autosave not working on style manager when classes are disabled

Question

Version: 0.16.18 Are you able to reproduce the bug from the demo? [x ] Yes: https://jsfiddle.net/ju1a0onx/ What is the expected behavior? Autosave should always call the "store" command after a style change, even when the classes are disabled What is the current behavior? When you disable all classes on an element (Or set them all to private - not shown in this sample) and make a style change, the Autosave doesn't kick in, and your changes aren't saved. Are you able to attach screenshots, scree...

artf · Accepted Answer

Thanks for the report, there is a bug with the editor.load method, which could be currently patched in this way Actually, if you have used editor.load() only because it doesn't load on start, that because you have to define your custom storage in a plugin, in that way the autoload (true by default) will work correctly (without any temporary patch on your side)

Joshmamroud · Answer

@Davidvlv I'm experiencing the same issue. I believe it's a combination of the avoidInlineStyles: 1 in the config and no class being selected. It seems to work as expected with avoidInlineStyles: 0

Davidvlv · Answer

I've tried it out, and that setting does stop it from not saving when it should, but it introduces some other issues on our end with how we're using the output later on. We turned on avoidInlineStyles to avoid these issues.

Autosave not working on style manager when classes are disabled

Question

Answers (3)

Related Questions and Answers

linear-gradient CSS does weird things to background-image

BUG: Layer manager appendTo is duplicating the layers every time grapesjs is init

Textable not working with extended text component

Problem with copy and paste a node

Paid Plugins That Match This Issue

Browse Plugin Categories