directory structure of C5.5.2.1 - empty folders
Permalink
In fact this doesnt just apply to this version, but all since i have been using concrete, so V5.4 on wards.
when i unzip the file, i see
c:\concrete\blocks, concrete\concrete, concrete\css etc
about 20 folders, all are empty except 2
concrete\config and
concrete\concrete <<<< this folder has almost the same file/folder structure in it as concrete\
but there are files in the different folders this time.
once installed on my server and running, i see that still these empty folders have nothing in them.
So.....
why are they there and are they needed?
Thanks :)
when i unzip the file, i see
c:\concrete\blocks, concrete\concrete, concrete\css etc
about 20 folders, all are empty except 2
concrete\config and
concrete\concrete <<<< this folder has almost the same file/folder structure in it as concrete\
but there are files in the different folders this time.
once installed on my server and running, i see that still these empty folders have nothing in them.
So.....
why are they there and are they needed?
Thanks :)
And just to clear up this with an example:
Let's say your customer has really strict needs on how the form block should appear. You notice that to be able to do that, you'll need to change how the form block outputs its HTML markup because you cannot style the current markup like it is required by your customer.
Now, all you need to do is to copy the form block's view template (or alternatively make your own template) to the base folder structure. These files will override the core files and you'll get it working EXACTLY like you need it to, without hurting the core.
And why not change these files straight to the core? Well, when you update to a newer version, you'd have to do everything all over again. With your overrides in place, no matter which core code version you're running, they will always override those files.
In fact, this method is used also in other CMS systems or frameworks, so this is not concrete5-specific way to handle this.
Let's say your customer has really strict needs on how the form block should appear. You notice that to be able to do that, you'll need to change how the form block outputs its HTML markup because you cannot style the current markup like it is required by your customer.
Now, all you need to do is to copy the form block's view template (or alternatively make your own template) to the base folder structure. These files will override the core files and you'll get it working EXACTLY like you need it to, without hurting the core.
And why not change these files straight to the core? Well, when you update to a newer version, you'd have to do everything all over again. With your overrides in place, no matter which core code version you're running, they will always override those files.
In fact, this method is used also in other CMS systems or frameworks, so this is not concrete5-specific way to handle this.
thanks to both of you.
This, i am sure will help others too :)
This, i am sure will help others too :)
See
http://www.concrete5.org/documentation/how-tos/developers/change-th...