Override system seems complicated

[Syntax2]

Well it would be nice if someone pointed out that when you create your own template all the boxes/banners/search/cart modules that are on the left and right of the page get disabled by default..

At least mine did.. all this time Ive wasted to find out that the page was blank because all the modules were turned off..

[Ryk]

Well it would be nice if someone pointed out

You didn't actually ask a question...you came on here with a first post that's bit of a rant, and from your comments, I'm guessing that you leapt straight in. You certainly haven't read the tutorials/FAQ section as if you had, you'd have found the one labelled How do I create a new Custom Template? which tells you EXACTLY what you need to do to create your own custom template folders.

ZenCart is downloaded hundreds of times a day; there a thousands upon thousands of ZC stores around the web. Almost any question you can think of will have been asked - and answered - somewhere within these forums...so search, then ask if you still can't find what you're looking for.

You'll find this an amazingly helpful community - but don't just moan.

[styledata]

The override system does seem to be one of the most misunderstood features of Zencart. And one of the biggest topics on the forum. I have wondered why the folder system for overrides is not simply built into the release, as empty folders, under the name CUSTOM. A short text file in each folder could explain what you could put in there.
Failing that, it would be great if someone came out with a contribution that created all the folders for a custom template for you, in the proper structure, that you could upload to your site, with a text or html file explaining what to do.
I may be naive in the world of coding, but this seems to me to be one of those things that could be easily rectified by one of the two approaches.

[Merlinpa1969]

I have wondered why the folder system for overrides is not simply built into the release, as empty folders, under the name CUSTOM. A short text file in each folder could explain what you could put in there.

Hi Style,
while this sounds like a good idea, it would then have the same issue as using the classic folder.
it would be over written the next time you upgraded.

the other sounds feasible and I might just do that later this afternoon.

[Merlinpa1969]

Here go,
its quick and its easy but its the entire template file structure
with a read me for each folder explaining what needs to go where

Custom template base file structure

[styledata]

Here go,
its quick and its easy but its the entire template file structure
with a read me for each folder explaining what needs to go where

Custom template base file structure

Wow that's fast service! Looks great. I hope it saves YOU folks some time in answering questions, so you can keep working on the magic for us.

[clydejones]

Here go,
its quick and its easy but its the entire template file structure
with a read me for each folder explaining what needs to go where

Custom template base file structure

Merlin,

You might want to point out in your Overview and How To that although the folders are named "custom" they can be renamed to anything the user wants.

If you don't mind, I think I'll reference the download in a couple of tutorial/FAQ articles as well as in the wiki.

[Ryk]

You might want to point out in your Overview and How To that although the folders are named "custom" they can be renamed to anything the user wants.

And you must spell it out that they must all be the same!

Because if you don't , someone will come along and say "Well it would be nice if someone pointed out that when you..."

(Oh, and could we have a set called YOUR_TEMPLATE please)

[Ryk]

The instruction "wherever you see a classic folder, you can place your own custom one alongside it" doesn't really leave much room to screw up!

[Ajeh]

I am sorry that you had difficulty in reading all of the FAQs and Wiki for getting started in addition to trouble using the search ...

The templates and overrides directories are all marked, as indicated before, by the /classic directory to help as a guide to lead you to where and what can be overridden ...

The template structure itself is based on /includes/templates/template_default

But you will note that the only things in the /includes/templates/classic are the bare essentials ...

You never copy a file to a templates and overrides directory unless you are actually making changes ...

Languages follow the same pattern in the /includes/languages

At various levels you will again see the /classic directory ... this means that is where overrides for that given directory would belong ...

The same holds true on the code side of the directory structure such as:
/includes/modules with overrides indicated to go to the /includes/modules/your_template_dir because again you will see the /classic directory ...

There are no overrides for functions and classes, but you will see the /includes/functions/extra_functions directory ... this is a location of where you can add your own functions and they will autoload for you as if part of /includes/functions files ...

Again, not as overrides but as additional or extra functions that you may need ...

Similarly you will see in the /includes directory
/includes/extra_configures
/includes/extra_datafiles

These are made for adding on to things like new database define and new filename defines without having to touch the original files ...

You can use 1 or many files in the /extra_something directories so that add-ons, your own code, etc. is more easily managed ...

I do hope you will take advantage of the forum, FAQs and Wiki to help make your Zen Cart experience more meaningful ...