I am pretty new to brick. A week ago I started building a page in the editor. Today I wanted to move on but the editor just shows me a blank white page but when I click on “view on frontend” it shows me the text and images I added the week ago.
What’s wrong??
Hi,
Welcome to the forum!
Is the builder completely invisible (i.e., everything is white), or just the canvas?
If everything is invisible, please open your developer console and check whether any errors are displayed there. If necessary, also activate wp_debug and check your server’s error logs.
Alternatively, you should deactivate all plugins and custom code to see if that solves the problem. If so, it is a plugin conflict. By activating one plugin after another and testing again, you can find out which one is the culprit..
If only the canvas is empty, please look here:
The canvas is just white and I am not using cloudflare.
I had the same issue before, so please try these steps. You may be able to find what’s causing the problem.
1) Enable debug log (without showing errors on frontend)
Go to your hosting File Manager and open:
public/wp-config.php
Add or update the following lines just above this line:
/* That's all, stop editing! Happy publishing. */
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
This will:
- Enable debugging
- Create a debug log file
- Not display errors on the frontend or inside the editor
2) Check the debug log file
After reloading the Bricks editor once, check:
wp-content/debug.log
If the file does not exist:
- Make sure the
wp-contentfolder is writable - WordPress will automatically create
debug.logwhen an error occurs
3) What to look for in the log
Check for:
- PHP memory exhausted errors
- Fatal errors
In my case, heavy SVGs inside loop sliders caused the issue.
The frontend worked fine, but the Bricks editor showed a blank white screen because the editor needs more memory than the frontend.
4) If the issue still happens
Only after checking the debug log:
- Create a staging site
- Disable plugins one by one and test the editor
Important:
If the editor works after disabling a plugin, it does NOT mean the plugin is broken.
Disabling plugins can free memory, which allows the editor to load again.
The real issue is memory usage, not the plugin itself.
That’s not the only potential cause mentioned in the known issues (keyword GoDaddy). Without specific information (such as an error log – thanks @Binu), we can only consult the crystal ball… with poor prospects of success.
If you cannot find the cause, please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.