GrapesJS Issues

GJSBlock

Thanks for reporting this, @JonathanRiche. Great question about stylePrefix property not overiding the gjs in most elements with the gjs-class. The recommended approach with StyleManager is to use the event-driven API. Start here: Check th...

artf

This first one is the component method, the second is the block property (used here)

vaneatka

the reason I opened this issue is that the method is not visible. maybe there is need to a new entry for the method declaration in the types? like for the setId /*Set new id on the component / setId(id: string): this;

GJSBlock

Thanks for reporting this, @vaneatka. Great question about resetId types mismatch. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the...

artf

Seems to be an issue with the color picker itself, I'll try to fix it for the next release. ps: for bug reports you don't need to create the discussion first, you can open directly the issue by following the template. This will also avoid...

GJSBlock

Thanks for reporting this, @DhanaDSP1120. Thanks for sharing your report about Undo manager - Not working properly, when we try to apply and undo the background color then made click outside the block, then the removed color will appears....

artf

Sorry but by simply trying to submit an asset the payload I see is correct, so without a reproducible demo, it looks to be an issue on your backend side (ensure to have the proper body-parser).

Aar-if

Thanks, worked using Multer, the issue was with the body parser.

GJSBlock

Thanks for reporting this, @Aar-if. The issue with Asset manager upload sending empty object to backend endpoint appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and...

micker

interesting feature

GoodPHP

interesting feature Thanks ✅

GJSBlock

Thanks for reporting this, @GoodPHP. The issue with CKEditor5 + Froala + Tinymce6 into GrapesJS appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications...

artf

Hi @malonecj I'm not sure how exactly you would expect to see and manage those components (especially when you combine templates inside conditions) but I think your current approach in isComponent is not properly correct as you have to dea...

artf

I'm closing this one as there are no issues with the core itself, if you have any other questions @malonecj let me know.

GJSBlock

Thanks for reporting this, @malonecj. Great suggestion about Custom component for text node including special characters! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the...

artf

Hi @TanyaKulikovskaya please provide a reproducible demo as from a quick check the color picker seems to work without hash

GJSBlock

Thanks for reporting this, @TanyaKulikovskaya. The issue with Color input with no hash does not update color picker appears to be a race condition or state management timing problem. This typically happens when component lifecycle events a...

artf

I guess we should avoid selecting children of already selected components in the first place.

GJSBlock

Thanks for reporting this, @RomanGlazkov. Great suggestion about JS error when moving an element with its child! While this specific feature isn't yet in the core API, there are several ways to achieve similar behavior. Using the event sys...

ronaldohoch

Same as described here, not a issue: https://github.com/artf/grapesjs/issues/4350

artf

Yeah but even in a case of a custom UI, the update is skipped if the value is not changed as it's not necessary.

bit-ocean

The code that I pasted is using the standard api, pretty much copy/paste from the documentation. And clearly the update's mechanism has changed between the versions. Before if target element had been changed, the update was triggered, and...

collins-lagat

The release says that there a breaking change. Try that and see if the problem goes away. I got the same error but haven't tried the fix yet. https://github.com/artf/grapesjs/releases/tag/v0.20.1

artf

Yes, as mentioned in the release note you have to switch from the old legacy API for custom component registration.

GJSBlock

Thanks for reporting this, @Aventrue. The issue with After Update to 0.20 from 0.19 the error Cannot assign to read only property 'defaults' of object '[object Object]' occurs appears to be a race condition or state management timing probl...