I've been looking at updating my store to ZC v9.3.9h - and find that I may have really built a sand trap when I worked on the v1.3.8a code...When comparing the original store with the v1.3.8a files, WinMerge revealed that I have a number of override code that is in the files that will be updated by v1.3.9h...instead of being in the "custom" override folders. So, OK - I'll move the code t the "custom" folder and it'll be fine...right?
Not quite.
In reviewing the structure of the override system, I see that some of the files I modified are not in folders with a "classic" directory, as indicated in the tutorial as the "key" to if a file can be overridden. Or are they? Are the override operations on a single - or a multiple - basis?
In other words, if I want to override the "/includes/languages/english.php" file, I can create a copy file - "/includes/languages/CUSTOM/english.php" - because there is a "classic" folder in the original folder.
But what of the "/includes/templates/classic/css/stylesheet.css" file? It is in the "classic" folder, 2 levels down...I can make a "/includes/templates/CUSTOM/ css/" path with the "stylesheet.css" file copy, but does the override reach 2 levels down?
And do I copy ALL of the "classic" folder over to "CUSTOM", or just copy the files I need to change?
Finally, in the tutorials I see that I can use "template_default" like the "classic" sense - ie:"/includes/templates/template_default/templates/tpl_***.php" can be copied to "includes/templates/CUSTOM/templates/tpl_***.php"...so it would seem that the override does go more than one level...at least with the templates.
Oh, and do I need to tell the override that it exists and should run the override code instead of the ZC code?
Sorry to sound so confused, but really, I am! I wrote the code about a year ago, and basically got it working and went on to other things...now I am paying the price for that in having to relearn it all over.
Bookmarks