Header menu error

Sub-menu behavior is the responsibility of your theme. I recommend seeking help through your theme’s dedicated support channel where its support staff there are in the best position to help you.

Hi, I ran into one menu issue today. I am customizing a child theme, in the pages I edit, I have the header (including the menu), but once I click on view page or view site, the header disappeared. it’s so wired, what could it be?

Also, in the advanced settings for adding block css, sometimes there is a wp theme default code there already, e.g. is-style-animated, should I put a comma or a semicolon there if I want to add more css code after this one, since you can’t use enter to start a new line, but anything I put after it, it seems the default code loses function instantly. I found nothing online talking about this. Also, in the appearance – customize – additional CSS, should we use period in front of a class and sharp in front of a id etc. just as how we code normally? Does the hierarchy work the same, like in this? .container p img a:hover

Last, how do you add css animation @keyframe to a block in the advanced or additional CSS section, because it will be code out of the flow as in the CSS sheet.

Oh there’s something else, when I do customize – pages – home, I couldn’t even select any block in the body part, the only parts respond to cursor click are the footer and header part, is this normal?

I am new to wordpress, sorry if my questions look silly to you.

Thank you very much!

Your header appears on pages in the site editor but not on the front end (the version visitors see)? That’s strange. There must be an issue with the page template? Does it also happen if you switched from your child theme to its parent theme? If so, I still recommend seeking help through your theme’s support channel. If the problem is solely with your child theme, review your template code, compared with the same from the parent theme.

The Additional CSS content ends up being placed within an inline <style> block on any front end page, so you’d format Additional CSS exactly like you’d format CSS in an inline <style> block. Enter key for a new line should behave normally as it would in any text editor as long as the text edit cursor is active. If for some reason using the Enter key invokes some kind of undesired action, try using Shift+Enter to get a new line.

If you’re editing an existing rule to add a new selector group, then yes, use commas to demarcate different selector groups. Similarly, dots and hashes denote classes and IDs just as they do in normal CSS. Thus @keyframe ought to work just as it does in normal CSS, in the end there’s is no difference between Additional CSS content and inline CSS you might manually add to a template.

You should be able to edit any element appearing in the site editor, but depending on where you are in the editor, altering body content may be inadvisable even if it’s feasible. For example, the body content of the archive template. This is supposed to be auto-filled based on your latest blog posts. It appears blog posts can be edited here, though I’ve never done so myself, I’ve always used the dedicated post editor.

If you’re unable to alter body content in the site editor, it might be a “feature” of your parent theme? Perhaps it’s auto-filled with content from other sources? Maybe you’re supposed to go to the root source instead of using the site editor. Similar to how we can edit pages through the page editor instead of the site editor.