Running separate themes via multistore, what happens to modifications?

Hey folks,
So I managed to convince client that to separate retail and wholesale functionality, we utilise multisite (this did not just pertain to customer groups FYI, many little mods that the settings would not handle).

So far so good (awesome in fact!).

Question: I have several small page items eg. a message in footer explaining that all prices include tax. On the subdomain, I wish this to say the opposite. Should I simply use a function in my controller to check which store and output relevant text... or should I create a duplicate theme and make the required changes in that.

Further to this, my default theme uses several extensions, and I have noticed one alters the header.twig/product.twig - how does this work when using a new theme? eg. what happens to the modification structure??

Ok so to answer my own question (and help others), refreshing the modifications edits both the existing and new theme files. This makes me very happy

This is an old post but just to help anyone searching. The modification will automatically work on any template if the file path has a "*" wildcard in the file path of the template being worked on. For example catalog/view/theme/*/template/common/header.twig (same for both twig and tpl tenplate files)

This is the same with language files and is the same for ocmod and vqmods

frgot to mention that it will work NLy if xml instructions will find in x theme what and where to change or add. Because all templates twig/tpl files willhave mostly other html code so mostly if the moduleis related with changing something in tpl or twig files for each theme it may be required to add extra xml rules in a module to find exact matches based by theme used

Jeremy Fisk wrote: ↑

Sun Apr 14, 2019 4:03 pm

This is an old post but just to help anyone searching. The modification will automatically work on any template if the file path has a "*" wildcard in the file path of the template being worked on. For example catalog/view/theme/*/template/common/header.twig (same for both twig and tpl tenplate files)

This is the same with language files and is the same for ocmod and vqmods

D3MO wrote: ↑

Sun Apr 14, 2019 9:05 pm

frgot to mention that it will work NLy if xml instructions will find in x theme what and where to change or add. Because all templates twig/tpl files willhave mostly other html code so mostly if the moduleis related with changing something in tpl or twig files for each theme it may be required to add extra xml rules in a module to find exact matches based by theme used

Jeremy Fisk wrote: ↑

Sun Apr 14, 2019 4:03 pm

This is an old post but just to help anyone searching. The modification will automatically work on any template if the file path has a "*" wildcard in the file path of the template being worked on. For example catalog/view/theme/*/template/common/header.twig (same for both twig and tpl tenplate files)

This is the same with language files and is the same for ocmod and vqmods

Nice tip, however that is general knowledge and is true in all cases - even if you have a single template. OCMOD replace works only when it finds matching expression.