Upgrading from 1.x to 2.x
Though the installation process is very simple, we need to take some precautions as explained below.
a) First of all, MAKE A COMPLETE BACKUP of your current osDate installation, including files and database content. Physically keep these in a separate place (i.e., not on the web server that is getting upgraded!)
b) Extract the zip file and apply any available patch for the bundled version. These are periodically loaded into the osDate forum. Please read all readme.txt files which are available in the patch sets, to ensure that they are being correctly applied.
c) The upgrade process will create backup of your current tables and copy data back to new tables. This process may take a lot of time if your system has many records. Sometimes, this may invite a time-out issue in PHP. Hence, it is SUGGESTED that you manually create an Extended SQL Export of your large tables (e.g. USER, USERSNAPS, INSTANT_MESSAGES, etc.) using phpmyadmin or any other tool you are using. Just see the number of records in the table. If it is more than 300+ records, then export and keep it aside. The export file should have multiple insert statements with each statement containing the field names. Then truncate those tables for which you have made a backup. DO NOT INCLUDE _glblsettings and _payment_config and _payment_modules tables.
d) Create a new directory for osDate v2 in your server.
e) Upload all files from the unzipped location (refer to step b above). I suggest that you verify the number of files loaded to the server with the number of files in the distribution. Also, ensure the files are fully loaded. On some servers, poor FTP clients do not fully load all files. This is because of too many connections for the FTP process. I suggest you load files from one directory at a time.
f) Now load your existing config.php to osDate v2 root. If you are using any language other than English as default language, change it to 'english' in config.php before uploading to osDate v2 root directory.
for example, change the constant in config.php to:
define( 'DEFAULT_LANG', 'english' );
g) Change permissions for following files and/or directories:
/cache, /templates_c, /userimages, /uservideos, /temp,
/myconfigs, /banners 777 (or the minimum required permission for writability by PHP)
if /myconfigs/config.php is available, then that file to 777 as well (or the minimum required permission for writability by PHP)
h) Now you can run installer. It will show first page, which checks your server environment to ensure that it's compliant with osDate's requirements. If anything is missing, please correct and re-run installer.
i) The osDate installer will suggest to the "upgrade" option. Please select this. Next step will show if DB connections were OK. If all OK, then proceed with the upgrade. This will add any missing tables, table indices, and table fields that might not have been present in the previous version of osDate.
j) Please set up your mail server settings, if default shown by the installer is not correct.
You should have successfully completed upgrade.
Now you can truncate those tables for which you have made export in step (c), and import to osDate v2 using phpmyadmin or any other tool you are using. In other words, you're basically backing up the data from those tables, then installing, then truncating those tables of the installer's sample/default data, then re-adding the data from those backed-up tables, essentially to avoid PHP time-outs. Again, it's only needed if your server is prone to PHP timing out. If you run a dedicated server with a large value for the PHP time limit, this backup/restore process may be skipped.
Any user upgrading from 1.1.8 patch 03 or earlier, MUST DO FOLLOWING STEP after upgrade
to 2.0.
a) After loading to DB, you should run /admin/modifyuserstatus.php to correct the
Active Flag values.
b) Then run /admin/update_loaded_counts.php to update pictures loaded counts in the User Table.