Upgrading (Page 1 of 2)

hey,

i am trying to update FA 2.4.4 to 2.4.5,

i am using custom theme and let me know can we update files SIDE by SIDE code or another way to do this instead of replacing files?

Regards

I have seen these steps mentioned in a few posts.

Why do you say to upgrade to Ver 2.3.26 (last version of FA2.3) before moving to FA2.4.x?
Does this last version save things differently or the upgrade?

I ask because In Theory any FA2.3 version should have the same DB structure

Tom

I was able to import it ok from 2.3.16 to 2.4.6 using the steps you provided (skipping the fresh install of 2.3.26)

Well so far it looks good

Tom

Verify with the stock sql/en_US-new.sql for any schema changes and unused tables and field orders.

@ tom - I guess if you do the missiby step.  It will fix the db issue.

I hope that FA2.4 correctly updates the DB...

Tom

After a detailed look at my database I have found that he difference between my tables (2.3.16) and 2.3.26 are that 3 fields are out of order.
Seems they were added to the end not in the middle.

There are also many defaults that are different.

I am wondering if I could export my DATA only and import into the 2.3.26 tables (truncating the tables before inserting)

It seems that could work, unless I am missing anything obvious

Thoughts?
(Yes everything is backed up so total failure is not a real problem)

Is this statement correct?

7. Now when you login as administrator, FA will ask you to update your database. 

I loaded the demo data from 2.3.26 into my 2.4.6 install and FA does not ask me to update my DB.

I can go do the update, but it never asks me.
What triggers this question from the code?

Is there something missing from mt DB?

Tom

When I was comparing my database to the FA2.4 I found a number of fields had different default values and such, so I felt it might be better if I make my DB conform to the exact same structures of demo data.

So here is what I ended up doing:
1. Exported my data with phpMyAdmin keeping Just the Data and truncating the tables (as opposed to dropping them)
2. I created a fresh DB and imported the 2.3.26 demo data with phpMyAdmin (my system was FA2.3.16)
3. I imported my Data Only with phpMyAdmin
4. I then logged into an admin account of my DB and did a Software Update

All appears to be well.

The same steps could work for an FA2.4 db clean up as well

Tom

Experience similar to Iffig - updating from 2.3.26 to 2.4.8 on Windows 10 Wamp server. Followed the steps outlined by kvvaradha. When I log as administrator in the company "0" and do a software upgrade, the process fails. I get the following error messages:

30:Duplicate column name 'tax_shipping'
36:Duplicate key name 'stkcode'
37:Duplicate key name 'itemcode'
39:Duplicate column name 'bank_account'
41:Duplicate column name 'tax_included'
45:Duplicate column name 'bank_charge_act'
48:Duplicate column name 'transaction_days'
50:Duplicate column name 'prep_amount'
51:Duplicate column name 'alloc'
53:Duplicate column name 'prep_amount'
54:Duplicate column name 'alloc'
59:Duplicate column name 'invoiced'
68:Duplicate column name 'prep_amount'
79:Duplicate column name 'no_purchase'
80:Duplicate column name 'dflt_no_purchase'
83:Duplicate column name 'rate'
86:Duplicate column name 'save_report_selections'
87:Duplicate column name 'use_date_picker'
88:Duplicate column name 'def_print_destination'
89:Duplicate column name 'def_print_orientation'
143:Duplicate column name 'dimension_id'
144:Duplicate column name 'dimension2_id'
151:Duplicate column name 'usage'
152:Duplicate column name 'memo'
155:Duplicate column name 'person_id'
159:Duplicate column name 'person_id'
199:Duplicate column name 'reg_type'
255:Can't DROP 'branch_code'; check that column/key exists
256:Can't DROP 'SupplierID_2'; check that column/key exists
257:Can't DROP 'type'; check that column/key exists
260:Duplicate column name 'fixed_asset'
273:Duplicate column name 'depreciation_method'
274:Duplicate column name 'depreciation_rate'
275:Duplicate column name 'depreciation_factor'
276:Duplicate column name 'depreciation_start'
277:Duplicate column name 'depreciation_date'
278:Duplicate column name 'fa_class_id'
279:Unknown column 'actual_cost' in '0_stock_master'
288:Duplicate column name 'unit_cost'
289:Unknown column 'std_cost' in '0_wo_requirements'
291:Can't DROP 'last_cost'; check that column/key exists
294:Unknown column 'assembly_account' in '0_stock_master'
295:Unknown column 'dflt_assembly_act' in '0_stock_category'
308:Unknown column 'counter' in '0_budget_trans'

Lots of errors to fix, but I don't know where to start. Please give me some ideas.

kvvaradha, I took the approach mentioned in your last paragraph, editing the alter2.4.sql file. I opened it in a text editor and made each of the lines mentioned in the log file a comment by inserting '* rjp   '  at the beginning. Thus line 30 became

# rjp  ALTER TABLE `0_tax_group_items` ADD COLUMN `tax_shipping` tinyint(1) NOT NULL default '0' AFTER `rate`;

Similarly, lines 36 and 37 became

# rjp  ALTER TABLE `0_sales_order_details` ADD KEY `stkcode` (`stk_code`);
# rjp  ALTER TABLE `0_purch_order_details` ADD KEY `itemcode` (`item_code`);

This modification allowed me to update the software without errors