[Question] Is there any way to get the parser errors other than from console log
Question
I am using the latest GrapesJS (v0.16.27). As per the fix for the issue, (#2029) the exception has been caught and logged into the console.
Is there any way where we can get to know about the errors other than from console log?
Something similar to asset:upload:error, if we have parse:error, it would be helpful to handle the errors in a custom way. If we already have a way to handle this, please let me know.
Answers (1)
Usually, the error doesn't come from the parser but from the creation of the DOM (eg. the editor creates the element by using setAttribute). You can catch the editor's errors by listening to the log event
editor.on('log:error', (err) => console.log('error from the editor', err))
Here, for example, you can put your logic (eg. by reading the error) and show the appropriate response
Related Questions and Answers
Continue research with similar issue discussions.
Issue #1167
[QUESTION] export options
Hi @artf, Are there any other export options than HTML/CSS ? I'm thinking of a way to directly load the configuration from a remote server...
Issue #1066
[QUESTION] Get content with inline CSS
I've been looking for some explanation and I found that some email clients blocks CSS... I would like to know if is there some way to get e...
Issue #2364
[Question] How to add toolbar functionality to the layers panel.
I am trying to add the toolbar to the layers panel and I am not sure how to go about this. Is there any way to accomplish this? toolbar Whe...
Issue #2805
[QUESTION] "Changes you made may not be saved." alert popup is displayed
Hey guys I have some problem related to alert which displayed when I tried log out of page. Actually I do not know bug is it or something e...
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.