We have gotten our arms around fop2 and the chrome fop2 extension at this point. We update to 2.28 earlier this week as well.
We looked into fop2 manager a bit today and have some questions/issues.

• Our environment can be best described as plain, vanilla asterisk, as there is no freePBX involved.
• In our demo environment, we have about 4 users, 10 extensions, 2 queues, 4 Ringgroups, etc setup. probably around 25 buttons. configured into the fop2 and button cfg files.
• When we go into the fop2 manager,we see traces of the users and buttons we created in the cfg files, but by no means many of them.
• If we create a user in the manager interface, we see if created, but we can't log in using that info, and it is not reflected back in our cfg files -- it is presumably resident in the mysql tables.

How do the two environments (flat cfg files and the fop2manager database) inter-relate ? Does it require a freePBX based install ?
If so, then OK, we will stop here with the manager and just focus on fop2. Otherwise, can you give us some hints as to how to diagnose the issue(s).

last question for this round:
I went into plugins directory and clicked an Install button for Busy Counter. I see a fast-moving red box in the lower right that says "Error extracting plugin archive(2)" almost immediately. This occurs on any and all of them.

Please advise next steps when convenient.
Thanks,
Ron

Hello again.
Maybe I have missed the purpose of the fop2 manager. When I review functions-custom.php I see code attempting to decipher extensions, trunks, queues, etc from asterisk conf files. I would *never* have expected or anticipated the fop2 manager to decipher extensions, and queues, etc from my asterisk conf files. I wrote my own php code to generate the button.cfg file(s) for this very purpose. We generate our own fop2 configuration from our asterisk conf files.

I was just questioning whether the fop2 manager should be able to add/edit the button cfg files that we have already created. I was anticipating that the fop2 manager should be able to show the button objects that already exist.

Similarly, when I create a user in the fop2 manager, I am anticipating it is a fop2 user, that logs into fop2. I wouldn't anticipate have to reload asterisk for that to happen, since it has nothing to do with asterisk -- in least the way I am thinking now.

Based on your responses, I am beginning to realize that possibly the intent of the fop2 manager is not so much to manage the display objects in fop2, but to manage (i.e. create/modify/delete) the objects in asterisk ?

MAYBE what I should do is take the php script that I use to generate my own button files and fit it into the functions-custom.php.

Thanks for the tip on the plugins chmod. that is certainly easy enough. Should have thought of that myself.

Hello again.
Maybe I have missed the purpose of the fop2 manager. When I review functions-custom.php I see code attempting to decipher extensions, trunks, queues, etc from asterisk conf files. I would *never* have expected or anticipated the fop2 manager to decipher extensions, and queues, etc from my asterisk conf files. I wrote my own php code to generate the button.cfg file(s) for this very purpose. We generate our own fop2 configuration from our asterisk conf files.

I was just questioning whether the fop2 manager should be able to add/edit the button cfg files that we have already created. I was anticipating that the fop2 manager should be able to show the button objects that already exist.

Similarly, when I create a user in the fop2 manager, I am anticipating it is a fop2 user, that logs into fop2. I wouldn't anticipate have to reload asterisk for that to happen, since it has nothing to do with asterisk -- in least the way I am thinking now.

Based on your responses, I am beginning to realize that possibly the intent of the fop2 manager is not so much to manage the display objects in fop2, but to manage (i.e. create/modify/delete) the objects in asterisk ?

MAYBE what I should do is take the php script that I use to generate my own button files and fit it into the functions-custom.php.

Thanks for the tip on the plugins chmod. that is certainly easy enough. Should have thought of that myself.

apologies for the duplication