Child theme - by Artūras Jakubauskas - on WordPress WooCommerce support

This topic has 7 replies, 3 voices, and was last updated 5 years ago ago by Artūras Jakubauskas

  • Avatar: Arturas_Jakubauskas
    Artūras Jakubauskas
    Participant
    December 3, 2020 at 13:26

    Why enabling child theme breaks whole website stylesheet?

    6 Answers
    Avatar: Rose Tyler
    Rose Tyler
    Support staff
    December 3, 2020 at 13:42

    Hello,

    After the theme update, go to Theme Options > click on Publish.

    When you switching between child theme and parent theme your widgets and theme options could be different because the child theme does not inherit all theme options of the parent theme and the parent theme does not inherit theme options of the child theme.
    So, before switching from the correct theme (where everything is correct) you need to export theme options (Theme Options > Export/Import) and then import them after switching. Widgets should be moved to correct areas at Appearance > Widgets.

    Regards

    Avatar: Arturas_Jakubauskas
    Artūras Jakubauskas
    Participant
    December 3, 2020 at 13:45

    a, ok, but now i have been switched back. Deleted cache in chrome, but doesnt change anything to me.

    Avatar: Arturas_Jakubauskas
    Artūras Jakubauskas
    Participant
    December 3, 2020 at 13:48

    Ok doing this now. But now some of the options working, some not. Very strange..

    Avatar: Arturas_Jakubauskas
    Artūras Jakubauskas
    Participant
    December 3, 2020 at 13:50

    On mozzila header top options doesnt moved. Chrome still showing broken stylesheet… So is it better to work with firefox? Chrome after deleting cache did nothint…

    Avatar: Olga Barlow
    Olga Barlow
    Participant
    December 3, 2020 at 14:08
    Avatar: Arturas_Jakubauskas
    Artūras Jakubauskas
    Participant
    December 3, 2020 at 14:14

    doesnt helped https://prnt.sc/vv1tly

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

The issue related to '‘Child theme’' 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.