You know… *sigh*… I’m so tired to customize the blog after each update. Can at least someone of developers think about this? I’m so tired to customize my themes every (very frequently) update. Is there any ideas about updating only CHANGED part of the code? You could use SVN-like system, or… *sigh*. I don’t know. Just stop this despondent mess, please. I beg you.
Make a child theme? Right now all my themes are child themes (since my edits are few and mostly related to color and images) and I’ve found it to be a wonderful tool.
i’ve read this thing, and that’s not that i want. What if i changed the code? Yes i agree, after update the style.css will not be touched, but php files, that i customized will be updated even if code wasn’t changed in some files. Also, i said about core updater too.
I’m so tired to customize the blog after each update.
If you are using a modified version of the default or classic theme, make a copy of it, give its directory a new name, rename it in its style.css, and then switch to it. Now upgrades won’t overwrite it.
Oh, you mean this operations will keep my changed php files and after update only changed files will be updated? I think no.
WordPress will only overwrite themes in the /default/ or /classic/ theme directories. If you are referring to updates of other WordPress themes overwriting your theme changes, then use a child theme (as suggested) or switch to a different theme since most non-official WordPress themes don’t update very often (or at all).
If you are modifying core WordPress files, then upgrades will overwrite your changes, which is a major reason why editing these files is not recommended.
Okay, i’ll agree with core changes protection. But about themes. My changed php files will keep? Or just things about style.css?
WordPress will only overwrite themes in the /default/ or /classic/ theme directories.
If you copy /default to /mydefault, it will NEVER GET OVERWRITTEN
But honestly, if all you’re doing is making a couple PHP file changes and a style.css, you could make /mydefault a child of /default and your PHP and CSS would always override the /default 🙂 I swear, it works! Even your changed PHP files always override the parent. I do it on three themes, happily.
@ipstenu: I got the feeling Shortman was talking about automatic theme updates, but your advice is the same either way.
Right, that’s what I said 🙂 If you copy the theme to a new folder, it never gets updated. Nothing. Not PHP, not CSS, not an image, not even the ‘buggerallthis.txt’ file you put in as a joke for a friend… and yes, I did once.
If you update it in the folder it came in (i.e. make changes in /default for your theme) then when they update the theme, you lose your changes.
So the answer is simple: NEVER update core or theme directly! Use functions or a plugin for core, and copy/child the theme 🙂
I change anything i dont like in my blog, so i want to see everything you can offer.
I can’t answer that. No one can. Why? What you don’t like and what I don’t like are vastly different. I hate curly ‘smart’ quotes, self-trackbacks/pings, single spaces after periods that end sentences, and dark backgrounds. You may like those.
So … yeah. Figure out what, specifically, you want to change and then ask about that. I’m confident that there is a plugin or function hack for 90% of it. And if not, people can sort out a way to do it.
Frequently i change only themes (php code, style.css, images etc), and i want to keep my modified code, but also i want to keep their updates. For first example:
I have downloaded a new theme with files index.php, single.php, archives.php and installed it.
I’ve changed some code in archives.php. After some time theme update has came out, which includes archive.php and index.php updates. Can i update this files without touching my modified code?
…After some time theme update has came out, which includes index.php and single.php updates. Can i keep my modified archive.php without updating the whole theme? (Because core updates not updated files)
- The topic ‘Very sad updating problem.’ is closed to new replies.