<![CDATA[$SQLITEDB fop2settings.db location doesn't survive upgrade]]>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?

]]>http://localhost:4567/topic/2285/sqlitedb-fop2settings.db-location-doesn-t-survive-upgradeRSS for NodeTue, 27 Oct 2026 03:12:36 GMTMon, 11 Jul 2016 15:19:54 GMT60<![CDATA[Reply to $SQLITEDB fop2settings.db location doesn't survive upgrade on Tue, 19 Jul 2016 21:20:03 GMT]]>The latest fop2manager version will preserve the config.php file on web upgrades.

]]>http://localhost:4567/post/10022http://localhost:4567/post/10022Tue, 19 Jul 2016 21:20:03 GMT<![CDATA[Reply to $SQLITEDB fop2settings.db location doesn't survive upgrade on Wed, 13 Jul 2016 19:36:32 GMT]]>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";

]]>http://localhost:4567/post/10021http://localhost:4567/post/10021Wed, 13 Jul 2016 19:36:32 GMT<![CDATA[Reply to $SQLITEDB fop2settings.db location doesn't survive upgrade on Wed, 13 Jul 2016 00:24:19 GMT]]>Maybe you are referring to /var/www/html/fop2/admin/config.php ?

]]>http://localhost:4567/post/10020http://localhost:4567/post/10020Wed, 13 Jul 2016 00:24:19 GMT