2. PHPRunner General questions
  3. Best Practice Advice
This topic is locked

Best Practice Advice

 		4/9/2011 12:07:18 PM
PHPRunner General questions
A
 alicea author

Hello everyone,
I recently had a "minor" issue editing a 5.0 file with 5.3 which was easily corrected. I've been using PHPR since 5.0 and my question/concern is, as PHPR evolves and clients come back after a few years for changes/mod's, what is the best way to deal with this?
In the manual world, this is a non-issue as an older script does not really affect the programmer. But in the PHPR scenario where a newer program has to open an older file, as the years go by, this could present problems is my concern.

  • So I am worried about nothing meaning core functionality will always be backward compatible?
  • For those users that have been using PHPR for many more years than I have, how have you dealt with this?
  • Is there the possibility of a current or future version of PHPR that at some point won't work on an older file?
    I think I've expressed my concern and would like to have a plan in place as my intent is to continue using PHPR for all development.
    Thanks for all input.
H
 		horsey_kim 4/10/2011

That has been one of my issues too. I actually have some clients who I used ver. 4.2 and did a TON of custom work to make it function well.
When you install a new version of PHP it usually makes a new folder in the program directory for it. So I say until you can work out the kinks moving an older version of a project to a new version of phprunner, don't delete the older version of PHPrunner. And before you update the project to a new phprunner, make a backup of the project files. That way if it all fails, you can wipe off the server, and run the backup through the older version of PHPrunner and get the site back the way it was.
Just an idea,
Kim
Sergey Kornilov admin 4/10/2011

You are always able to open older projects in the latest version of PHPRunner. We never drop any functionality that old application rely on.