Oh I absolutely saw those, and I did not help. I wasn't meaning to express any disappointment in the devs or with SME - I love it! Been using it since 4.03 or so and I hope it never goes away. Very grateful to all contributors.
This is my first time using this contrib, so it's unlikey I would have tested this anyway -- but your point still stands!
The bug says it's fixed -- and I don't have the same symptoms as the bug. I can't even configure PHP properly. I don't have the existing experience with PHP to get this to a state where I can even find a bug with zoneminder or the contribs for it. I can't get index.php to run. This is competency problem, not a bug report.
So to be of any help, I need to figure out what I need to put in the apache config so that index.php is run on the server instead of being sent in the browser to the client. The way SME server is setup, I guess this means it should be in an ibay so that I can manage it via the GUI -- but that's not where the contribs installed it, they put it in /usr/share/zoneminder/www/
So I need to follow the SME path of how to do it or the contribs path, and I generally follow the path of least resistance (hence "install zm... nope! Install shinobi... nope! install motion....nope!)
I'm under no illusions that me following the "easiest' paths somehow obliges anyone else to help me -- for free no less. I've already had more help from the forums over the years than I've contributed back!
Anyway this is the wrong code for the Directory stanza in the zm.conf.
AddType application/x-httpd-php .php
<FilesMatch \.(phar|php)$>
<If "-f %{SCRIPT_FILENAME}">
SetHandler "proxy:unix:/var/run/php-fpm/php74-primary.sock|fcgi://localhost"
</If>
</FilesMatch>
... because (I guess??) zoneminder doesn't work with this fastphp model?
https://stackoverflow.com/questions/14555996/no-input-file-specifiedSo that's where I'm up to. I assume motion falls over because it wants a special version of ffmpeg that it doesn't have, and as for shinobi if my woeful attempts to make php work are any guide, I have no hope with node.js and npm!
So if anyone would like to pass me a stanza to try, that's great! Either way, this problem is mine and it's nobody else's "job" to fix it.
Have a great 2022 all.