1
Wicked96SS
Re: Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
  • 2006/3/1 14:48

  • Wicked96SS

  • Just popping in

  • Posts: 5

  • Since: 2005/12/19


Well, I put it back to 2.2.3, and did the upgrade again, and like the first time, there were no errors, but the footer of the Administration page still said version 2.2.3, which was my original "concearn"... just changed the footer, and all is the way it was before I reverted and re-upgraded... Seems that it has worked, just needed to upgrade the footer myself to reflect 2.2.4 change.

Thanks again!



2
Wicked96SS
Re: Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
  • 2006/3/1 13:36

  • Wicked96SS

  • Just popping in

  • Posts: 5

  • Since: 2005/12/19


WOW!

That was quick... OUTSTANDING! Thanks a million.



3
Wicked96SS
Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
  • 2006/3/1 13:29

  • Wicked96SS

  • Just popping in

  • Posts: 5

  • Since: 2005/12/19


Hello! I have been using XOOP now for a while, and like it quite a bit. But, have a rather simple question...

I have upgraded from 2.2.3 FINAL to 2.2.4 (warning from provider to keep all of our stuff updated, or get booted off the server... nice). Here is what I did:

1. Backed everything up.
2. Unzipped over and verified the new files are in the same place.
3. Ran the xoopsupdate.php and it succeeded.
4. Went into the moudule menu in the Admin page and manually hit "update" for every module and that all succeeded.

If I try to "re-update" I get warning messages that fields in the database already exist, but then it reports the update was successful. Here are the messages I get:

Quote:

...
Adding user profile fields...
ERROR: Could not insert field umode into the database. Duplicate column name 'umode'
ERROR: Could not insert field uorder into the database. Duplicate column name 'uorder'
ERROR: Could not insert field notify_method into the database. Duplicate column name 'notify_method'
ERROR: Could not insert field notify_mode into the database. Duplicate column name 'notify_mode'
ERROR: Could not insert field user_regdate into the database. Duplicate column name 'user_regdate'
ERROR: Could not insert field posts into the database. Duplicate column name 'posts'
ERROR: Could not insert field attachsig into the database. Duplicate column name 'attachsig'
ERROR: Could not insert field timezone_offset into the database. Duplicate column name 'timezone_offset'
ERROR: Could not insert field user_mailok into the database. Duplicate column name 'user_mailok'
ERROR: Could not insert field theme into the database. Duplicate column name 'theme'
ERROR: Could not insert field actkey into the database. Duplicate column name 'actkey'
ERROR: Could not insert field last_login into the database. Duplicate column name 'last_login'
xoops_module_pre_update_system executed successfully.

...


And

Quote:

Adding user profile fields...
ERROR: Could not insert field umode into the database. Duplicate column name 'umode'
ERROR: Could not insert field uorder into the database. Duplicate column name 'uorder'
ERROR: Could not insert field notify_method into the database. Duplicate column name 'notify_method'
ERROR: Could not insert field notify_mode into the database. Duplicate column name 'notify_mode'
ERROR: Could not insert field user_regdate into the database. Duplicate column name 'user_regdate'
ERROR: Could not insert field posts into the database. Duplicate column name 'posts'
ERROR: Could not insert field attachsig into the database. Duplicate column name 'attachsig'
ERROR: Could not insert field timezone_offset into the database. Duplicate column name 'timezone_offset'
ERROR: Could not insert field user_mailok into the database. Duplicate column name 'user_mailok'
ERROR: Could not insert field theme into the database. Duplicate column name 'theme'
ERROR: Could not insert field actkey into the database. Duplicate column name 'actkey'
ERROR: Could not insert field last_login into the database. Duplicate column name 'last_login'
Updating user profile field default value...


I am assuming that this just means it is trying to add a field to the database that it has already added in the past. First time I got no errors.

Here is the "issue" (or manybe a non-issue), since I have done that the version number on the Admin page still read 2.2.3 FINAL and not 2.2.4... does that mean that something went wrong? Should I take a Paxil and relax?

I have confirmed it is using the "new" files... and everything seems to work...

Any help would be greatful.

Thanks!



4
Wicked96SS
Re: sqmail & 2.2.3
  • 2005/12/21 22:21

  • Wicked96SS

  • Just popping in

  • Posts: 5

  • Since: 2005/12/19


After and upgrade to a newer version of PHP, I couldn't even view emails after that, and this problem never got solved, I switched over to Tropical mail for XOOP, and like it much better, although you have to log in every time (might be a setting for this, just installed it, still playing with it). Anyhow, it works.



5
Wicked96SS
Re: sqmail & 2.2.3
  • 2005/12/19 0:46

  • Wicked96SS

  • Just popping in

  • Posts: 5

  • Since: 2005/12/19


I am new to Xoops, but am having the same problem that Northern is having, and cannot find a way to get around it.

Anybody have any suggestions?




TopTop



Login

Who's Online

133 user(s) are online (94 user(s) are browsing Support Forums)


Members: 0


Guests: 133


more...

Donat-O-Meter

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

Latest GitHub Commits