I’m not sure about that. I just did this a month ago with a server, moved it to 7.2. With error reporting on, I was able to find all the errors that 7.2 complained about. Including the count errors for arrays.
There’s no point in doing any PHP 7.x stuff unless it’s all 7.2+. 7.0 is EOL, 7.1 is EOL at the end of the year so 7.2+ is the only logic version to build against. Otherwise you’re just back in the same boat, running an unsupported PHP release.
Honestly, FreePBX 15 doesn’t really excite me like v14 did. For me this is a release that was made more grandiose than it really is. I also consider this a release that is over 18 months behind as it was announce shortly after the release of v14 that there would be a six month release cycle for major version updates. Thus v15 was supposed to be public by Jan 2018 and it’s now July 2019. Which according to a six month release cycle means we should have v18 coming out now.
I mean let’s just look at v14 vs v15. We had an Alpha release of v14 in Jan 2017, Beta by March/April-ish and the Stable was released July 2017. Six months. In contrast, we waited for over a year and a half for a beta of v15 and it’s still in Beta with no time table of its release to stable.
I think that part of the problem is the lack of having a LTS release or any real plans on releases. FreePBX v13 is not really supported but is supported somewhat if you have HA because it’s the only release that still supports it. v13 will be considered officially EOL when v14 (or v15) have HA support. It’s also been 18 months on v14 having HA support that’s still no where near anything public as far as I’ve seen. So that begs the question, will v15 having proper HA support? Because I can’t see a company taking $3,000 product and killing that revenue stream for 18 months. Well I can if either 1) It’s so broken that it is unsellable. 2) It just wasn’t selling to meet quantities that make keeping it maintained and supported financially viable. 3) Combo of 1 & 2.
Again, this is just me. Not looking to start some epic battle with anyone over this.