GrapesJS Issues

Search parsed GitHub issues, see highlighted answers, and open the original discussion when needed.

3464 issues found

#4991March 21, 2023by glapridaNo answers
0 reactions

BUG: Wrong Placeholder marker when dragging a display:grid element

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome v111Reproducible demo link https://codepen.io/glaprida/pen/eYLLXbQDescribe the bug How to reproduce the bug?Go to the codepen link https://codepen.io/glaprida/pen/eYLLXbQDrag one section to the canvasDrag another oneW...

#4972March 12, 2023by FaisalShaikhHANo answers
0 reactions

BUG: Checkbox trait not getting checked or unchecked on undo/redo actions.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Version 110.0.5481.177 (Official Build) (arm64) Reproducible demo link https://grapesjs.com/demo.html Describe the bug What is the current behavior? Checkbox trait not getting checked or unchecked on undo/redo (trait value...

#4967March 9, 2023by wyxcoder2 answers
0 reactions

BUG: new storage doesn't work

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/1vknjLst/ Describe the bug How to reproduce the bug? click run What is the expected behavior? load and save in the new storage should be called and console should display...

artf

You have to use the plugin plugins: [dbStoragePlugin, 'gjs-blocks-basic']With autosave: false you're disabling the autosave, which means the Storage.store will be triggered only if called programatically (eg. editor.store())There is no set...

wyxcoder

thank you! that works fine

#4962March 7, 2023by himansh-gjrNo answers
0 reactions

BUG: broken links in the docs

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? any Reproducible demo link no Describe the bug I believe many links of configuration objects in the docs are still to javascript files but the code has been updated to typescript <img width="1437" alt="Screenshot 2023-03-0...

#4947February 27, 2023by FaisalShaikhHA3 answers
2 reactions

BUG: Undo manager not working properly on undoing a remove action

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome - version 110.0.5481.100 (Official Build) (arm64)Reproducible demo link https://codepen.io/faisal-praella/pen/ExeNwxJDescribe the bugI have added a custom columns component with a number trait name columns used for ad...

artf

Yeah undo triggers the change:columns, in your case you could try to wrap your updateColumns changes in editor.UndoManager.skip.

artf

Ok I'm closing this one then and please open a new bug issue related to checkbox traits.

FaisalShaikhHA

Thank you @artf it works, to fix this I was toggling the trait change listener by listening to undo command before & run events but this feels cleaner. The checkbox trait not getting checked or unchecked on undo/redo (trait value is update...

#4940February 21, 2023by mani-rai1 answer
0 reactions

BUG: Destroying and re-initializing produces "Cannot read properties of undefined (reading 'get')"

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Google Chrome Version 110.0.5481.100 (Official Build) (64-bit) Reproducible demo link https://stackblitz.com/edit/js-3urscf?file=index.html,index.js Describe the bug How to reproduce the bug?Initialize the editorDestroy th...

artf

Yeah, the editor instance is not expected to be destroyed immediately due to some deferred async functions (eg. for the StorageManager) but that can be fixed. For now you can overcome the issue by doing something like this:

#4937February 20, 2023by besart-k1 answer
1 reactions

BUG: block:custom is not working on React

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 110.0.5481.100 (Official Build) (arm64)Reproducible demo link NoneDescribe the bug I am trying to replicate in React the customizing the Block Manager like in this example Vue block manager, but the "block:cus...

artf

@besart-k you have to provide a reproducible demo as if it works with the current Vue demo example it shouldn't be different in React. Maybe you're using an old version of grapesjs or doing something wrong in your React app, so in this cas...

#4929February 14, 2023by handhikadj3 answers
0 reactions

BUG: a tag inside button is removed

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome LatestReproducible demo link https://codesandbox.io/s/interesting-bell-xntbtrDescribe the bug How to reproduce the bug?go to the codesandboxdrag and drop Custom Code block.put this code inside the Custom Code editor a...

artf

This happens because of the button implementation in the forms plugin, which allows only textnodes as children. If you remove the form plugin you'll be able to see the <a> element (if you prefer you can also extend the button component wit...

handhikadj

so what is the code of "normal" implementation of the button? btw, may I know why do you make the button to behave like that on the forms plugin?

artf

If I recall properly the main reason there was a problem with inline text editing with button elements, so that approach was the easiest way to fix a common issue. I guess the "normal" implementation would be to skip/overwrite the init met...

#4922February 11, 2023by clonefunnels1 answer
0 reactions

BUG: Using !important code provided here breaks background image and gradient.

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox Reproducible demo link https://jsfiddle.net/jLgb0mv3/1/ Describe the bug How to reproduce the bug?...Put this code in the editor: editor.on('styleable:change', (model, property) => { const value = model.getStyle()[...

artf

I only see the issue with composite/stack style manager properties and that is because not every style manager property is part of the styles so in your code you would only need to check if the value of the style actually exists, eg. if (v...