Upgrade

From FusionPBX
Revision as of 23:17, 20 December 2010 by Swilkey (talk | contribs) (Source)
Jump to: navigation, search

Source

There are two methods to upgrade FusionPBX source. 1. Menu -> System -> Upgrade (doesn't update all files) Used to update FusionPBX to the latest release.

2. Subversion (currently the preferred method to use) Login to the FusionPBX web inteface. <== note this is critical or you may not be able to do update schema afterward

Login to the console, navigate to the fusionpbx directory:

 svn update

Database

Login as a user that is a member of the super admin group. Then run Advanced -> Upgrade Schema which will ensure that your database structure is correct.

 http://domain_or_ip/core/upgrade/upgrade_schema.php

Menu

Now update the menu to the latest version.

 http://domain_or_ip/core/menu/menu_list.php

Press 'Restore Default'

SQlite Database Restore

You shouldn't need to do this, and it's probably the wrong thing to do, but if your database won't load after an upgrade...

Synopsis of what happened [to me]

1. You were not logged into the browser interface
2. You updated from svn via CLI
3. You went to login to run upgrade->Schema, but couldn't due to some changes.

Remedy

from cli:

mv /var/www/fusionpbx /var/www/fusionpbx.bak
reinstall the lastest fusionpbx... (if you are using svn checkout make sure you set the permissions correctly on the fusionpbx directory structure before proceeding to the next step)

from browser

login via the gui, complete the install... Don't log out

back to cli

cd /var/www/fusionpbx/secure
mv fusionpbx.db fusionpbx.db.new
cp /var/www/fusionpbx.bak/secure/fusionpbx.db ./
chown www-data:www-data fusionpbx.db
   (or whatever your webserver user/grp is)

from browser

go to: http://domain_or_ip/core/upgrade/upgrade_schema.php
This should fix the database.

In the future

Make sure you're logged into the browser interface before doing an upgrade...

You will need to have FusionPBX recreate all of the FreeSWITCH xml files. When you reinstalled, they were properly deleted (the database was empty at that point). Edit an extension/gatway/route/etc, and click save (you won't need to edit it).