GrapesJS Issues

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

3,464 issues found

#5442Oct 3, 2023by kishanp1024 answers
0 reactions

After applying the text color not able to set the background color

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? chrome Reproducible demo link https://jsfiddle.net/a3xgLm7c/3/ Describe the bug How to reproduce the bug?Select the text and apply the text colorSelect the same text and apply the background color What is the expected beha...

mapsmarketing

Hi @kishanp102 , I tried to reproduce the issue with the steps described but both the text and background colours are being applied (please see screenshot). <img width="318" alt="image" src="https://github.com/GrapesJS/grapesjs/assets/7955...

kishanp102

Drag and drop the text component then apply the font color and click outside again click on the text and put the background color it is not applying screencast-jsfiddle.net-2023.10.11-091942.webm

mapsmarketing

Yep, you are right @kishanp102 it doesn't apply a new background colour on it after you've already set one. It's definitely a bug.

#5441Oct 3, 2023by padcom2 answers
0 reactions

No id for elements not having styles but with `script`, which results in script not running for those elements

GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Chrome latestReproducible demo link https://github.com/padcom/grapesjs-no-id-for-element-exampleDescribe the bug When creating custom GrapesJS components, if those components have the script() (runtime behavior for component...

artf

The issue is caused by the use of jsInHtml: false and how the internal JS generator is handled. I'll try to fix it for the next release.

GJS Helper

The issue you've described is a known behavior in GrapesJS related to how component IDs are generated and optimized during HTML serialization. When a custom component has a script() function but no explicit styles applied to it, GrapesJS m...

#5432Sep 29, 2023by mahmudz1 answer
0 reactions

TailwindCSS responsive md:w-2/3 classes gets converted to md:w-2-3

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome 117.0.5938.132 Reproducible demo link https://jsfiddle.net/bx8rtseh/2/ Describe the bug How to reproduce the bug?Setup remote store managerLoad some html with tailwindCSS classes Sample What is the expected behavior...

GJS Helper

The issue you're encountering, where TailwindCSS classes like md:w-1/2 are transformed into md:w-1-2 when loaded into GrapesJS, stems from GrapesJS's internal class management and parsing logic. Root Cause GrapesJS, by default, processes a...

#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...

#5408Sep 21, 2023by quentin-bettoum3 answers
0 reactions

Main.scss is missing in 0.21.6

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Firefox 118 Reproducible demo link none Describe the bug Hello there, I have themed GrapesJS following the instructions of the doc here: https://grapesjs.com/docs/getting-started.html#theming But with 0.21.6, it's not poss...

joukhar

yeah src folder is missing

artf

Same issue as https://github.com/GrapesJS/grapesjs/issues/5392

GJS Helper

Hello! You've correctly identified a change in how GrapesJS packages its styles starting from version 0.21.x. The main.scss file, along with the entire src/styles/scss directory, is indeed no longer included in the nodemodules/grapesjs fol...

#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...

#5392Sep 17, 2023by joukhar4 answers
11 reactions

Latest version 0.21.6 doesn't come with src folder

GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 114.0.5735.199 (Official Build) (64-bit) Reproducible demo link N/A Describe the bug Latest version 0.21.6 doesn't come with src folder when installing grapesjs using npm npm install [email protected] Code of...

joukhar

it was just one file scss files are more organized and more powerful that css files but i have a backup plan

artf

@bgrand-ch I think what you're mentioning is fixable with CSS variables. I was also thinking about introducing a new small module for theming, that would allow updating the editor appearance programmatically, and under the hood, it would b...

joukhar

because of sass files to overwrite variables it is very important

#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?

Browse all topics