Installation of Open Page bug

Hello. I have a problem with after the installation of Open Page. When I hit fwconsole reload, it gave me a error, here is the error:

What version of the module do you have installed? What version of FreePBX are you using?

FreePBX version: 17.0.19.25

Open Page module version: 17.0.6

I reported the bug and I believe @theJames fixed it in version 17.0.7 but the revised version has never appeared for download.

This has been fixed in 17.0.7. Sorry about that. We had fixed it a few weeks ago and with trying to get the ISO done and out it was missed publishing this. You should be all set as its been published now.

Does it take awhile to propagate? Still showing 17.0.6.

Nope and I show its available


when I check online

I’m on IncrediblePBX and pointed at the ClearlyIP mirrors but still have 17.0.6:

image

Ahh ya. That would be the issue. We do not have a way today of automatically publishing that into incredible mirrors. I will get a internal ticket opened on this to see how we want to address it.

Great! I’m sure a lot of people on IncrediblePBX are using ClearlyIP products so it would certainly be better if the ClearlyIP and TangoPBX modules flow into the IncrediblePBX mirrors. Obviously, the Open Page 17.0.6 got there somehow.

So, on my FreePBX, do I need to in console download and install 17.0.7 by doing fwconsole ma downloadinstall openpage 17.0.7?

If your using our mirror repos then yes that would work. Or you can do a module online check from the GUI

At this time we have no way of pushing that automatically to IncrediblePBX. I have manually loaded it there.

I’m using Clearly IP mirror, not TangoPBX mirror. I’ll do that command this evening.

Thanks Tony. I hope this can be worked out.

New version 17.0.7 still won’t load on IncrediblePBX (Debian 12, Asterisk 22, FreePBX 17) @theJames

fwconsole reload --verbose
Reload Started
TypeError: FreePBX\modules\Openpage::getPageGroupSettings(): Return value must be of type array, bool returned in file /var/www                                                              /html/admin/modules/openpage/Openpage.class.php on line 320
Stack trace:
  1. TypeError->() /var/www/html/admin/modules/openpage/Openpage.class.php:320
  2. FreePBX\modules\Openpage->getPageGroupSettings() /var/www/html/admin/modules/openpage/Openpage.class.php:235
  3. FreePBX\modules\Openpage->doDialplanHook() /var/www/html/admin/libraries/BMO/DialplanHooks.class.php:109
  4. FreePBX\DialplanHooks->processHooks() /var/www/html/admin/libraries/Console/Reload.class.php:323
  5. FreePBX\Console\Command\Reload->reload() /var/www/html/admin/libraries/Console/Reload.class.php:95
  6. FreePBX\Console\Command\Reload->execute() /var/www/html/admin/libraries/Composer/vendor/symfony/console/Command/Command.ph                                                              p:312
  7. Symfony\Component\Console\Command\Command->run() /var/www/html/admin/libraries/Composer/vendor/symfony/console/Application                                                              .php:1022
  8. Symfony\Component\Console\Application->doRunCommand() /var/www/html/admin/libraries/Composer/vendor/symfony/console/Applic                                                              ation.php:314
  9. Symfony\Component\Console\Application->doRun() /var/www/html/admin/libraries/Composer/vendor/symfony/console/Application.p                                                              hp:168
 10. Symfony\Component\Console\Application->run() /var/lib/asterisk/bin/fwconsole:163

I am not seeing that on stock FreePBX 17 or TangoPPBX 17

I have that problem with FreePBX 17. Here’s the photo:

I installed your distro. Used module update to update all the modules and it took Open Page from 17.0.6 to 17.0.7. Reload worked and open page looked good until…

If you go to Applications > Paging and Intercom and then try the “Add Page Group” it bombs out.

What I’ll do is this. I’ll just hold off on having Open Page since it’s having a bug problem. I have already uninstalled the Open Page module on my FreePBX. And, I assumed you already reported the issue to Clearly IP or whoever’s in charge of taking care the bug issues.