Blank Settings Page

Hello,

I recently installer fop2 and fop2manager Version: 2.30.06 - great product, however I'm having the following problems.

A.- when I click on the settings page i get a blank screen
B.- I edited the .js page to display a single line but the console still shows 2 lines (I think this is because in this version the buttons are driven by the settings page instead )

Any ideas on how fix these?

I'm running plain asterisk 13 core on top of ubuntu 14 LTS


Thanks for you help.

Comments

  • you must change ownership of the /usr/local/fop2/fop2settings.db to be the user of your web server. The make script will attempt to use the "asterisk" user, but in ubuntu most probably your web server is running with another user, like www-data or similar. So, find out the user your web server is running as, and chown the file, example:

    chown www-data.www-data /usr/local/fop2/fop2settings.db

    With correct ownership, then you will be able to edit the settings and configure the showLines to be 1 in the fop2 manager directly.

    Best regards,
  • Hi

    I changed the permissions as you indicated but still getting a blank screen. I restarted the server to make sure but still nothing

    Thanks
  • Check your web server error log file. Perhaps you are missing the php-sqlite module.
  • That was it - Thank you.

    Now i have another issue, the users can't see any of the buttons. I can see them in fop2admin but they are not been displayed to the user.

    If use the bottons.cfg it works fine and the user can see the buttons but then users setup in the DB can't login.

    I have tried the following:

    1.- Removing the user and recreating it
    2.- Removing all the buttons and groups and re-adding them

    Thank for your help.
  • How did you remove buttons? It is not possible to remove buttons via the FOP2 Manager, that is why I am asking. In any case, whatever you see or not is a result of the configuration. When using the FOP2 Manager, you must have in fop2.cfg the line

    #exec autoconfig-users.sh

    And nothing else, no user=xx line, no buttonfile=xx line (for manual configurations), as config will overlap and it won't work as you might expect.

    In order to "see" the configuration that comes from the FOP2 Manager, you can run in the command line those scripts:

    /usr/local/fop2/autoconfig-buttons.sh

    And inspect the output. If you see valid configuration for buttons, then you are in the right direction. If you see blank or errors, those will give you a clue of what the problem might be.

    Finally, a common error for new users is try to create permission or groups in the FOP2 Manager without actually knowing what are there for. My advise in that case is to NOT create any groups or permissions. Edit your User and uncheck any groups it might have assigned. Set permissions in the User tab to "all". Restart FOP2 and try from there. That is the most "open" config possible, with no restrictions. *anything* you can do from the Manager after that is for RESTRICTING views or permissions, that means, REMOVING buttons from view, or REMOVING the possibility to perform actions.

    So, for starters, leave it all open/unrestricted. See if it works or work your way until it works. Then think about changing permissions, or limiting views with groups.

    Best regards,

  • Here is a portion of what I get when I run autoconfig-buttons.sh

    I removed all the groups as you suggested - now when I login as a user I see the gray bar where the buttons supposed to be but a label that says No Buttons.

    Thanks
  • My initial guess would be to say that fop2.cfg was modified and it is not doing the #exec correctly. My second guess is that your users are still having groups assigned, that are not populated or emtpy, leading to a display with no buttons.

    What is the output from:

    cat /etc/sysconfig/fop2

    grep exec /usr/local/fop2/fop2.cfg

    grep user /usr/local/fop2/fop2.cfg

    ?

    My recommendation, if you modified fop2.cfg, is to restore the original one and change ONLY the manager_user and manager_secret to match your manager.conf settings and let all the rest intact.
Sign In or Register to comment.