[RESOLVED] quick upgrade to 5.6
I need to upgrade from 5.2. to 5.6 . Is there a quick way to check my (zillion) scripts to make sure I don't have any problems when they run under 5.6? I am still using DzSoft PHP editor and I am not sure if I simply need to install 5.6 for DzSoft to check my code.
All help is very much appreciated.
I can't think of a quick way to check that doesn't involve having unit testing in place to begin with.
The four pages in migration53, migration54, migration55, and migration56 that deal with backward-incompatible changes list that things that could break when going from 5.2 to 5.6. Those at least give you things like function names that you can do a search for to see if how you're using them is still valid (a while back I had to search through my code base to find places where I'd used preg_replace's /e modifier), but there are some that can't be found that way (such as functions expecting call-by-reference arguments being given literal values instead).
And with PHP 5 having recently entered into its "security fix only" phase, you can start thinking of the fun you'll have of upgrading to PHP 7 and more extensive list of incompatibilities.
Last edited by Weedpacket; 03-02-2017 at 05:35 PM.
High Energy Magic Dept.
Sounds like a job for a robust unit test suite and a VM or Docker image where you can try it out.
I'm not familiar with DzSoft, but it likely uses the "php -l" option to "lint" check the source code, so you could conceivably install a separate instance of PHP 5.6 and point the editor to that executable, assuming its config has a way to do that?
Settled 4 red convertible
+1 for VM's. Set one up like the prod server and put your stuff there first, and parse error_log like there's no tomorrow. And tell the boss he needs more people assigned to QA, and you'll gladly supervise them for a 10% raise ...
The problem is I am the head, cook and bottle washer - so, there is no 10% raise insight. She, who must be obeyed, will see to that.
OK, all joking aside, I have a Virtual Server setup and I have 7 months to do my testing. But, I did receive some very good advice here and I thank everybody for that.
I won't mark the thread as complete as yet, just in case there is somebody out there who has more ideas.
I upgraded 5 projects from 5.6 to 7.0 without changing any code, by not relying on any deprecated features. So as long as you can run with full error_reporting and no errors, it should be easy.
Originally Posted by Weedpacket
Sadly, nobody codes for anyone on this forum. People taste your dishes and tell you what is missing, but they don't cook for you. ~anoopmail
I'd rather be a comma, then a full stop.
User Authentication in PHP with MySQLi
- Don't forget to mark threads resolved - MySQL(i) warning
Well, I had a problem this morning with 2 of my sites. Turned out, I had sent 5,000 emails (whilst I was still asleep) and about 100,000 emails where queued up. That is what sparked the entire process.
I will check with Godaddy, to see about PHP7.0 a bit later.
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)