Post a Reply
1574 views

noExtenInLabel

  1. 7 years ago

    othibeault

    6 Dec 2016

    After making some tests with your latest version 2.31.06, I finaly understand why noExtenInLabel doesnt work for certain and work for others.

    If you configure your users/buttonfile in the "general" context of /usr/local/fop2/fop2.cfg and call your fop2 : http://your_server/fop2, it work fine

    BUT...

    If you configure your fop2 to be multi-tennant and configure your users/buttonfile in a custom context, exemple :

    [blablabla]
    user=blablabla1000:5555:all
    buttonfile=buttons_blablabla.cfg

    then call you fop2 with the custom context : http://your_server/fop2/?context=blablabla

    The noExtenInLabel doesnt work anymore, even if your activate it in the admin menu or in the presence.js file.

  2. admin

    7 Dec 2016 Administrator

    Where are you setting noExtenInLabel ? in the FOP2 Manager for that particular context settings?

  3. othibeault

    7 Dec 2016

    http://your_server.com/fop2/admin/pagebs.fop2settings.php

    page 2 noExtenInLabel => yes

    I dont have any option to chose the context

    I use the "enableDragTransfer" option and it work fine for default and my context.

  4. admin

    7 Dec 2016 Administrator

    Not sure how you configured your different context, but I can tell that settings are stored in the fop2settings.db sqlite file, and is context/tenant aware. My guess is that the setting is not being set correctly or the context name is not matching the one you are using. I have just tested to be sure and it works as expected if the context is correct, so I know there is no bug in FOP2 itself.

    sqlite3 /usr/local/fop2/fop2settings.db

    SELECT * FROM setup WHERE extension='SETTINGS' AND context='XXX';

    where XXX is your uppercase context name.

  5. othibeault

    7 Dec 2016

    Every context in "setup" is in uppercase, although I always enter my contexts in lowercase...

    33|SETTINGS|XXX|noExtenInLabel|false
    9|SETTINGS|GENERAL|noExtenInLabel|true

    I remember having issue with some originate before where FOP2 try to call the context in asterisk in uppercase and the originate failed because of that.

    I change it manualy and now it work : update setup set value = 'true' where context = 'XXX' and parameter = 'noExtenInLabel';

    Thanks for the sqlite thing, I see others setting I can check, like the language who is set to fr_FR in general but still "en" in my context.

or Sign Up to reply!