Frontend scrambled while editor looks ok

Hi, were there any notices or errors when you open the browser devtools window at the frontend? If you switch back to using Twenty Twenty-Three, do you still get the same frontend issue? If you only see the issue when your child theme is active, then it could be that the child theme is not enqueuing the parent theme styles. Good luck!

Hey there @editoraaplicacao – could you tell me a little about your reason for using Create Block Theme in the first place? What kind of changes were you making that required a child theme?

After doing so, the main header broke, but only on the browser/frontend (chrome, safari, firefox, safari on iphone).

Before things broke in your child theme, which specific actions did you take in your child theme?

(In the future, if you run into issues around using Create Block theme, its forum is here: https://www.ads-software.com/support/plugin/create-block-theme/ And for help with Twenty Twenty-Three,you can post in its forum here: https://www.ads-software.com/support/theme/twentytwentythree/)

Hi, @metamezzo ! I’m not an experienced developer, I’m just coming back to WP after many years but I didn’t see any notices or errors. Issues pane at chrome says “no issues detected so far”. I went back to twenty three, deactivated and later deleted all plugins, but it made no difference.

@zoonini so sorry for posting in the wrong place, obviously I should have looked for Create block theme forum, as the layout broke after using it. I guess I felt it would be more general because after deactivating and deleting the plugin and even re-installing 2023 theme through the dashboard, it didn’t come back to normal.

I haven’t made changes in the theme, but after reading a little, I understood it would be safer to use a child theme from the start (but maybe REALLY from the start). I was using create block theme to create the child theme (it was already installed because I was planning to add other fonts). The only actions I took, before trying to create the child theme, were creating this header and changing a little the typography, but still using the standard fonts.

I am having the exact same issue and tried the same solutions with no results.

• This reply was modified 1 year, 3 months ago by ihatethis2.

@editoraaplicacao –

I haven’t made changes in the theme, but after reading a little, I understood it would be safer to use a child theme from the start (but maybe REALLY from the start). I was using create block theme to create the child theme (it was already installed because I was planning to add other fonts). The only actions I took, before trying to create the child theme, were creating this header and changing a little the typography, but still using the standard fonts.

A child theme is only needed under certain specific circumstances, so if you don’t really need one, you can just go ahead and make changes in the Site Editor. Changes like editing blocks, modifying colours or typography, and adding new templates in the Site Editor do not require a child theme. On the other hand, changes to theme.json or adding new fonts or other files directly inside the theme folder, will be wiped out when updating the theme, so you would want a child theme to protect those from being overwritten.

As far as troubleshooting after the fact, it’s tricky to diagnose what’s going on without being able to see your site directly. I’d probably recommend just starting with a fresh Local install, as you have. Or if you can make the test site live, I’d be glad to take a look for clues.

Hi @ihatethis2 – would you mind please starting a separate thread so folks can troubleshoot with you directly? If your issue is with the Astra theme that I see on your site, please post in the Astra forum and its support community will chime in there. Thanks!