karlma / fusionpbx

Automatically exported from code.google.com/p/fusionpbx
0 stars 0 forks source link

Fusion upgrade from 3.4 to 3.6 does not seem to alter postgres datatypes #917

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Upgrading from 3.4 to 3.6 as per Upgrade wiki page
2. Editing an extension

What is the expected output? What do you see instead?
Expecting FusionPBX to sucesfully update directory xml. Instead, it removes the 
old extension .xml's, but does not spit out new ones. Silently fails without 
any errors. (XML Handler not in use)

What version of the product are you using? On what operating system?
Fusion 3.6
FreeSWITCH 1.4.18
Centos 6.6

Please provide any additional information below.

After upgrading fusionpbx from 3.4 to 3.6 as per the Wiki guide, it all seemed 
to work OK, until a while later we tried editing the extensions. This failed, 
removing any old .xml (XML Handler is not used) but not spiting out new ones. 
No red in apache logs either.

All other XML (dialplan, etc.) did seem to work correctly.

Needed to run Upgrade -> tick Schema -> Execute again which edited some 
datatypes and now directory .xml was sucessfully spat out.

Original issue reported on code.google.com by karo...@suretec.co.uk on 15 Apr 2015 at 2:26

GoogleCodeExporter commented 9 years ago
this is normal behavior, upgrade schema is part of the upgrade process.

Original comment by nysoluti...@gmail.com on 15 Apr 2015 at 2:43

GoogleCodeExporter commented 9 years ago
nysolutions is correct what is Upgrade -> Schems -> Data Types is considered 
required for the upgrade.

Original comment by markjcrane@gmail.com on 30 Apr 2015 at 3:31