XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk

Subject:*
<
Name/Email:*
<
Message Icon:*
<
Select*
<
Message:*
<

 
 
 


Click the Preview to see the content in action.
Options:*
<
Confirmation Code*
< 		6 - 1 = ?  
Input the result from the expression
Maximum attempts you can try: 10
*
< 		     

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

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!
Re: Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
by Quest on 2006/3/1 13:48:00

The errors should not be there!

I would restore your backup and return your site to what it was like before you tried to update to 2.2.4.

Then go here and follow the directions. Do like it says and you shouldn't have any problems.

Xoops 2.2.3 to 2.2.4 patch Upgrade Instructions.

Remember: Do just what it says. (you will not need to upload the install folder from the package since you already have 2.2.3)

I have no idea what someone meant about your footer... I musta missed something.

Have a great Day!
Quest
Re: Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
by Wicked96SS on 2006/3/1 13:36:44

WOW!

That was quick... OUTSTANDING! Thanks a million.
Re: Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
by msdana on 2006/3/1 13:32:29

You need to manually change the footer:

Got to admin > preferences > system > meta tags and footer

There you can change the footer information.
Upgrade from 2.2.3 FINAL to 2.2.4 "issues"
by Wicked96SS on 2006/3/1 13:29:42

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!

Search

Advanced Search

Recent Posts

Who's Online

190 user(s) are online (144 user(s) are browsing Support Forums)

Members: 0

Guests: 190

more...

Donat-O-Meter

Stats
Goal: $15.00
Due Date: Jul 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $15.00
Make donations with PayPal!

Latest GitHub Commits