GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v128 Reproducible demo link https://app.grapesjs.com/studio Describe the bug After adding a Page, removing it with undo and adding back with redo, the page is not working properly. The Layer Manager does not update...
artf
Thanks for the report @rhoenerSBS
GJS Helper
This is indeed a bug in GrapesJS's undo/redo mechanism, specifically when handling page additions and removals. The behavior you've described is consistent with an incomplete restoration of the page's internal state after a 'redo' operatio...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 128 Reproducible demo link https://jsfiddle.net/sammousa/bxgsdc12/11/ Describe the bug How to reproduce the bug?Load an HTML string with a non empty <head>, using the option {asDocument: true}.Export the data via ed...
SamMousa
Thank you, but that's not really the point. I'm fully able to make a workaround, but that does not fix the bug. The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Fur...
artf
The bug is that an export via getProjectData() followed by an import via loadProjectData() should result in the same state. Yeah definitely not expected, we'll look into it. Appreciate the easily reproducible steps on the demo ๐
artf
Thanks @SamMousa detailed bug reports are always welcome. If a direction is requested, we're happy to guide you ๐โโ๏ธ
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 91VReproducible demo link https://jsfiddle.net/8tsj5vpb/Describe the bug I'm encountering an issue with GrapesJS where traits defined for a custom component are not being displayed after reloading the editor. The trai...
mohamedsalem401
@Alababdiy I was unable to reproduce the issue using the link provided. However, it seems like the issue is that GrapesJS doesn't allow adding or defining a component after it has been initialized.
mohamedsalem401
Hey @Alababdiy, I wasn't able to reproduce the issue you described in the JSFiddle.
GJS Helper
You've encountered a common issue related to how GrapesJS persists and re-identifies custom components after reloading the editor. The traits for your custom component disappear because GrapesJS is not correctly re-associating the loaded c...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://jsfiddle.net/kanaihyakumar/oedg76nt/ Describe the bug Description When selecting any component on the canvas, it highlights the bottom resize box as per the settings. However, upon cli...
kanaihyakumar
Earlier, I needed to be more clearer about the steps to reproduce the issue. Here is the refined steps to produce the issue. Steps to Reproduce the Issue:Click on the section directly.Observe the resizable options displayed.Click in an are...
kanaihyakumar
Trust me, I was lucky that I was able to find this tragic behavior of clicking different places inside section was behaving but different.
artf
I don't see it disappearing if not when you press the click but that is expected as it gets ready to be dragged
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Latest Reproducible demo link https://jsfiddle.net/condsjm1/ Describe the bug How to reproduce the bug?Change a Component's innerHTML Press CTRL + Z What is the expected behavior? To undo the content What is the current be...
artf
UndoManager tracks component state changes, not its DOM. This should work in your case element.components('Hello Planet')
leo-budgetsimple
@artf Thanks!
GJS Helper
The issue you're encountering is due to directly manipulating the component's innerHTML property, which bypasses GrapesJS's internal change tracking mechanism. GrapesJS's undo/redo manager (part of the Editor instance) only registers chang...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Edge v128Reproducible demo linkshttps://codesandbox.io/p/devbox/github/jdkcoder/cv-builderhttps://stackblitz.com/github/jdkcoder/cv-builder Describe the bug I'm using GrapesJS in Nuxt.js 3 project, the error Cannot read prop...
artf
You can skip removing the components (instance.value.Components.clear()) as you're destroying the editor anyway This shouldn't generate any error
WilliamDASILVA
@jdkcoder By commenting the reRender function we don't have the issue anymore. The lastComponent error comes from the this.get('selected') in Editor being undefined at some point. And by checking the debugger, it indeed becomes undefined w...
GJS Helper
It looks like you're encountering two distinct issues in your GrapesJS Nuxt.js 3 project. Let's break them down and provide solutions. Issue 1: Cannot read properties of undefined (reading 'lastComponent') after clearAll() Root Cause This...
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chromeReproducible demo link https://stackblitz.com/edit/vitejs-vite-4noagg?file=src%2FApp.tsxDescribe the bug I am not able to see my custom component at the first time of my react application rendering , when i try to sear...
artf
Use the plugins when you want to extend something at the GrapesJS API level
MdShadabAhamad
i also added custom style setupStyleManager but its show blank ,https://stackblitz.com/edit/vitejs-vite-4noagg?file=src%2FApp.tsx
GJS Helper
The issue you're experiencing, where your custom component block isn't visible on the first render but appears after searching, is a common timing problem related to how GrapesJS initializes its UI components, specifically the Block Manage...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? v126 Reproducible demo link https://jsfiddle.net/r5062suy/1/ Describe the bug How to reproduce the bug?Run the demo link (https://jsfiddle.net/r5062suy/1/)See that I try to update the text in the div from "Hello world!!" t...
danstarns
Try using the .getEl method on the component then setting the element directly.
mannyyang
Problem with this is that when you export the HTML, it returns the old text.
artf
@mannyyang where did you find the usage of set('content', ...? It's more like private property and you should never use it. To update inner components programmatically use component.components('test')
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? latest Reproducible demo link https://stackblitz.com/edit/grapesjs-react-custom-ui-nrqcgn?file=src%2FApp.tsx Describe the bug How to reproduce the bug?...... What is the expected behavior? ... What is the current behavior?...
danstarns
Hi, @sridharK64 thank you for your report, can you elaborate on your issue, please? As we only have: 'How to load grapesjs by default preview'Your stack blitz Could you tell us what you're trying to achieve?
artf
@sridharK64 I got what you mean but the next time try to elaborate a bit better. To trigger the preview on load, this would be enough but in your example, you're using @grapesjs/react with full custom UI, which means you have to implement...
GJS Helper
To load GrapesJS in preview mode by default, you need to initialize the editor and then execute the built-in core:preview command. This command toggles the editor's state between editing and preview, effectively hiding the editor UI and di...
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link asdasd Describe the bug I am having an issue while installing NPM plugin packages like preset-webpage, preset-newsletter , the css file is missing while installing in both when i check node mo...
artf
@SAJAD-CH please provide a reproducible live demo (eg. via stackblitz) when you open a bug issue
GJS Helper
It seems you're encountering a common issue when integrating GrapesJS plugins into modern JavaScript frameworks like Angular, where the CSS files don't appear as standalone files in nodemodules for direct linking. This is expected behavior...