I am trying to extend the preview command. I expected the code below to run the normal preview command along with console output, but only console statement runs. How can I preserve the original preview code? The below works for me until someone can enlighten where my thought process went wrong.
artf
If you specify a new run() function the command will run only the new one, otherwise, it wouldn't be possible to fully change a command (here more about extending commands)
ronaldohoch
Hello Artf, oddly enough, i need the same thing he does. So, the best way to do is doing the same way he does? Running the original preview command inside the extended preview?
ronaldohoch
Well... Other thing i'm doing is extending the preview by running the command on event.:
Hi @artf I would like to know why layer's name span has a contenteditable attribute. There is no mechanism implemented on grapesJs to really change the layer name after refreshing the page if I'm not wrong. It can be a little bit confusing to the user. Thanks.
artf
If you double click on the layer name you can actually change its name :)
Franci5co5aoco
@artf , sorry I think I was misunderstood. I meant you can change the name but when you refresh the page the changes are not been saved... and I think that there isn't a mechanism implemented to achieve it. When the user modifies the layer...
artf
No, the mechanism to store/load custom layer names is there, the only issue is that the change is not triggering the store... indeed, if you try to move some component right after the change, you will see them after page refresh. Anyway, t...
WARNING READ and FOLLOW next 3 steps, then REMOVE them before posting the issueFollow CONTRIBUTING Guidelines https://github.com/artf/grapesjs/blob/master/CONTRIBUTING.mdDo a quick SEARCH first, to see if someone else didn't open the same issueAll relative statements/questions have to be filled/answered, otherwise, th...
NagarRahul
@artf when I drag button it is expend. I want to fix it. It's should not expend when drag new button. It will shoe scroll after overflow.
artf
it just depends on the styling of the component (eg. using display inline-block for that button might fix the that)
GJSBlock
Thanks for reporting this, @NagarRahul. Great suggestion about FEAT: @How to fix container size when we are drag element inside the container,Container will be expended according to the child dragged element. How we can auto size child ele...
I am trying to use the set function to change the content of a component, but actually the result is an empty component with nothing inside. This is an example with the code summarized Version used: 0.16.44 What is the expected behavior? The code executed should result in a component with text "foo" inside. What is th...
artf
you shouldn't use the content property, use selectedComponent.components(str)
GJSBlock
Thanks for reporting this, @nairdapuiu. Great question about Set content function empties the component content. The recommended approach with Components is to use the event-driven API. Start here: Check the GrapesJS documentation for your...
grapesjs - 0.16.105 When I click in one element(form - this element have disable cloning), next second element(column). First element clone in to second element and lost all styles. Can You help me? https://user-images.githubusercontent.com/44744754/112153667-cb534080-8be3-11eb-90ef-dbccc866fde2.mp4
artf
Hi, at first, you need to update your grapesjs version, it's too much old, and I can't help you without a reproducible demo of the issue
qweiop801
I update grapesjs to 0.16.45 and problem still exist
GJSBlock
Thanks for reporting this, @qweiop801. Great question about double click problem. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific module Look for the...
When I click in one element, next second element first element clone to second element and lost all styles. Can You help me?
artf
Hi @qweiop801 please follow the issue template by following all the steps
GJSBlock
Thanks for reporting this, @qweiop801. The issue with double click copy bug. appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modifications overlap, creating...
What are you trying to add to GrapesJS? Un-minified versions for each release Describe your feature request detailed I am working with some more complex methods utilizing the Component Manager. The last release that had an un-minified 'debug' version was 0.15.xx. Can you please release the unminified as well as the mi...
artf
Hi @mitcht the current bundle includes the minified file but also its source map, so you can easily view the original code from dev tools (more about it here), therefore there is no reason to include also the unminified version if you need...
GJSBlock
Thanks for reporting this, @mitcht. The issue with FEAT: Unminified version in the latest release appears to be a race condition or state management timing problem. This typically happens when component lifecycle events and DOM modificatio...
Hi @artf , When I have several elements nested in the Layers panel then some elements names are truncated because the Layer panel's width is not big enough, I know that custom resizable panel can be a solution but adding a title attribute would be enough for the majority of the use cases. A tooltip (title) would be he...
artf
Yeah, why not... would you like to create a PR? :)
Franci5co5aoco
@artf of course, thanks! I'm going to create the PR...
GJSBlock
Thanks for reporting this, @Franci5co5aoco. Great question about FEAT: Add a title attribute to the Layers panel elements. The recommended approach with GrapesJS is to use the event-driven API. Start here: Check the GrapesJS documentation...
Version: 0.16.44 What is the expected behavior? I expect to have 2 separate instances of grape in one single page and being able to utilize the asset manager properly Describe the bug detailed I have initialized 2 instances of grape in a page with the config below what happens is that in the second instance of the edi...
ThetripGr
OK so after a little bit more investigating, the real issue was due to how I was initiating the editors so my bad. I wasn't making sure the instances were truly separate and I was overwritting the first instance even though it appeared as...
GJSBlock
Thanks for reporting this, @ThetripGr. The issue with having two instances of grape present makes the asset manager of the first "stop" working appears to be a race condition or state management timing problem. This typically happens when...
thanks for your work, this is a good project, this may be is not a bug I trying to make the colorpicker in style manager scroll with the input box. for example: the (color,background) input boxopen the colorpickerscroll the style manager the input box moved, but the colorpicker stay at the old position I try this on t...
artf
The color picker is placed absolutely. Unless you'll find a way to update it on the scroll of the style manager, I don't see alternatives.
GJSBlock
Thanks for reporting this, @jcsofts. Great question about The colorpicker scroll off the input box. The recommended approach with StyleManager is to use the event-driven API. Start here: Check the GrapesJS documentation for your specific m...