Upgrading has never really been a cakewalk :). (Not complaining)
There are other time taking testing ativities that require admin's time (Not complaining)
luna template set ---> finally someothertemplatename set (obviously with names corected in css) --> visible to users (unaffected by upgrades) ... not sure if this would not break anything. Shouldn't AFAIK
luna (original -- with local deleted) there in working installation so that upgrade's does not complain. Post upgrade Admins would always prefer to go thru each detail before applying it to working install. In fact this would only be made readable/writebale before upgrades for some reasons.
Now if core.css is made a compulsion, then perhaps yes, there would be no option but to have a core.css + custom.css
Thanks
Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================
There are other time taking testing ativities that require admin's time (Not complaining)
luna template set ---> finally someothertemplatename set (obviously with names corected in css) --> visible to users (unaffected by upgrades) ... not sure if this would not break anything. Shouldn't AFAIK
luna (original -- with local deleted) there in working installation so that upgrade's does not complain. Post upgrade Admins would always prefer to go thru each detail before applying it to working install. In fact this would only be made readable/writebale before upgrades for some reasons.
Now if core.css is made a compulsion, then perhaps yes, there would be no option but to have a core.css + custom.css
Thanks
Thanks
HyTC
==================================
Mail Me If Contacting Privately Is That Necessary.
==================================