ZoneMinder Forums

Hi all!
Ubuntu Server 20.04 LTS with latest updates.

After upgrading ZM from 1.37.13 to 1.37.15_20220504130434-focal_amd64.deb OPT_USE_API turned itself off.
Any attempts to turn it back on silently end up with OPT_USE_API=0.
The only solution I've found was to downgrade to 1.37.14_20220502095655-focal for a minute just to turn it back on. Then it stays ON until I change anything in /zm/index.php?view=options&tab=system with saving. The parameter I change is saved successfully, but OPT_USE_API turns OFF and no way to change it to ON without doing a "downgrade to 1.37.14 -> turn on OPT_USE_API -> upgrade to 1.37.15" procedure.

Don't think it's normal. Maybe changing this setting in DB Config table would work, I didn't check.
e. g.

I experienced this as well. I compile ZM from source for Puppy Linux Bionic64, Fossapup64 and Void Linux and variants.

Suddenly zmNinja which worked great on the desktop communicating with ZM on 1.37.14 did not on 1.37.15

I reset and renewed the server config on zmNinja and after clicking on save twice (?) the API srang to life and zmNinja began to stream.

This though now appears to be related to what you are describing. But with an odd twist.

Fixed in 1.37.15~20220506114546-focal

UPD: problem persists in 1.37.15~20220506114546-focal.
So far I'm using a workaround directly enabling OPT_USE_API in DB, works without restarting ZM

Sigh. My apologies. I did fix it in the timeframe I thought.. however I never pushed it, and so latest packages did not have it.

Building new packages now.

Confirm it's woking in 1.37.15_20220507193920-focal
But it didn't in the intermediate 1.37.15_20220507113926-focal