Title: Theme update without loosing child theme
Last modified: January 28, 2022

---

# Theme update without loosing child theme

 *  [bdchika](https://wordpress.org/support/users/bdchika/)
 * (@bdchika)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/)
 * Hello,
 * I have a notice that there is an update to the Olsen Light Theme. How do I update
   my theme without loosing all my customizations that are saved in my ‘Olsen Child
   Theme’ and “Additional CSS’. I have version 1.0.3 installed and am wanting to
   update to 1.7.0.
 * Thank you

Viewing 6 replies - 1 through 6 (of 6 total)

 *  [Fotis](https://wordpress.org/support/users/markwaregr/)
 * (@markwaregr)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15301062)
 * Hi,
    This is why you have a child theme initially, to keep changes when updating
   your parent theme.
 * Take a backup and update your theme. Child theme and additional css changes will
   not be lost.
 * Let me know how I can help out more
 *  Thread Starter [bdchika](https://wordpress.org/support/users/bdchika/)
 * (@bdchika)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15304351)
 * I just updated and my site is looking ruined??? any suggestions PLEASE
 *  Thread Starter [bdchika](https://wordpress.org/support/users/bdchika/)
 * (@bdchika)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15304399)
 * i fixed the issues….
 *  Thread Starter [bdchika](https://wordpress.org/support/users/bdchika/)
 * (@bdchika)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15304409)
 * So actually no it is not fixed….i restored by backup and then updated the theme
   and again my site looked MESSED UP ….the following were at the top of my pg
 *     ```
       Warning: Illegal offset type in isset or empty in /home/customer/www/borroweddelights.com/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php on line 891
   
       Warning: Illegal offset type in /home/customer/www/borroweddelights.com/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php on line 895
   
       Warning: Illegal offset type in isset or empty in /home/customer/www/borroweddelights.com/public_html/wp-content/plugins/google-site-kit/includes/Core/Assets/Assets.php on line 897
       ```
   
 * how can i update to the new version without my site getting messed up?
 *  [Fotis](https://wordpress.org/support/users/markwaregr/)
 * (@markwaregr)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15304937)
 * Hi there,
    None of these errors come from the theme but from third party plugins.
   Please disable all plugins and let me know if all errors resolve
 *  Thread Starter [bdchika](https://wordpress.org/support/users/bdchika/)
 * (@bdchika)
 * [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15306501)
 * I’ve disabled all plugins and my site still looks messed up….the warming msgs
   are gone but the site does not look at all as it should…

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘Theme update without loosing child theme’ is closed to new replies.

 * ![](https://i0.wp.com/themes.svn.wordpress.org/olsen-light/1.7.1/screenshot.png)
 * Olsen Light
 * [Support Threads](https://wordpress.org/support/theme/olsen-light/)
 * [Active Topics](https://wordpress.org/support/theme/olsen-light/active/)
 * [Unresolved Topics](https://wordpress.org/support/theme/olsen-light/unresolved/)
 * [Reviews](https://wordpress.org/support/theme/olsen-light/reviews/)

 * 6 replies
 * 2 participants
 * Last reply from: [bdchika](https://wordpress.org/support/users/bdchika/)
 * Last activity: [4 years, 6 months ago](https://wordpress.org/support/topic/theme-update-without-loosing-child-theme/#post-15306501)
 * Status: not resolved