July 21, 2015 at 17:49 UTC - Views: 2 #18056
Is it necessary for me to create child themes for upcoming changes to themes? Or will the updates not screw up my present theme? Thanks..(As you can see, I am new to this.)July 21, 2015 at 17:55 UTC - Views: 1 #23507
Child themes are an advanced technique used if you need to alter the behavior of standard theme files (for any theme). You should never, ever modify the original theme’s files – but create a child. Very few people need to do that. Child themes allow you to alter code in the original theme in a way that allows the theme to be updated, yet preserves the changes you made in the child theme.
But we are talking about files, not settings. If you are just using standard themes options, then updates won’t change anything with your settings.)July 21, 2015 at 18:01 UTC - Views: 1 #23508
I think I understand what you are saying…for example if I get a notice that there is an update for my theme from 1.2.2 to 1.2.4..do I need a child theme to do this?July 21, 2015 at 18:12 UTC - Views: 1 #23509
I suspect the answer you need is – NO, you don’t need a child theme UNLESS you’ve directly edited a file from the existing version of the theme. That is a HUGE no-no, but sometimes ignorant plugin authors will tell people to do exactly that – modify a file in a theme. That should never never never be done. That is when one needs a child theme.July 21, 2015 at 18:36 UTC #23510
Thanks a lot, weaver. So all I need to do to make the necessary changes to weaver ii, update 2.2 etc..is to install the Weaver ii theme extras plugin and follow instructions…no child theme needed..July 21, 2015 at 18:36 UTC - Views: 1 #23511scramblerModerator
All settings including Custom CSS you put in the admin pages survives any updates.
As a regular precaution, always save and backup your settings first using the Save / restore page SAVE button and Download All settings optionJuly 21, 2015 at 18:45 UTC #23512
This is my first time doing this. I have not made any custom css…Thanks for all your help. I am especially happy that I do not have to create a child theme, this is waaay beyond my technical capabilities. Appreciate the help.July 22, 2015 at 08:24 UTC #23513BobthearchParticipant
The best part about WeaverX is that child themes are generally unnecessary. The WeaverX interface is designed with special areas for inserting custom code where it will be preserved through WP updates.
It seems as if most other themes and some plug-ins expect users to create child themes, a process that is rather complicated and unsupported by WordPress.July 22, 2015 at 16:47 UTC #23514
Your last point is one that I have a huge philosophical difference with what seems to be the majority opinion of those in charge of WP.org. That idea – create child themes – is EXACTLY what they want. There seems to be a philosophy to only allow professionals to create highly customized sites – usually via very complex CSS and child themes.
The whole point of Weaver is to allow highly customized sites using checkbox options. Designers with more experience can add custom CSS pretty easily, and the real experts can build child themes, but it is almost never necessary at all.
But because of the philosophical differences, Weaver has always been treated with some disdain by may of the mail power brokers at WP. Quite unfortunate.July 23, 2015 at 05:11 UTC - Views: 2 #23515BobthearchParticipant
Another big advantage of entering custom code in the WeaverX Options panel instead of directly editing the WordPress files, it’s easy to find the user-created code again and undo it / re-do it / modify it. All without any ‘permanent’ changes or potential damage to the WordPress template files.
- You must be logged in to reply to this topic.