the changelog entry says "fixed API receiving null and false instead of an array in method parameters"
this issue was about zabbix frontend + php7.
is zabbix frontend now officially working & supported with php7 ? if so, should that be mentioned in the changelog, maybe ?
Ivo Kurzemnieks It's not about all php7 related problems in the frontend. If such problems occur, it should be split into multiple tasks. There could be numerous things for improvements and so on. The issue was about user trying to log out on php7 and got a fatal error. The main problem occurred deeply in API core. There were more ways to generate fatal errors breaking the API, just by simply not giving "params" in request. In other words - function arguments. The thing that was fixed, was that API received "null" and "false" instead of an array. I cannot say for sure that it fully supports php7, I haven't run the tests. Bugs could be hidden deeply in the code. We just haven't found them yet. Claiming to fully support php7 and getting a new issue the next day would be silly. Most of the frontend should work on php7, but I'm very suspicious.
Ivo Kurzemnieks I ran some tests. So far sniffers couldn't find anything useful. But unit tests don't work.
Fatal error: Uncaught Error: Call to undefined method Mock_CConverter_985a22a8::method() in C:\Development\zabbix\frontends\php\tests\unit\include\classes\import\converters\CConverterChainTest.php on line 53