Style.css of child theme doesn’t impact webpage

This topic has 5 replies, 2 voices, and was last updated 4 years, 8 months ago ago by Blade

  • Avatar: ozaando
    Blade
    Participant
    April 20, 2021 at 14:50

    Hello,

    I can’t see any change on my webpage when i make modfications in xstore-child/style.css

    The child theme was directly generate during the installation.
    The function.php contains this :
    add_action( ‘wp_enqueue_scripts’, ‘theme_enqueue_styles’ );
    function theme_enqueue_styles() {
    etheme_child_styles();
    }

    I have clear all the cache but nothing. It seems that the style.css from child theme is not called.

    Thanks for your help.

    4 Answers
    Avatar: Olga Barlow
    Olga Barlow
    Participant
    April 20, 2021 at 17:12

    Hello,

    If I check your site I see the style.css https://prnt.sc/11rgdhw And also I see that you use Cloudflare CDN. Did you clear the CDN cache after changes in child theme style.css?

    Regards

    Avatar: ozaando
    Blade
    Participant
    April 20, 2021 at 17:35

    Ok ! I see on your screenshot and effectively it works.

    But unfortunately on my side i can’t see the change (https://prnt.sc/11rh5gx). I’m working in private mode and i use liteSpeed Cache to clear all. Maybe i have to check Cloudflare CDN params ?

    Thanks for your answer.

    PS : I have checkk on Firefox and Chrome in private mode with the same result…. No change.

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    April 20, 2021 at 18:05

    Hello,

    Did you clear the browser cache? Try this extension https://chrome.google.com/webstore/detail/clear-cache/cppjkneekbjaeellbfkmgnhonkkjfpdn

    Regards

    Avatar: ozaando
    Blade
    Participant
    April 20, 2021 at 18:31

    Thanks a lot for this plugin. It does the job very well.

    Have a nice day.

    Regards

  • Viewing 5 results - 1 through 5 (of 5 total)

The issue related to '‘Style.css of child theme doesn’t impact webpage’' has been successfully resolved, and the topic is now closed for further responses

We're using our own and third-party cookies to improve your experience and our website. Keep on browsing to accept our cookie policy.