Shopping cart content

[Kevin205]

On the shopping cart it says:
'You may want to add some instructions for using the shopping cart here. (defined in includes/languages/english/shopping_cart.php)'

Don't these type of revisions require override files for custom template? Or changes are made in includes/languages/english/shopping_cart.php?

If an override is not necessary, what is the reason for includes/languages/english/Your_template/ folder, which contains and "emty.txt" file?

[Ajeh]

The original language file is displayed in the text so that you can locate the file that you need to change and, yes, you should use your templates and overrides for your custom changes ...

[Kevin205]

Good to hear from you again Linda. Please excuse me as my brain is not functioning properly this morning!

So is it safe to say, for any change whatsoever (from simple text to code change), one should create an override structure?

And in this case the override should be includes/languages/english/Your_template/shopping_cart.php.

[stevesh]

Yes, and yes. Some files can't be overridden, but it's a good idea to use the override function when possible.

[Kevin205]

Yes, and yes. Some files can't be overridden, but it's a good idea to use the override function when possible.

Thank you.

[schoolboy]

The GENERAL RULE for whether a file has an over-ride capability is to check if there is a "classic" folder visible.

Wherever you see a "classic" folder (be it in LANGUAGES, MODULES or TEMPLATES), you can safely put in another folder named after your CUSTOM folder set.

EG:

/includes/modules/classic/

allows for:
/includes/modules/YOUR_CUSTOM_TEMPLATE_NAME/

and

/includes/languages/english/classic/

allows for:
/includes/languages/english/YOUR_CUSTOM_TEMPLATE_NAME/


and

/includes/languages/english/html_includes/classic/

allows for:
/includes/languages/english/html_includes/YOUR_CUSTOM_TEMPLATE_NAME/

NB: Do not RE-NAME "classic"... ADD your custom folder at the same directory level...

[Kevin205]

Great advise.

I have not added any custom templates. I am working and revising the stock template from 1.5.1 called "Classic Contemporary Green" and as you know the template directory is called "classic".

Thank you.

[schoolboy]

Great advise.

I have not added any custom templates. I am working and revising the stock template from 1.5.1 called "Classic Contemporary Green" and as you know the template directory is called "classic".

Thank you.

ER... not a good idea...

CLASSIC is a useful diagnostic tool... when a CUSTOM template gives problems, reverting to "classic" often helps point to the problem.

You can CLONE classic and then build your own template (with overrides), but it is not a good idea to tamper with classic.

[gjh42]

You should use a separate template folder for your custom template, even if it starts from the Classic design. Copy all /classic/ folders to /your_template/ folders (whatever name you want to use) and start with new modifications there.

You could then upload new copies of /classic/ folders from a fresh download of Zen Cart, to give you a clean Classic template to use in debugging if necessary.

[Kevin205]

ER... not a good idea...

CLASSIC is a useful diagnostic tool... when a CUSTOM template gives problems, reverting to "classic" often helps point to the problem.

You can CLONE classic and then build your own template (with overrides), but it is not a good idea to tamper with classic.

You should use a separate template folder for your custom template, even if it starts from the Classic design. Copy all /classic/ folders to /your_template/ folders (whatever name you want to use) and start with new modifications there.

You could then upload new copies of /classic/ folders from a fresh download of Zen Cart, to give you a clean Classic template to use in debugging if necessary.

Since I have been working on it for a while now, I guess I have to rename "classic" to "My_Custom_Template" and possibly re-install the the "classic" template?

Any suggestion on the best way to accomplish that task?

Thank you.