Community Forums › Forums › Archived Forums › General Discussion › Outdated child theme
Tagged: child theme, updated child theme, version control
- This topic has 5 replies, 4 voices, and was last updated 7 years, 2 months ago by
kylehsings.
-
AuthorPosts
-
June 14, 2017 at 5:18 pm #207753
webauthor
MemberI'm currently using the Altitude Pro theme version 1.0.0. I recently noticed that the latest version is now 1.1.2.
Is there any recommended way to update to the latest version of this or any other child theme?
I haven't made any modification to the styles.css or functions.php file. Instead, I've been using both the Simple Custom CSS and the My Custom Functions plugins to make changes.
Thanks
June 15, 2017 at 12:28 am #207760Robert
MemberSimple way would be to:
1) Login To Your WordPress Dashboard
2) In a new tab/window Go to Cpanel or use FTP and navigate to your sites theme folder. Located in wp-content -> themes -> "your theme".
3) rename your active theme folder "altitudepro1" (name of your theme and add a 1)
4) In your wordpress dashboard upload the latest child theme version
5) Activate the theme and see if there are any issues
6) If there are issues - Go to your theme folder -> rename the messed up theme MyTheme2. (altitudepro2)
7) remove the "1" from the original theme folder name. To restore your site.
Should be a very quick way to test it out.
-Robert McMillin
RobertMcMillin.comJune 15, 2017 at 8:44 am #207790webauthor
MemberThanks and good idea. I understand now why there is no option to auto update a theme. Does anyone know of a changelog URL for a particular child theme?
Thanks again
June 16, 2017 at 4:56 am #207825Victor Font
ModeratorIf there is a change log, it would be in the child theme directory, not available as a URL.
As a general rule, updates have not been provided for child themes unless there was a significant problem with a release. When Studio Press released their hosting service, many of the child themes received updates to support WooCommerce. Your theme was one of them. If you're not using WooCommerce or planning to, there's probably no reason to move to the latest version of the child theme.
If you do move to the new child and you install and activate WooCommerce, make sure you allow WooCommerce to create its standard pages, otherwise content will not display on your site.
Regards,
Victor
https://victorfont.com/
Call us toll free: 844-VIC-FONT (842-3668)
Have you requested your free website audit yet?June 20, 2017 at 10:30 pm #208016webauthor
MemberThank you
November 26, 2017 at 11:26 am #213968kylehsings
MemberIs there documentation I've missed on recommendations for customizations that guard against problems when child themes are updated? Unfortunately, I've made significant changes to style.css, style-front.css, functions.php and front-page.php in a site using Atmosphere Pro. I just tried updating the child theme in order to correct the Chrome anchor problem and, of course, those changes were hosed. I then tried uploading the 4 changed files and got the white screen of death. So, I've reverted and still need a fix for anchors in Chrome.
I suppose in the future I'll modify Genesis Framework child themes strictly using plugins that store the changes in the database. Is that now a practice recommendation? And did I just miss it if it always has been?
-
AuthorPosts
- The forum ‘General Discussion’ is closed to new topics and replies.