2012-03-23, 07:17:04
I've just re-organised the files in my developmental Coa theme as follows:
I also hacked a core GS file (naughty, I know!) to allow .coa files to be edited by the Theme Editor. I changed line 89 of admin/theme-edit.php to:
I think this might allow me to build something I can unleash on a client now
- template.php - code soup replaced with include. Also changed file permissions so it can't be opened/written by GS, and added comments explaining the editing ban and pointing to Coa documentation.
- coa/coa.inc - includes the code soup that is the Coa engine - included in template.php
- coa/constant.coa
- coa/page.coa
- Also other directories: css, img, js
I also hacked a core GS file (naughty, I know!) to allow .coa files to be edited by the Theme Editor. I changed line 89 of admin/theme-edit.php to:
Code:
$allowed_extensions=array('php','css','js','html','htm','coa');
I think this might allow me to build something I can unleash on a client now