-
Notifications
You must be signed in to change notification settings - Fork 20
Troubleshooting
- Make sure that Goomento Page Builder module was enabled, in
Goomento > Configuration > General > Active
- Make sure Page Builder was
Enabled
andStore view
is matching with current storefront - Enable the Debug Mode to see what happened, in
Goomento > Configuration > Editor > Debug Mode
chooseYes
- Flush/ Clean Magento Cache
- Visual editor may crash for the first load, it's due to the timeout of loading resources from CDN, try to reload your browser, It'll go away
Goomento stored CSS files in pub/media/css
, those files responsible for each content styling, so please make sure
- Folder
pub/media/goomento/css
is writable - Try to generate the new style, go to
Goomento > Management > Global.Css > Save and Refresh
- Will refresh all globals and contents styling - Use different
CSS Print Method
inGoomento > Configuration > Editor > Style > Use Inline Css
then chooseYes
- Will use inline CSS instead - Flush/ Clean Magento Cache
If you saw some issue which related to these, you're good to go:
Uncaught Error: Script error for "ace/...
[Report Only] Refused to frame 'https://www.google.com/' because it violates the following Content Security Policy directive ...
These issues won't causing any issue to Editor
Anyone with programming knowledge can read code and debug
Go to Goomento > Configuration > Editor > Debug Mode
set to Yes
This action will throw error on the storefront
Since Goomento Page Builder serves cache for better experiment, this can causing some issues that storefront does not update regarding new changes that has just made
Go to System > Tools > Cache Management
then disable Pagebuilder Frontend
and Pagebuilder Backend
then give it a try
Goomento saved logs into 02 files
-
var/log/pagebuilder/debug.log
: It records every hit on rendering content or common usage -
var/log/pagebuilder/error.log
: Error will be written into this file, regardless configGoomento > Configuration > Editor > Debug Mode
Developer need to collect these log files to investigate the issue
Something else? Open An Issue or Contact Us