Bricks Version: 1.1.3
Browser: Chrome and Firefox
URL: [(https://bricks-test.auster.net/])
After updating from bricks 1.5 beta, which was running fine, to 1.5rc, a whitepage error appears. Switched DEBUG on, so you can see errors.
You can use your credentials to log into backend if possible.
Best regards,
Joachim
Is it possibly related to the other issues people have been reporting lately with the white screen showing?
Seems the usual cause is Rocket Loader in Cloudflare, and also third-party software such as BricksExtras (which an update was published which resolved it already too if using BricksExtras).
@d19dotca
Thanx for the links, I checked only a bit before update and after error of update.
Bricks 1.5 and all its current discussions about errors, blocks and divs make a lot of noise and that is never a good signal too me, thats why I do not invest in testing currently.
I had just some freetime yesterday, where started a simple update without any preperation.
Just wanted to give update to Stefan and Thomas that I also ran into issues during update.
There are too much changes in the product, so I wait for more silent water to sail again with bricks on the ocean 
UPDATE:
I updated BricksExtras BEFORE doing the update to 1.5RC, because I heard about that issue before.
But even deactivting BricksExtras does NOT solve it.
Currently there is no Chance to access front end or backend, both multiple errors.
should I restore? I made a backup before running th update?
Hello @joachim.auster
Thank you for your report. Apparently, none of the PHP errors that are displayed now would be a justification for not having the site up and running.
The errors shown are all non-bricks related, most are just light PHP warnings. If you scroll down, the site is still there:
I tried using one of the login accounts you created for our support but it says the user is permanently blocked. Do you have access? If yes, could you please check it for us? We would like to investigate this issue.
Thank you!
@luistinygod
yes, that is right. But those messages were NOT the problem.
I forgot to delete browser cache after update.
AND I had to deactivate BricksExtras 1.0.4. which causes the whitescreen.
BUT in Bricks all frames (divs, container) are now broken (no longer assigned as supposed to be)
Now you should be able to investigate in this issue via Browser Inspector.
UPDATE:
After Update from 1.4.0.2 to 1.5beta I ran the converter for sections and container.
And after that the site looked fine so far.
Now the new block with 1.5rc seems to crash everything. (I had a short look into Editor).
Update 2: 03.08.2022 15.38h
I did not see the available update for BricksExtras before in WP dashboard. Now it appeared via MainWP and after updating to 1.0.5 there is no more a whitescreen error.
@Sridhar Maybe you update your changelog of BricksExtras, which I checked in this case durint error investitation, but the only is 1.0.4 shown, so I thought, there is no update available.
Hello @joachim.auster,
Ok, nice to hear! Then I suggest you turn off WP_DEBUG_DISPLAY.
Bricks 1.5RC introduces the Block element which is the one that replaces the DIV element from Bricks 1.5-beta, and this may explain why the layout looks broken. As mentioned by Thomas in the RC release post on Facebook:
In response to the beta feedback & further testing we settled on a four layout element solution: Section, Container, Block, Div.
This offers a clear separation of layout concerns, and minimizes possible styling conflicts & overconfiguration.
The new “Div” element is now a plain div without any styles.
The new “Block” element uses flex & has a 100% width. Perfect for equal-column layouts, or anywhere else where you need to cover the entire available width.
You can adjust the layout element default styles in your Theme Styles.
The layout “Converter” (under: Bricks > Settings > General) now converts your container-based site into Section, Container, Block layouts.
For those of you who already converted your live sites using the 1.5 beta:
You might want to set the “Div” element theme styles accordingly, so the Div behaves like a Block (display: flex; width: 100%, etc.) or if it’s a small site you could manually convert Divs into Blocks via the context menu.
The update changed container from flex to block.
After manually changing this back, the wanted layout/design comes back.
I had a good concept until 1.4 with my sections and divs and defining them with my own utility-classes.
Now I have to reorganize and rethink my concept to work with Bricks 1.5 and above.
Hope there are no more of those section, container, block and div changes.
Nobody pays me the time to change this stuff manually.
In this case I have a small wish:
please put into container element doku in academy, HOW I can manually inside the builder change a div to block, to container and to section. Currently the documentation only describes that there are those different elements, but not how to switch them inside the elment itself, without replacing the element.
Switching from block to flex I had to find out by myself, but there might be a lot of users who can not help themselves, so this might be a good opportunity how this can be done
@luistinygod
I know this message from Thomas about 1.5rc in Facebook group.
Read it 2-3 times on last weekend, so I know what was changing.
BUT there is NOTHING in this message, that says, that existing containers with flex will be converted into block. And there is NO need in my opinion to do this.
It would be better to leave containers as they are.
Blocks are only a nice-to-have for containers with 100% width.
I do NOT and I will NOT use BLOCKS, because I solve this via utility-classes.
And the current merger tool chrashes this setting without any need IMHO.
I dont want Bricks to tell me that I have to use blocks, although there is no need to use them at all.
Hello @joachim.auster,
1.5 RC changed the Div element from display: flex to display: block, making the Div element an element without any default styles (CSS default for any div is display:block). In Bricks, the Container element, is still display: flex by default.
Good point. Meanwhile, you may use the context menu to convert Section/Container/Block/Div into any of the other layout elements. Please note that the Container/Block/Div can only be converted to a Section if they are not children of any other element.
