What makes concrete5 look inside the /concrete directory for override files (and throw errors)?
Permalink
Hi There,
Occasionally, we see confusing error messages which show that C5 is looking for a custom file inside the /concrete directory instead of in one of the top-level override directories.
For example, we're currently seeing a themes error where c5 is complaining that the theme doesn't contain a default.php file.
But C5 is looking for the theme's default.php file here:
But the theme's default.php is actually in the themes directory here (and exists):
We don't know if it's Git, OSX permissions or the database - has anyone else seen this?
Any help or pointers in the right direction would be much appreciated.
Cheers
Ben
Occasionally, we see confusing error messages which show that C5 is looking for a custom file inside the /concrete directory instead of in one of the top-level override directories.
For example, we're currently seeing a themes error where c5 is complaining that the theme doesn't contain a default.php file.
But C5 is looking for the theme's default.php file here:
/website/concrete/themes/theme-name/default.php
But the theme's default.php is actually in the themes directory here (and exists):
/website/themes/theme-name/default.php
We don't know if it's Git, OSX permissions or the database - has anyone else seen this?
Any help or pointers in the right direction would be much appreciated.
Cheers
Ben
Is there any kind of pattern?
Something new been added?
Or this message actually shows infrequently but always when a particular page / pagetype / block / helper etc is called?
I can't really offer much in the way of help except that the only time I've seen such issues is when paths have been incorrectly described or are somehow ambiguous.
Maybe someone will chime in shortly with an exact answer but if not I'd be basing my initial investigations around the above.