Why duplicate folders in C5 directory ?

Permalink
Hi guys !

I just realized that my C5 installation is kinda duplicated. On my root server, I have a directory named "concrete" and all folders inside are empty except (another) 'concrete' 'packages' and 'themes' plus 3 files (index.php. htaccess, sitemap.xml.
If I open the 2nd 'concrete' then I see the same folders again but this time with files insides.
ALthough my C5 is working well, I find it a bit messy and wonder if I should clean that up and pull the (2nd) concrete directory one level up then delete all the other empty folders ?

Please see screen copy attached.

THANK YOU all for your help :)

1 Attachment

 
Maynar replied on at Permalink Reply
Maynar
DO NOT DELETE any folders you have. The structure you have now is correct.

The "concrete" directory contains all "Core" features and the other directories are for add-ons/plugins.

Even when you don't use them, don't delete them.
nathan replied on at Permalink Reply
nathan
I was under the impression that the empty folders were for overrides, i.e. you want to change the way [root]/concrete/blocks/autonav/templates/header_menu.php works, duplicate the original into [root]/blocks/autonav/templates/header_menu.php. By doing this the file outside the concrete directory will be used instead of the file inside the concrete directory.

This is my understanding and this is what I'm currently doing and it's working.

I must admit that it can be confusing, the file structure is a little confusing, would it not be better to have both a core directory and an overrides directory, the overrides directory should then take priority over the core dir, this would certainly tidy up the root directory and probably avoid the confusion.

Just my 2c...

Cheers.
Maynar replied on at Permalink Reply
Maynar
Yeah they might also be for overriding, I am not using it. I use them for when I create blocks, controllers and single_pages.
mikehall5 replied on at Permalink Reply
*OK just a (bad) joke :)
Thanks Maynar I got the message and won't delete anything but as Nathan mentioned (and I totally agree), the file structure can be quite confusing...
For an easy and very clear CMS like C5, there might be a way to make the file structure a bit more intuitive too.
I wonder what's the opinion of Franz on that subject (?)
THANK U guys!
Remo replied on at Permalink Reply
Remo
I agree, it can be confusing at the beginning but it makes a lot of sense..

There are some root folders which you can delete though. I realized this when I used an extractor that doesn't extract empty directories.. I just had to create another two directories or so and it worked.
ijessup replied on at Permalink Reply
ijessup
the file structure makes perfect sense when you understand how it works. There is a method to the madness.
frz replied on at Permalink Reply
frz
that's there for a good reason. The /concrete directory off of the root is your core concrete directory. that stuff /should/ be updateable with a version release and not impact your site.

the reason why is you do have the second /concrete directory, and anything you put in there will be used before the stuff in the root /concrete directory will.. think of it as an override.

this doesn't always mean 100% upgrades (obviously) but it does make it much easier to build complicated sites without "damaging the core" or "forking the code"

we didn't make this technique up, we ripped it off.
ijessup replied on at Permalink Reply
ijessup
when you can set up folder aliases. You can host the core code from a repository and make upgrading seamless.

That way you upgrade everything in the blink of an eye without touching your own mods/blocks/packages/etc.
mikehall5 replied on at Permalink Reply
Now I understand this structure is there for eventual updates and can be a safer way to upgrade some folders.
Just needed to have a clear answer (even from the CEO) and this is now done and available for others through the forum search ;)
Pretty clear. Thank you all !
macromax replied on at Permalink Reply
First of all, this is a great idea. I wish other scripts did this. However, the duplicate directory names almost guarantees I'll end up accidently modifying wrong file at some point. Couldn't you change the folder names slightly? For example add "core" or "c" to each directory in the core script.
tallacman replied on at Permalink Reply
tallacman
It works great. Don't change anything (except the way you think about the folder structure).

This website stores cookies on your computer. These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media. To find out more about the cookies we use, see our Privacy Policy.