Change log for Blanco 2.9.2 - by fashionlover

This topic has 4 replies, 4 voices, and was last updated 10 years, 5 months ago ago by Jack Richardson

  • Avatar: fashionlover
    fashionlover
    Participant
    July 1, 2014 at 19:10

    Hi Can you provide a change log for Blanco 2.9.2? We are currently using 2.3 and I want to manually change so that I don’t have recreate the customizations. Thanks!!

    3 Answers
    Avatar: Eva
    Eva Kemp
    Support staff
    July 1, 2014 at 19:28

    Hello,

    Sorry, but you must upgrade the theme as described in our documentation: https://www.8theme.com/demo/docs/blanco/index.html#!/upgrade , but not just part of files.
    If you don’t want to lose your changes you should create child theme and copy all modified files into there.

    Regards,
    Eva Kemp.

    Avatar: scolwell
    scolwell
    Participant
    July 2, 2014 at 01:14

    Could you please clarify for me the role of the custom.css (as shown in the tutorial video) versus using a separate style.css within a childtheme folder? Does the contents of the custom.css file (renamed from default-custom.css) get overridden at the time of an update?

    Just not sure why you would need a childtheme style.css if the custom.css file does not get overridden.

    Thanks,

    Scott

    Avatar: Jack Richardson
    Jack Richardson
    Support staff
    July 2, 2014 at 06:56

    Hello,

    Custom.css is used for custom changes in css code. It doesn’t get overridden after theme update as well as style.css of child theme. The purpose of child theme is to safely change php files of the theme. The styles can be added either to custom.css or style.css of child theme – result will be the same.

    Regards,
    Jack Richardson

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

The issue related to '‘Change log for Blanco 2.9.2’' 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.