Updating themes questions

I meant:

“…since they tend to cause less problems when updating”

sorry

The main point of using a Child Theme is so that you don’t lose your modifications when the template (i.e. the “Parent” Theme) is updated.

If you like the style/design/functionality of a particular Theme, but only want to tweak the style to suit your needs, then using a Child Theme is ideal.

If you want to make more involved/complex/functional changes to a Theme, then at some point you will want to consider forking it (i.e. modifying the Theme, renaming it, and maintaining it yourself).

So when forking a theme, I’ll lose my modifications if I update it?

So how can it be updated?

If you fork a Theme, you’re the only one who will ever update it.

That’s the point: a forked Theme is a different Theme for the original. It’s no longer functionally linked to the original. If the original is updated, the forked Theme is not updated.

oooh, I understand. But if a theme is updated I can check the updates and transfer them to the forked theme, right?

Just to be sure, the wordpress and plugins are a different scenario, meaning the updates do not imply loss of modifications, is that correct?

oooh, I understand. But if a theme is updated I can check the updates and transfer them to the forked theme, right?

Absolutely. The caveat is that you would assume responsibility for pushing those changes downstream to your forked Theme, whereas with a Child Theme, you still get those updates automatically, without losing your own modifications. (In the latter case, you just assume the responsibility that your modifications remain compatible with the as-modified Parent Theme.)

Just to be sure, the wordpress and plugins are a different scenario, meaning the updates do not imply loss of modifications, is that correct?

I don’t understand what you’re asking here.

Hum, my doubt is related to the plugins and wordpress’s updates. It may be a dumb question, but imagining I have a forked theme, when there is a newer wordpress/plugins version available, I can update easily. In other words, there is no risk of losing my modifications, like the case of a theme update?

WordPress core, Themes, and Plugins all update separately. Within Themes and Plugins, individual Themes and Plugins also update separately (although the process can be run in bulk for both Themes and Plugins).

In all cases, settings that are stored in the database are entirely unaffected by core, Theme, or Plugin file updates (though if core, a Theme, or a Plugin changes its option schema – i.e. adds, removes, or renames options – you may see an impact on your particular settings).

ooh ok, so that should be fine. It is just the case of saving a copy before updates.

One final question if it’s okay, I heard that the problem with child themes is related to heavy sites. Taking that into account I began to think that child themes are not a good solution for an online multimedia newspaper that is daily updated. Do you think that makes sense?

I heard that the problem with child themes is related to heavy sites. Taking that into account I began to think that child themes are not a good solution for an online multimedia newspaper that is daily updated. Do you think that makes sense?

Child Themes present absolutely no inherent performance issues or problems whatsoever. At its most basic, a Child Theme is nothing more than a CSS stylesheet.

ahah, in that case it will be difficult to make a decision. If the theme needs a lot of modifications, maybe it is best to fork it. That will be my thought when reaching a decision.

Thanks for all Mr. Bennett!