Override for includes/modules/pages?

[swguy]

In includes/modules/sideboxes, there's a "classic" directory. This is your clue that the directory can be overridden. The directory includes/modules/pages does not have a classic subdirectory and cannot be overridden, so be sure to make a backup of (and notes about) any files you change.

The things you can change in includes/modules/custom are files from includes/modules, such as column_left.php.

Good luck,
Scott

[Website Rob]

And do I understand correctly, 'template_default' is the exception to the rule?

i.e.
any file / dir. within the 'template_default' dir. can be copied over, or are we restricted to just 4: common, css, images, templates, and their subsequent files?

[swguy]

template_default is the baseline. Copy out of here into your own template and start modifying. This directory is overwritten every release, so you don't want to modify files in here.

Good luck,
Scott

[DrByte]

Yes, overrides outside the "templates" folder are 1-level deep.

http://www.zen-cart.com/index.php?ma...roducts_id=298

[Website Rob]

Nice chart, DrByte. Thanks for pointing it out. Don't think I would have found it otherwise. Hopefully, the downloads section will one day become searchable.

The chart indicates that only 3 main directories are worked with for overrides.
includes - languages, modules, templates

Although the chart looks like it is/was part of something with more information on overrides, if I know the 3 above dir. are all I need to focus on then it definitely helps to focus on the required areas.

I find I'm asking a lot of questions on the override setup because I have not yet wrapped my head around its proper usage. Will be doing a CSS Template shortly that I would like to freely offer to others and that should answer a lot of questions as well. Don't know about others but completely understanding how the overrides setup works, is so very important and for many reasons.

[qhome]

. The directory includes/modules/pages does not have a classic subdirectory and cannot be overridden, so be sure to make a backup of (and notes about) any files you change.
Scott

Why is that ? I just came across this trying to be Zen-like and come to find I can't. Is there plans on using overrides here in the future?

[swguy]

I have no earthly idea. But if you feel strongly - and it appears you do - put a note in the suggestions forum. Adding a donation might help it percolate up too.

Good luck,
Scott

[DrByte]

Is there plans on using overrides here in the future?

No .

[swguy]

Well there's your answer!

What I do in cases like this is to keep a copy of the unchanged file as

<filename>.orig

Then when it comes time to upgrade, I can consult my notes AND search for *.orig to be sure I catch all the files that need manual merging.

Good luck,
Scott

[qhome]

Well there's your answer!

What I do in cases like this is to keep a copy of the unchanged file as

<filename>.orig

Then when it comes time to upgrade, I can consult my notes AND search for *.orig to be sure I catch all the files that need manual merging.

Good luck,
Scott

Ya i used to do that.. but now I find it easier to backup the new version... then after the upgrade overwrites my existing file, I can just merge it with a copy of my backup.