Ive been fighting with EPM not being able to edit basefiles with a couple of versions now across multiple installs, i keep reading the bug is fixed but still there. I have also tried edge on 3 boxes for the endpoint module but still get the error when i try and change and then update/rebuild the config files. Here is the error…
Whoops\Exception\ErrorException
Undefined index: user
File:/var/www/html/admin/modules/endpoint/functions.inc/functions_common.php:2108
im starting to get really depressed now about this im wasting so much time, support ticket was pretty unhelpful so running out of ideas, any suggestions appreciated
edit… i have noticed also its only when there is extensions assigned to the template, if i create a new or clone the template with no extensions assigned i do not get the error
All sites we run the paid commercial version of EPM. We generally run a mix of polycom and yealink phones. ive enabled Edge and run all updates for system and modules
FreePBX 13.0.191.1
EndPoint Manager 13.0.104.6.8
i dont know if it has anything to do with it but the common things here seem to be when a duplicate a base template to a new name and then add some custom entries to the basefile after the extensions have been assigned to the template…my only solution at present is to continue to make any changes to the original template, clone it off again, re-assign the extensions and reboot the phones, then delete the template given me trouble… very long and tedious way around it.
Nathan,
Would you mind opening an issue at issues.freepbx.org? I can certainly try to reproduce it using the steps you’ve provided. That’s definitely useful information.
Any update guys? I have logged issues, waited, give as much info as i can… im getting really desperate now, have almost a dozen sites with paid epm modules that i cannot edit basefiles without massive muck around
There was a release made to fix the issue you reported (http://issues.freepbx.org/browse/FREEPBX-14352) about a week ago. JIRA should have sent you emails for the updates. That fix is available in 13.0.105.