$SQLITEDB fop2settings.db location doesn't survive upgrade

  1. 8 years ago

    I have fop2settings.db located in /drbd/spare/fop2/, and I update its location in /var/www/html/fop2/admin/fop2settings.db to $SQLITEDB="/drbd/spare/fop2/fop2settings.db";

    Whenever I upgrade fop2, my custom entry in /var/www/html/fop2/admin/fop2settings.db reverts back to default, to /usr/local/fop2/fop2settings.db";

    Is there a way to not have this happen at each upgrade?

  2. admin

    13 Jul 2016 Administrator

    Maybe you are referring to /var/www/html/fop2/admin/config.php ?

  3. Sorry, yes. I meant the line $SQLITEDB="/drbd/spare/fop2/fop2settings.db" doesn't survive an upgrade in /var/www/html/fop2/admin/config.php.
    It reverts back to /usr/local/fop2/fop2settings.db";

  4. admin

    19 Jul 2016 Administrator

    The latest fop2manager version will preserve the config.php file on web upgrades.

or Sign Up to reply!