FYI, The history was literally me arguing with @dicko and someone else (who also ran cloud instances of FreePBX) in a thread here on community for a couple of days until I actually did the thing they/he was proposing
Additionally in FreePBX 2.5 or so there was also a cron manager of sorts. Which was abandoned at some point which is why the crontab looked horrendous after a couple of years. The Jobs class was there to solve that issue.
This is all too familiar with the recent sks gpg key servers issue as well. FYI if you didn’t know Jason Parker was the last one working on GPG issues (Publically) in FreePBX for Sangoma and he was “terminated” from Sangoma in October 2021 (see: Jason Parker - Jeltz | LinkedIn). Mergers and Acquisitions can be a b*tch.
Checking my emails now I see this message started appearing for me today straight after the 06:35 UT automatic module Update email. It appears every 15 minutes.
So whatever is causing this came via the update. I just did a manual module update but there is no change.
I have not read through this long thread - is there a fix for this?
Same problem as documented in this thread. Basically FreePBX pushed an untested and broken module to your PBX. You will need to either wait for a fix, presumably next Friday, or manually revert the module. It is not a real killer but an incredibly incompetent release
It might be a little more complicated than that, because the previous module didn’t inject a crontab and the broken one might not remove it on being ‘replaced’.
That would take some regression testing, ask FreePBX but they are currently not exactly A+ on that right now. Why not suck it and see. let us know how it worked out.
I am on 15: Upgrading module ‘userman’ from 15.0.63 to 15.0.65
The FreePBX docs say ‘Starting in version 12 you can downgrade module versions from Modue Admin.’ but my V15 Module Admin does not show a ‘Previous’ option.