upgrade 1.1.0 -> 1.4.0

[DiabloRex]

Then upgrading from 1.1.0 to 1.4.0 I get this two errors, after the upgrade.php script is done

Warning: Supplied argument is not a valid MySQL result resource in /usr/local/www/html/everspoon/forum/Sources/Load.php on line 142

Warning: Supplied argument is not a valid MySQL result resource in /usr/local/www/html/everspoon/forum/index.php on line 76


----------------------------------------------------------------------


It might be another problem. I have run the upgrade.php several times now, and each time it says the same thing (mostly table inserted succesfully) However shouldnt it, after the first time, say "error - dublicate table" ? Its like the table is inserted but never saved or updated.


Also I get this error while upgrading

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist



It does however say that my upgrade is successful

[David]

Have you checked via phpMyAdmin to see if that table actually exists?

[DiabloRex]

no its not there, shouldnt the upgrade script take care of that anyway?

If not, when what data/fields whatever should it contain (If I have to make it manually)

[David]

I wonder if any of the new tables were made?  Does the user you are using have permission to make new tables?  How many tables do you have right now?

[DiabloRex]

Yes the user have permission and some of the new tables was indeed created (the calendar_holiday table) Since I havnt had the calendar installed, I know this one is made

I currently have 25 tables, however one of them might belong to the age old original port of the add more smileys mod.


--------------------------------------------------------------------



This is the upgrade screen and its errors. The maximum about 32 keys is a new one. (Some of the "Data inserted succesfully" have been edited out)

YaBB SE SQL Upgrade Utility

Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Error: MySQL said:

Duplicate column name 'readBy'

Data inserted successfully!

Data inserted successfully!


Data inserted successfully!

Data inserted successfully!

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Data inserted successfully!





Data inserted successfully!

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Data inserted successfully!





Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Data inserted successfully!

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Error: MySQL said:

Table 'everspoon.everspoon_log_activity' doesn't exist

Data inserted successfully!





Data inserted successfully!
Data inserted successfully!

Data inserted successfully!

Error: MySQL said:

Too many keys specified. Max 32 keys allowed

Data inserted successfully!


Data inserted successfully!

Upgrade of SQL is ok.


If there is an error message indicating a duplicate column or an table that already exists, you can ignore those errors.

[DiabloRex]

Any ideas why the table isnt created? I looked in the thread "Version 1.4.0 have been released" where another had the same problems with Subs.php where running upgrade.php fixed his problems.

However I have run upgrade.php, several times actually.

[ioa]

I have the same error.

When I run the upgrade I got the error ...log_activity' doesn't exist

And after the ugly warning messages.

I install the log_activity table manually. Here is the SQL to run:

CREATE TABLE yourPreFix_log_activity (
  month tinyint(4) NOT NULL default '0',
  day tinyint(4) NOT NULL default '0',
  year mediumint(9) NOT NULL default '0',
  hits int(11) NOT NULL default '0',
  topics int(11) NOT NULL default '0',
  posts int(11) NOT NULL default '0',
  registers int(11) NOT NULL default '0',
  mostOn int(11) NOT NULL default '0'
) TYPE=MyISAM;

So when I run upgrade.php again it runs ok but I still have the warnig errors:

mysql_num_rows(): supplied argument is not a valid MySQL result resource in myhome/Sources/Load.php on line 142

Warning: mysql_fetch_array(): supplied argument is not a valid MySQL result resource in myhome/foro/index.php on line 76

Kind of buggy upgrade script.

 

[DiabloRex]

Good to know I am not alone

Do you still get those error messages after you have created the table yourself, and run the upgrade.php script? (the errors in Load.php and Index.php)

[ioa]

Yes I did but guess what: I just fix it:

Al you have to do is this:
Run this SQL:

ALTER TABLE yourPreFix_members ADD MSN TINYTEXT;
ALTER TABLE yourPreFix_members ADD lngfile SMALLINT UNSIGNED;

That will fix the error on Load.php and Indes.php.

Notice that more error could be in other pages. Hope the developers of this YabbSE take note. I'll keep fixing them and posting in here as much as I can but I have not too much time.

Hope this help.
Regards

[DiabloRex]

Have you tried to post a message? IIRC I got an error in Subs.php.

[ioa]

No, I just post a msg and was fine.

Let me know your error message so I can have an idea.

[ioa]

I got another erro when I tried to post a message.
The message get posted but you still get an error.

Soluction:
Run this:
ALTER TABLE yourPrefix_members ADD notifyOnce TINYINT UNSIGNED;

Notice, I'm not sure about the data type of notifyOnce, I asume it is tinyint becase of the way the use it.

I hope the they review the entire upgrading script. It is not worthy to upgrade if you will have too many ugly problems.

[ioa]

Here is a precedure that might work.

After having so many problems I decided to do this.

1 - Backup your 1.1.0 files using PHPMyAdmin. Notice, Only backup the data. Do not backup the structure.

2 - Run the upgrade script.
3 - From the full version of 1.4, get the file yase140.sql.
4 - Go to notepad or any editor and replace {$db_prefix} with your table prefix name.
5 - Delete or your 1.1.0 tables on your datebase. You already have a backup.
6 - Run the yase140.sql so it will instal all of the tables again.
7- Very importan: Run this sql script:
delete from  your_table_prefixbanned;
delete from your_table_prefixboards;
delete from your_table_prefixcalendar_holiday;
delete from your_table_prefixcategories;
delete from your_table_prefixcensor;
delete from your_table_prefixinstant_messages;
delete from your_table_prefixlog_activity;
delete from your_table_prefixlog_banned;
delete from your_table_prefixlog_boards;
delete from your_table_prefixlog_clicks;
delete from your_table_prefixlog_errors;
delete from your_table_prefixlog_floodcontrol;
delete from your_table_prefixlog_karma;
delete from your_table_prefixlog_mark_read;
delete from your_table_prefixlog_online;
delete from your_table_prefixlog_topics;
delete from your_table_prefixmembergroups;
delete from your_table_prefixmembers;
delete from your_table_prefixmessages;
delete from your_table_prefixpolls;
delete from your_table_prefixreserved_names;
delete from your_table_prefixsettings;
delete from your_table_prefixtopics;

IT will delete any default settings that the forum has when it install for the first time. You don't need them because you already have your settings in the backup

8 - Final. Run your backup. Your forum will go back to live.

Its sound a little bit complicated but it is not. Most of the error after the upgrade are because de tables are not properly updated on the update script.

I did it and so far it works.
Notice, this is just a solution that I haven't proof but I think It work. I have not responsabilities for any lost of data and not liability. Do it at your on risk.

Regards.

[Jaxom]

Having spent the best part of a day trying to get the various tactics above to work (the back up and restore tables failed because my mysql fields weren't in the same order as a 'clean' 1.4 install in several cases).

I did eventually find the solution. You can't upgrade direct from 1.1 to 1.4. Half the sql upgrade entries and yabbimage files are not in the 1.4 upgrade. Instead, first run the 1.3 upgrade, specifically the upgrade.php and copy up the yabbimages - then run the 1.4 upgrade as instructed. This worked perfectly first time on my second, code identical yabbse board.

If any of the team who package the upgrade want to modify the install instructions to tell you to do this (easier than trying to combine the 1.3 and 1.4 installers together) it will probably save a lot of people grief - everyone expects upgrades to be cumulative these days, I did...

[jyagmin]

I'm having the same delightful problem...    Only I'm on 1.0.0 and I tried the "upgrade to 1.3 as an intermediate step" and it didn't fix anything...and since there appears to be no upgrade files from 1.0 to 1.1, I'm screwed