• I’m doing my first Full site Editing site using 2022. I’ve tried creating a child theme via child theme configurator. I’ve opened the child theme’s Stylesheet and tried adding CSS to customize the site, as I always do, but the changes do not show, even with the “!Important code. I’m getting frustrated since the options available using the Full Site Editing features are not adequate to control the look to the extent I’m accustomed. I’ve been writing child themes for years. Sometimes it’s very time-consuming. It would be nice to have a lot of the styling going on with the Full Site editor, but I don’t think I can do without the fine tuning of CSS. Am I missing something?

    The page I need help with: [log in to see the link]

Viewing 13 replies - 1 through 13 (of 13 total)
  • The only CSS I see in your stylesheet is this:

    
    input#name-6206a3671c081 {
        width: 200px!important;
        float: left!important;
    }
    

    I am assuming that you’re trying to reference “name” input field in your contact form. However, the ID in the CSS doesn’t match the one in the HTML source:

    
    input#name-620ac59e0d117
    
    Thread Starter keress

    (@keress)

    No, I haven’t bothered adding any more, because nothing happens when I do. That’s there, but it has no effect. I’ve tried a number of other tags, but nothing is being ‘seen.’ I’m wondering if I should even be trying, or is this just something this theme doesn’t support.

    • This reply was modified 2 years, 9 months ago by keress.

    I use the editor in the Customize section – and find it works very well.
    You can find it by adding /wp-admin/customize.phpto your site url.

    Thread Starter keress

    (@keress)

    Yes, that does work. Thank you. My vote, add this to the regular menu. I missed this ‘customizations’ for the CSS access and the favicon entry.

    Just a note, at first I thought you were saying I had to add a file named customize.php to the theme. My bad.

    @keress – Yes, my description was a bit vague (sorry) but I’m glad it works for you.
    On some of our sites, once you use the Customiser, it appears in the sidebar under “Appearance” but it doesn’t always appear there, so I have to remember the address!
    There’s talk that they will ditch the Customize panel altogether soon, but I fear that will be a bad move. I really hope they don’t, unless they provide some other way of customising with CSS.
    Andy

    Thread Starter keress

    (@keress)

    At one point I was following this Youtube, https://www.youtube.com/watch?v=1ThMIssK3IY, and saw something about a .json file I needed to make use of. I’ll have to watch it again. Not much recall there, I’m afraid, from last week. But when I added that a customization menu appeared and I felt like I had my moorings back. Or maybe it was because I was using a Bricksy theme. I prefer learning how to build sites from WordPress defaults (via child themes). Hoping this proves to be the most versatile, with faster development time. I know my CSS quite well, but it can be so labor-intensive I have trouble staying competitive. Hate to think it’s slated to become a lost art.

    Thanks for your input.

    The thing I love about customising CSS with the Customiser, is that you can (usually) see whether your code works, immediately. With child themes, you have to keep uploading and then checking in the browser – very time consuming.
    Customiser is FAR quicker.

    Older post, so not sure if anyone will respond? Can someone please clarify “Add /wp-admin/customize.php to the site URL”? Add it where?

    Thread Starter keress

    (@keress)

    After the url of your site.

    After it where? In Settings/General “WordPress Address (URL)”??

    Thread Starter keress

    (@keress)

    Sorry to be a nuisance Keress, but I Keep asking where to place this?

    Thread Starter keress

    (@keress)

    Place it in your browser, you know, where you put all your url’s when you’re calling up a site. Or, where you put your search terms when you’re searching for something.

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘Writing/Editing CSS with 2022 doesn’t seem to work’ is closed to new replies.