Heya, Just wanted to remind you that the latest Smarty 2.x version is 2.6.26, released in the middle of 2009... 3 years have passed by, and change is something that cannot really be stopped. You can either freeze the environment and plan to re-build your projects or maintain them, applying change as it comes, or maintain the older software in-house (you will end up with something really hard to manage). I can suggest you (at least it works for me) to use a continuous integration environment/server and run your sites with a dependency manager like composer (or something like an svn:external to a "latest" branch of the dependencies). Running the "composer update" command, the version of the software used by my projects gets automatically bumped to the latest available one, and then the CI environment runs the tests. That doesn't ensure that 100% of everything will work, but reduces the efforts needed to keep up with changes. This doesn't apply to major version changes like Smarty 2.x -> Smarty 3.x, obviously, but I hope it helps in reducing your workload while encouraging change and making it smoother. As said by Ferenc, you cannot think of avoiding refactoring (at least without freezing the project), that's part of our job.
Marco Pivetta http://twitter.com/Ocramius http://marco-pivetta.com On 25 August 2012 11:27, Ferenc Kovacs <tyr...@gmail.com> wrote: > 2012.08.25. 11:16, "Lester Caine" <les...@lsces.co.uk> ezt írta: > > > > Many of my 'problems' with all of the 'progress' being made with PHP are > caused because I'm using a core framework who's origins go back to PHP4 > days. Many of the facilities are currently unusable simply because they > have not had any of the PHP5.2/3/4 changes applied while all the stuff that > is still being used actively on live (paying) sites have been updated even > to be E_STRICT compliant. > > > > ADOdb has provided me with an ideal base for many years, and the data > processing systems have been fine tuned over many years with PDO actually > being more of a hindrance to performance than an improvement. The reason > for that being that the generic data structures developed for generic > drivers are at odds with the PDO 'style' and so extra conversions can be > needed so the generic drivers are used. > > > > I'm still on Smarty2 as the templating system as switching to Smarty3 > will require another long conversion process, and we are up to speed with > what S2 can do - and it works. > > > > All of this is working on a base which allows a sites whole style to be > remodelled simply from the css theme and we can add modules easily ( > reusing the core system code ). I can 'copy' an existing 'static' site and > enhance it with on-line editing and other interactive facilities in a few > hours while maintaining the same style that the owner is used to, and this > is what we are doing with many of the older sites we have taken over > support for. > > > > The main problem here is that the likes of the Zend framework and other > 'controller based' systems seem to be way people want to see PHP develop, > so keeping 'older' style systems working is getting more and more > difficult. > > > > The question ... how many other people are fighting the same up hill > struggle? > > > > -- > > Lester Caine - G8HFL > > ----------------------------- > > Contact - http://lsces.co.uk/wiki/?page=contact > > L.S.Caine Electronic Services - http://lsces.co.uk > > EnquirySolve - http://enquirysolve.com/ > > Model Engineers Digital Workshop - http://medw.co.uk > > Rainbow Digital Media - http://rainbowdigitalmedia.co.uk > > > > > > -- > > PHP Internals - PHP Runtime Development Mailing List > > To unsubscribe, visit: http://www.php.net/unsub.php > > > > So what do you propose? > There always will be people who don't want any new fearure or improvement > but their code workinf forever without any investment(refactoring) on their > part. > We shouldn't stop the development for that alone. > If I were them, I would pick an enterprise distro like rhel, where I can > get just that: same php version for many years with support. >
