| 1 |
On 2014-01-02 8:15 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
| 2 |
> On 02/01/2014 14:46, Tanstaafl wrote: |
| 3 |
>> Hi all, |
| 4 |
>> |
| 5 |
>> I have a VM running in the cloud that has an old web/php app (10+ years |
| 6 |
>> old, believe it or not), that still runs fine on apache 2.2.25, but I |
| 7 |
>> pinned php to 5.3 some time ago. |
| 8 |
>> |
| 9 |
>> Does anyone see any big potential gotchas (major changes) with php 5.4, |
| 10 |
>> or even 5.5, if I were to upgrade it? |
| 11 |
|
| 12 |
> Impossible to say without seeing your php code. Potentially there are |
| 13 |
> many changes. |
| 14 |
> |
| 15 |
> You'd be better off doing the heavy lifting yourself first: |
| 16 |
> |
| 17 |
> 1. read all the changelogs |
| 18 |
> 2. run it in a staging vm with php5.5 and see what happens |
| 19 |
|
| 20 |
Actually, I was just thinking of doing #2 on the dev server (no dev |
| 21 |
going on, but I had this set up some time ago when we moved the |
| 22 |
production server to linode, so now at least I can test things without |
| 23 |
breaking the production system), and if it breaks, just downgrade back |
| 24 |
to 5.3... |
| 25 |
|
| 26 |
That assumes, of course... |
| 27 |
|
| 28 |
Is php difficult to downgrade after an upgrade? |
| 29 |
|
| 30 |
Thx Alan... |
Archives