Dear, on a server (stand alone, ispconfig based), for several reason, we have the database schema of an old versione (3.1.2). With the application file of the latest version (3.1.13p1). We would like fix that. Our first idea was to set the ISPCONFIG version file here: /usr/local/ispconfig/server/lib/config.inc.php define('ISPC_APP_VERSION', '3.1.13p1'); back to 3.1.2 version, and then re-launch the ispconfig_update.sh script. This could be a good way to do that? There is downside or better way to procede? ty
That should be ok, there are no downsides. But you can also force an update without editing the version number like this: Code: cd /tmp wget http://www.ispconfig.org/downloads/ISPConfig-3.1.13p1.tar.gz tar xvfz ISPConfig-3.1.13p1.tar.gz cd ispconfig3_install/install php -q update.php The ispconfig version number does not matter for the database schema upgrade, what matters is the dbversion field of the server table, but when you restored an older database, then the dbversion field must contain the old database version information which means the updater will perform a database schema upgrade.
