GrapesJS Issues

3,464 parsed GitHub issues โ€” 370 solved ยท 90 open. Search, filter and explore battle-tested answers.

545 issues found

๐Ÿ” typescript
#5425Sep 26, 2023by javadsamiee2 answers
2 reactions

When add a similar page just components ids will be changed

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? 117 Reproducible demo link https://jsfiddle.net/mirjavad/ctsx7zer/5/ Describe the bug I wanted to create a clone action for a page and noticed this bug. How to reproduce the bug?Create several pages with the same component...

artf

Good catch @javadsamiee will be fixed in the next release

GJS Helper

The issue you've encountered is a known behavior in GrapesJS when initializing multiple pages with components that share the same initial IDs and corresponding inline styles. GrapesJS correctly identifies and renames component IDs to ensur...

#5424Sep 26, 2023by bgrand-ch2 answers
1 reactions

`component:styleUpdate` event is not fired

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome 116.0.5845.187Reproducible demo link https://jsfiddle.net/yLcvbwjd/Describe the bug How to reproduce the bug?Add component:styleUpdate eventUpdate a style of a component with addStyle or setStyle What is the expected...

bgrand-ch

@artf โค๏ธ

GJS Helper

The component:styleUpdate event in GrapesJS is an editor-level event that is primarily triggered by the GrapesJS Style Manager or other internal editor mechanisms when a component's style is modified through the UI. When you directly call...

#5398Sep 19, 2023by padcom2 answers
0 reactions

Missing type declaration from exports in package.json

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chromeReproducible demo link https://github.com/padcom/grapesjs-import-errorDescribe the bug 0.21.6 changed the way things are exported and now VSCode doesn't see type declarations: It happens when TypeScript uses: which is...

padcom

PR: https://github.com/GrapesJS/grapesjs/pull/5399

GJS Helper

This is indeed a valid bug report related to how TypeScript resolves type declarations when using modern module resolution strategies, specifically moduleResolution: "bundler" (or node16/nodenext). Root Cause TheThe issue stems from the ex...

#5389Sep 16, 2023by hannydevelop3 answers
1 reactions

GrapesJS v0.21.5 Doesn't Work in NodeJS (Headless)

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? ChromeV117.0.5938.62 Reproducible demo link https://stackblitz.com/edit/node-1zsusv Describe the bug How to reproduce the bug? Run node index.js to start application. What is the expected behavior? ... What is the current...

hannydevelop

Can you check with the latest version https://github.com/GrapesJS/grapesjs/releases/tag/v0.21.6 Thank you so much @artf this works perfectly.

artf

Can you check with the latest version https://github.com/GrapesJS/grapesjs/releases/tag/v0.21.6

GJS Helper

The issue you're encountering, TypeError: grapesjs.init is not a function when running GrapesJS in a Node.js environment, stems from a fundamental misunderstanding of how GrapesJS operates and the purpose of the headless: true option. Root...

#5388Sep 16, 2023by hannydevelop4 answers
0 reactions

Running Headless Mode Returns Different HTML from Editor

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? ChromeV117.0.5938.62 Reproducible demo link https://codesandbox.io/embed/quizzical-galileo-cqldjh?fontsize=14&hidenavigation=1&theme=dark Describe the bug How to reproduce the bug?Store pages using the store managerTry to...

artf

Hi @hannydevelop you have custom component types but you didn't pass any plugins on grapesjs.init that's why the default div is applied

hannydevelop

Hi @hannydevelop you have custom component types but you didn't pass any plugins on grapesjs.init that's why the default div is applied I'm sorry that I am opening this again, adding the plugin in the normal way returns an error:

artf

@hannydevelop can you please show the code?

#5385Sep 14, 2023by padcom4 answers
0 reactions

GetDirtyCount() non deterministic after load

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Reproducible demo link https://github.com/padcom/grapesjs-bug-dirty-count-non-deterministic/blob/master/index.html Describe the bug Currently, when the user calls await load() the dirty count is zero. Only after the...

artf

Added also load options in order to clear the editor internal state post load

padcom

Thank you! Looking forward to the next release!

artf

Already available here https://github.com/GrapesJS/grapesjs/releases/tag/v0.21.6

#5379Sep 12, 2023by Sw33tgt4 answers
4 reactions

Class modifications of components are not automatically detected

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome Version 116Reproducible demo link https://jsfiddle.net/h5b0ndvL/1/Describe the bug When a component is re-rendered in the canvas, a new attribute added to the model definition get rendered, but a newly added class doe...

Sw33tgt

For the moment, as a workaround, I added this in a editor.on('component:mount', (component) => {}); function until any feedback is received. It seems to be working well. In a case where a class is removed from the definition, the removed c...

Sw33tgt

Yeah, this is intentional with classes, with your approach you won't be able to remove defined classes from the component, they will keep being added on component init. Which is fine for when a class has been forgotten on a component and w...

Sw33tgt

Something like this in the initClasses() function of Component.ts would add the new classes to the element on render. Let me know what you think :

#5378Sep 11, 2023by Sw33tgt4 answers
0 reactions

Uncaught TypeError: Cannot read properties of undefined (reading 'Canvas') while dragging a component in Layer Manager Panel

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome v116.0.5845.97 Reproducible demo link https://grapesjs.com/demo.html Describe the bug How to reproduce the bug?Select any component from the canvasOpen the Layer Manager PanelSelect the first "Section" componentUse...

Sw33tgt

I downgraded to v0.21.4 and I don't have the issue anymore, so this is only occurring on the latest version available.

padcom

Having the same issue in the simplest examples. Downgrading do .4 makes it go away. Regression?

artf

Yeah fixed already here. I'll push a new release for the end of this week.

#5377Sep 11, 2023by Akkiiiiiii4 answers
0 reactions

Error: node_modules/grapesjs/dist/index.d.ts:12551:2 - error TS1005: '?' expected. 12551 }> ? C : {}) | undefined) => (editor: Editor) => void; ~ Error: node_modules/grapesjs/dist/index.d.ts:12558:3 - error TS1005: '?' expected. 12558 }> ? C : {}) | undefined) => (editor: Editor) => void;

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? ChromeDescribe the bug After Upgrade new version 0.21.5 getting these errors . we are working with grapesjs + angular, grapesjs v 0.21.5 not available in both jsFiddle and codeSandbox right now so i'm putting a dummy link. p...

Akkiiiiiii

@artf can you please check this one

THEWebDegenerate

I use safari and chrome On Tue, Sep 12, 2023 at 10:52 PM Akshay jangid @.> wrote:@artf <https://github.com/artf> can you please check this oneโ€”Reply to this email directly, view it on GitHub<https://github.com/GrapesJS/grapesjs/issues/5377...

ghost

+1 after upgrade

#5363Sep 5, 2023by rozek4 answers
0 reactions

Cannot "sort" elements of layer panel

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Version 1.56.20 Chromium: 115.0.5790.171 (Offizieller Build) (arm64)Reproducible demo link noneDescribe the bug When I try to reorder the elements on my canvas by sorting them in the layer panel, I repeatedly get the followi...

arbisyarifudin

Im facing same issue

rozek

Sorter.ts:500 contains const cv = this.em!.Canvas, which is obviously wrong (as em is null or undefined) Unfortunately, I don't currently understand the code with all its abbreviations - but: would a change of line 499 to if (model?.set &&...

artf

Closing as duplicate of https://github.com/GrapesJS/grapesjs/issues/5355

Browse all topics