FreePBX GUI is 100% open source. Always has been and always will be. We do big fixes and features in FreePBX every single day. We do new major releases close to yearly.
Zend gets included in the FreePBX Distro not in FreePBX GUI. The FreePBX Distro is a full ISO that includes both open source FreePBX GUI along with optional commercial modules you can choose if you want to license. Nothing forces you to use the FreePBX Distro you can download FreePBX GUI and install like you could the last 14 years. Or you can install our easy to use ISO.
In the end people need to put food on the table for their family and support the economy. They can’t do this if everything is 100% free. Their is a reason why FreePBX still exist when your Elatoxs and Trixbox of the world have all folded. You need a healthy mix of revenue to keep supporting a project of this size.
You are talking around the issue.
I didn’t say I didn’t want to support developers. I’m a developer.
I’ll say it very clearly right now.
I’ve working in engineering for over 35 years now.
EVERY SINGLE TIME there is a project that involves licensing software, it is a DISASTER. It breaks for the user. It’s a support nightmare for the company. It’s ALL bad. There is nothing good from it. It is wrong, it is evil. Stop doing that.
15 years ago I swore I would never have anything to do with anything that involved licensing. I got rid of every bit of software that works that way (see EA games). Even hardware like bluray players went on a burn pile in my back yard.
Now, somehow, this got by me. And I’ve wasted 3 days of my life trying to get this FreePBX installation to work, and I have other things I need to be doing.
Your issues in your other thread seem to come from the fact that you cross version restored. You spun up a new 14 machine and restored an old version on top of that.
Furthermore you need to activate (not purchase! Activation is free) in the distro to have the ability to select https certificates for apache. You can do this manually though.
I cant see commercial creep here because the ability to assign certificates to apache always required activation (which is free) and again you can do it yourself manually if you so desire, through certbot
To modify apache as the asterisk user we need to use a tools called incron. This is a security measure. If we modified everything root can modify as the asterisk user your system would be insecure. Because of the incron requirement it requires sysadmin