1
irmtfan
upgrade from 2.2.4 to 2.3.2b was failed
  • 2008/12/18 19:38

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


i dont know if its a bug or not but after upgrade i lost all custom blocks. via phpmyadmin i see xoops_newblocks table is EMPTY.

i have this error in cnt-2.2.x-to-2.3.0::
INSERT INTO xoops_newblocks (bid, mid, options, name, title, side, weight, visible, func_num, block_type, c_type, isactive, dirname, func_file, show_func, edit_func, template, bcachetime, last_modified) SELECT i.instanceid, c.mid, i.options, c.name, i.title, i.side, i.weight, i.visible, 1, CASE WHEN c.show_func='b_system_custom_show' THEN 'C' ELSE 'D' END, CASE WHEN c.c_type='' THEN 'H' ELSE c.c_type END, c.isactive, c.dirname, c.func_file, c.show_func, c.edit_func, c.template, i.bcachetime, c.last_modified FROM xoops_block_instance AS i, xoops_newblocks_bak AS c WHERE i.bid = c.bid AND i.instanceid = 271
Error number: 1054
Error message: Unknown column 'c.c_type' in 'field list'


php 5.2.6

mysql 5.0.51

2
GPboarder
Re: upgrade from 2.2.3 to 2.3.2b was failed
  • 2008/12/18 19:54

  • GPboarder

  • Friend of XOOPS

  • Posts: 248

  • Since: 2006/10/6


You can check here to see if there is a solution for you.
I ended up re-creating the custom blocks and haven't had a problem since.
Optimism is the mother of disappointment.

3
ghia
Re: upgrade from 2.2.3 to 2.3.2b was failed
  • 2008/12/18 20:10

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Does your original table xoops_newblocks not have a field named c_type?

4
irmtfan
Re: upgrade from 2.2.3 to 2.3.2b was failed
  • 2008/12/19 2:48

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


by installing a fresh 2.2.3 in local create one custom block and upgrade to 2.3.2b everything goes smooth.

but my running site has more than 50 custom blocks with a +500MB database. i still work on it to see what is the problem.

to ghia: no in 2.2.3 xoops_newblocks table dont has a 'c_type' field.

5
ghia
Re: upgrade from 2.2.3 to 2.3.2b was failed
  • 2008/12/19 3:07

  • ghia

  • Community Support Member

  • Posts: 4953

  • Since: 2008/7/3 1


Then it seems the update procedure is not valid for at least the first half 2.2.x series.

You should upgrade first with the normal 2.2.x releases to a later version, eventualy to 2.2.6 and then retry the upgrade to 2.3.2b .

Maybe the upgrade will work also when changing the lines
"        CASE WHEN c.c_type='' THEN 'H' ELSE c.c_type END," .
and
"        CASE WHEN c_type='' THEN 'H' ELSE c_type END," .
in /upgrade/cnt-2.2.x-to-2.3.0/index.php to
"        'H'," .



6
irmtfan
Re: upgrade from 2.2.3 to 2.3.2b was failed
  • 2008/12/19 3:23

  • irmtfan

  • Module Developer

  • Posts: 3419

  • Since: 2003/12/7


yes the issue is exactly this. you describe it perfectly.
i can see c_type is exist in 2.2.3 final in my local.
but my running site is 2.2.4 and it doesnt have c_type.
it seems i should upgrade to the latest 2.2 first.

i edit the title of this topic because it seems this problem comes with 2.2.4

Login

Who's Online

390 user(s) are online (283 user(s) are browsing Support Forums)


Members: 0


Guests: 390


more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: Nov 30
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits