09-19-2016, 07:33 PM
Thanks perfect. I think some of these may be best suited for US5 implementation, since there is definitely more freedom there. Some have already been implemented while others should be up for debate. But again, that is the entire point of this. If no one else chimes in, then we 3 have the debate ourselves 
One example I like is the option for changing header.php to allow custom CSS. Things which afford new flexibility are pretty easy to offer as long as they don't impact other functions.
Altering existing functionality (like the redirect) is something we certainly want to consider, but has more potential impact due to the change.
Your third point is something I would like to expand on...do you think it would be helpful starting a new thread to discuss init.php directly? We have already made some changes in US5, for example, moving more stuff to the DB out of the init...also moved some stuff from header.php to the init as well, so that header.php is really just the header info.
One example I like is the option for changing header.php to allow custom CSS. Things which afford new flexibility are pretty easy to offer as long as they don't impact other functions.
Altering existing functionality (like the redirect) is something we certainly want to consider, but has more potential impact due to the change.
Your third point is something I would like to expand on...do you think it would be helpful starting a new thread to discuss init.php directly? We have already made some changes in US5, for example, moving more stuff to the DB out of the init...also moved some stuff from header.php to the init as well, so that header.php is really just the header info.