BUG: Page update event doesn't fire
Question
GrapesJS version
- I confirm to use the latest version of GrapesJS
What browser are you using?
chrome
Reproducible demo link
https://jsfiddle.net/1hza4t9n/
Describe the bug
How to reproduce the bug?
- init grapes
- create event handler for when a page is updated.
- Update the page
- observe the event handler not firing
What is the expected behavior? event handler for page:update fires
What is the current behavior? nothing
If is necessary to execute some code in order to reproduce the bug, paste it here below:
const editor = grapesjs.init({
container: '#gjs',
fromElement: 0,
pageManager: {
pages: [
{
id: 'index',
styles: 'body { color: red; }',
component: ''
}
]
},
height: '100%',
storageManager: { type: 0},
plugins: ['gjs-blocks-basic']
});
editor.on('page:update', (page, changes) => {
console.log('page update', page, changes)
})
Code of Conduct
- I agree to follow this project's Code of Conduct
Answers (3)
Update the page
How do you update the page?
Worth nothing, page:* events are only triggered for page models, not the content of the page, eg.
editor.Pages.getSelected().setName('My page');
any update, dragging a block, changing text color. changing text content. In the JS Fiddle, I drag a Text block, change content, and change color. I do not see an event triggering when i make these updates, so I am questioning my expectations
I am trying to understand the best way to build a custom Storage Manager. I have been using grapess for a long time, and have lots of "middleware" between grapes and my server/database. I am in the process of upgrading Grapes, so I am trying to understand the best EVENT to tap into to keep track of changes made.
Ultimately, I am learning more about the Store Manager, and I have confidence that will get me to where I need to go.
Nonetheless, I would like to understand Page Manager.... I will have to think about what you say about page model.
Ok so page:update event is not what you need as it doesn't trigger on content change (so I'm closing the issue as the event is working as expected).
Can you explain what kind of custom Storage manager you're trying to build? The Storage manager itself is already triggering on content change so I don't understand why you're trying to rebuild that functionality.
Related Questions and Answers
Continue research with similar issue discussions.
Issue #5141
BUG: component resets attribute values on updating traits ( first time only )
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Chrome Version 113.0.5672.63 Reproducible...
Issue #4435
BUG: pages Manager
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? chrome latest versionReproducible demo link...
Issue #4546
BUG: Component disappears when we select all the inner text and use backspace. Link component disappears even when we try to update the text.
GrapesJS version[X] I confirm to use the latest version of GrapesJSWhat browser are you using? Version 104.0.5112.101 (Official Build) (arm...
Issue #4448
BUG: Error on resize image.
GrapesJS version [X] I confirm to use the latest version of GrapesJS What browser are you using? Brave Browser Last version Reproducible de...
Paid Plugins That Match This Issue
Curated by issue keywords and label relevance to help you ship faster.
Loading paid plugin recommendations...
Browse Plugin Categories
Jump directly to plugin category pages on the marketplace.