Closed stackcoder closed 7 years ago
@joeke I see this issue just celebrated its 1st birthday. Has this been investigated already, together with #92? Seems like a pretty serious flaw if FormIt is not fully compatible with PHP 7, as more and more people will be making that switch now..
@hugopeek I'm afraid this issue lost our attention a bit. I did apply the fix for formitsaveform by removing the list() function (thanks for that @stackcoder). I'm looking into the other compatibility issues now.
@stackcoder @hugopeek All the PHP7 compatibility issues should be resolved now (See https://github.com/Sterc/FormIt/commit/4c728757a4ad05ee6822014c084369a1c5017d04, https://github.com/Sterc/FormIt/commit/d0636355a868bc70d6bb0dd292f97d00f497a9a7 and https://github.com/Sterc/FormIt/commit/a4fbd70cf9f8e98deba0cec449318f63baa39638). All fixes will be included in the upcoming 3.0.3 release.
Excellent work @joeke! It's these little invisible fixes that keep things running safely and smoothly for everyone :)
FormIt isn't PHP 7 ready. I'm not sure exactly which functionality is broken if you execute this extra in a PHP 7 environment, but if you depend on it you should not update right now.
Result of php7cc v1.1.0
Further I did some code search and noticed:
File: /core/components/formit/elements/snippets/snippet.formitsaveform.ph
File: /core/components/formit/model/formit/module/fistateoptions.class.php
List of Backward incompatible changes: https://secure.php.net/manual/de/migration70.incompatible.php