I've been looking into how Theme Fall-back / Hierarchy works since CE 1.4 and I think I've fairly well understood it.
Then I move a legacy theme (the names
purple_theme following are exemplary) which had been put inside the legacy locations:
Those files have now been moved into the more appropriate, namespaced and currenlty as best-practice suggested ones:
This so far looks fine to me and is more or less just context of my question. It gets more interesting when I add magento extensions / modifications into the mix.
Some third-party plugins now have placed files into the old (and according to What About
default/default? (Magento's Theme Hierarchy Changes in CEv1.4 and EEv1.8) deprecated) location (even that plugin for example is a Feb 2014 release).
If I read the documentation it's now the case, since the moment I activate the new theme
purple_theme, the fall-back to
default/default will not be triggered any longer. Is this correct?
And so I now wonder what is best to do. Should I duplicate (copy) all those files into my own theme's
default directory (
purple_theme/default)? Or should I move those files?
Or should I copy/move them into
base instead (the extension files in question are within their own sub-directory, e.g. for the Payone plugin, it's
skin/frontend/default/default/payone/core/mandate.css)? What would be recommended practice here?
From my own (so far limited view, I don't have that much Magento experience), I tend to moving those files into
base/default so that every theme will benefit from the extensions changes (I also have the full tree under Git version control, so I'm sort-of relaxed that file-changes are easily tracked).
Also is it good practice to discuss this with extension developers? What are common guidelines to give to them?
I've seen Custom Package/Theme for Admin module that falls back to default package? which is about admin configuration (and version 1.8) so I'm not sure if it would apply for frontend as well (and if already since version 1.4).
I even think about having something like Magento Enterprise Theme Fallback (Sonassi) with the difference, that I don't want to have fall-back to
frontend/default/default. Via Theming - starting from scratch.
(Exemplary extensions that are in use: One-Step-Checkout, Payone and Customer-Credit; Currently on an outdated 1.4 version, as you can imagine this is also in the light of upcomming Magento upgrades)