Module updating past licensed version

[penguinpbx (C. Maj)]

@FreerPBXer

I was NOT switching mirrors.

Apologies for the confusion – it looked like your reply Licensed module access blocked without active maintenance? - #10 by FreerPBXer suggested otherwise on the mirror topic:

@FreerPBXer

The only module we have ever deployed outside the Sangoma stack is for

…[something clearly not in the official Sangoma FreePBX mirror.]

@FreerPBXer

Your code allowed the modules to be upgraded after support expired, and that happened recently.

Yeeting some log output into our pastebin could really help e.g. please run fwconsole ma list on the affected system(s).

Also to help clarify, would you mind sharing/confirming:

• You were running some commercial modules that you had not renewed maintenance on, but you were content with the older versions ?
• And when you ran updates last year, for example, those modules stayed at those previous versions ?
• Then this year, with no additional purchase or other major change, such as moving from FreePBX 16 to 17, you started getting automatic updates for those older commercial modules to the latest versions that you were not entitled to ?

Such experience would run counter to the current expected behaviour following the updates over the past few months as outlined in the previously mentioned blog post, and it would also conflict with established procedure from the past ten years as described here (and linked in that other topic):

Issue Tracker on the support board not working

Yes the software license is 25 years but you get support and upgrades for the first year included and after that you have to renew maint on the modules. That has always been the case but only last year did it stop you from upgrading modules without the maint contract. You can renew the maint from inside FreePBX module admin or in the portal under the reports tab.