Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0
Select messages from # through # Forum FAQ
[/[Print]\]

Nuke-Evolution.com -> 2.0.x Communiques
#1: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Technocrat, Location: Hell PostPosted: Tue Jan 30, 2007 4:14 pm
    —
We have decided that Evo v2.0.x has become stable enough for us to set a depreciation date for Evo v1.0.1.   This date currently is February 28, 2007.  Unless something changes our minds this date is set and is a necessary evil for moving forward.

There is also no longer a reason anyone should be using v2.0.0 RC1, v2.0.0 RC2, or v2.0.0.  These versions are now badly out of date.  You should not be using them.  So they will also be depreciated on February 28th.

This means that support will no longer be given.  The support forums will be closed.  We will also be removing the download for v1.0.1.

As always if you would like manual change files for any files in particular feel free to ask.  I will try to make them up for you.
#2: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: BotX,  PostPosted: Tue Jan 30, 2007 4:21 pm
    —
Tnx  for the info Techno Smile

I'm using Evo-2.0.1 and I've installed lots of mods from Evo-Mods.com  and my site is currently in testing progress...

i had some theme issues and now I'd like to USE Evo-2.0.2Smile

I'll Re-install the mods again(may be takes a day that is nothing Very Happy )

I always like *NEW* things... so I'm gonna use Evo-2.0.2  Wink


Thanks  Very Happy
#3: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Ice5192, Location: Va, USA PostPosted: Wed Jan 31, 2007 10:30 pm
    —
cool here we come v3 lol
#4: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Thaitanium, Location: Your sisters house PostPosted: Fri Feb 09, 2007 10:21 am
    —
This will make the recent topics more cleaner  Razz
#5: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: PeTeam, Location: Teh Pasdaran PostPosted: Wed Feb 21, 2007 12:06 pm
    —
cool  ! ill inform persian users !
#6: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: SixString,  PostPosted: Tue Mar 27, 2007 11:36 am
    —
Wow! I'm so far behind it's unreal Mad

Anything I need to know to upgrade from the RC2 version? Embarassed

Or should I just upload all the files from the download?

The only mod I've added is SQuery, should I remove it first?

Hope thats not too many questions...

BTW, by the looks of it, you guys are doing a great job with this and thanks for all of your hard work...

Six Cool
#7: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Technocrat, Location: Hell PostPosted: Tue Mar 27, 2007 11:43 am
    —
Run this SQL, it will take you to 2.0.1 then follow the steps from there.

Code:
ALTER TABLE `nuke_evo_userinfo` CHANGE `position` `position` INT(10) NOT NULL;
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
ALTER TABLE `nuke_blocks` CHANGE `view` `view` VARCHAR( 50 ) NOT NULL DEFAULT '0';
UPDATE `nuke_blocks` SET `view` = '4' WHERE `view` = '2';
ALTER TABLE `nuke_users` CHANGE `bio` `bio` TINYTEXT NULL;
ALTER TABLE `nuke_users` CHANGE `ublock` `ublock` TINYTEXT NULL;
INSERT INTO `nuke_bbconfig` VALUES ('image_resize_height', '400');
INSERT INTO `nuke_evolution` VALUES ('img_height', '300');
UPDATE `nuke_counter` SET `type` = 'os' WHERE `var` = 'Linspire';
ALTER TABLE `nuke_bbgroups` ADD `group_count` INT( 4 ) UNSIGNED NOT NULL DEFAULT '99999999', ADD `group_count_max` INT( 4 ) UNSIGNED NOT NULL DEFAULT '99999999', ADD `group_count_enable` SMALLINT( 2 ) UNSIGNED NOT NULL DEFAULT '0';
UPDATE `nuke_evolution` SET `evo_value` = '0' WHERE `evo_field` = 'collapsetype';
ALTER TABLE `nuke_bbsearch_wordlist` CHANGE `word_text` `word_text` varchar(255) binary NOT NULL DEFAULT '';
#8: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: SixString,  PostPosted: Tue Mar 27, 2007 2:46 pm
    —
Awesome! Upgraded without an issue.

Thanks again Technocrat Very Happy
#9: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: _Ascension_,  PostPosted: Tue Apr 10, 2007 7:00 pm
    —
wow umm I;m useing 1.0.1 anything special I need to get updated to 2.0.3? I cant find any other version to update too and the update files included in 2.0.3 dont say anything about 1.0.1
#10: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Tue Apr 10, 2007 7:06 pm
    —
Technocrat wrote (View Post):
Run this SQL, it will take you to 2.0.1 then follow the steps from there.

Code:
ALTER TABLE `nuke_evo_userinfo` CHANGE `position` `position` INT(10) NOT NULL;
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
ALTER TABLE `nuke_blocks` CHANGE `view` `view` VARCHAR( 50 ) NOT NULL DEFAULT '0';
UPDATE `nuke_blocks` SET `view` = '4' WHERE `view` = '2';
ALTER TABLE `nuke_users` CHANGE `bio` `bio` TINYTEXT NULL;
ALTER TABLE `nuke_users` CHANGE `ublock` `ublock` TINYTEXT NULL;
INSERT INTO `nuke_bbconfig` VALUES ('image_resize_height', '400');
INSERT INTO `nuke_evolution` VALUES ('img_height', '300');
UPDATE `nuke_counter` SET `type` = 'os' WHERE `var` = 'Linspire';
ALTER TABLE `nuke_bbgroups` ADD `group_count` INT( 4 ) UNSIGNED NOT NULL DEFAULT '99999999', ADD `group_count_max` INT( 4 ) UNSIGNED NOT NULL DEFAULT '99999999', ADD `group_count_enable` SMALLINT( 2 ) UNSIGNED NOT NULL DEFAULT '0';
UPDATE `nuke_evolution` SET `evo_value` = '0' WHERE `evo_field` = 'collapsetype';
ALTER TABLE `nuke_bbsearch_wordlist` CHANGE `word_text` `word_text` varchar(255) binary NOT NULL DEFAULT '';


Cool
#11: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: croh,  PostPosted: Sat Apr 21, 2007 1:19 am
    —
So you go to phpmy admin click sql query and you paste that in? Then once that is pasted in i can update my php eve from 1.0.1 to 3.2.

im defintently backing up first Smile
#12: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: croh,  PostPosted: Sat Apr 21, 2007 9:46 pm
    —
i recieved this: SQL query:

ALTER TABLE `nuke_evo_userinfo` CHANGE `position` `position` INT( 10 ) NOT NULL ;

MySQL said: Documentation
#1146 - Table 'bagntagc_nuke.nuke_evo_userinfo' doesn't exist

ive uploaded everthing into a diferent directory and have done everything but the 2- sql updates, and my stats for a game will not work, and the modules panel does not work. Is this becasue i have not updated the sql? it woldnt seem so, becasue everthing else (non sql) works fine.
#13: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Sun Apr 22, 2007 5:20 am
    —
that script will only update your database to 2.0.1 then use the 2.0.1 - 2.0.3 upgrade script in the evo package. if you're having a hard time upgrading your site, you can avail of the services at evo-help.com
#14: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: BEAR285, Location: WALES, UK PostPosted: Wed May 09, 2007 2:36 pm
    —
1.0.1 site, ran the script. uploaded all folders and files per instructions, one question is you say to do not upload the files in the includes root. I take it you mean the files that are in the includes folder with exception of the folders that are in the includes these must be uploaded.  II ran the upgrade from 2.0.1 to 2.0.3 and now get this error

SQL query:

INSERT INTO `nuke_bbconfig`
VALUES (

'rand_seed', '0'
)
MySQL said:  

#1062 - Duplicate entry 'rand_seed' for key 1

My question is did the sql stop at this error or did it complete the load with just this error displayed.  From past experience I take it stopped at this query.  My live site is now down again, desperate f0r some assistance.

Site is currently disabled.
#15: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: BEAR285, Location: WALES, UK PostPosted: Wed May 09, 2007 4:27 pm
    —
Okay, bit the bullet and did the includes, now i did save the orginal files, what files can I reload to put things relatively back to the config they where before without tottaly fragging the upgrade.
#16: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Thu May 10, 2007 3:09 am
    —
It's quite hard saying what files are needed and what files are not. I don't know what mods are installed in your site prior to the upgrade. To make it easier for both of us, you can just reupload all the files in the html folder, upgrade your database, then re-install all the mods you have.
#17: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: BEAR285, Location: WALES, UK PostPosted: Thu May 10, 2007 2:36 pm
    —
Okay, with my betasite I was able to fix the problems by comparing files and copying and replacing.  Everything is working now, the upgrade script that upgraded the site to 2.0.1 worked perfect, the upgrade sql from 2.0.1 to 2.0.3 did cause a few problems but it is all now sorted. thanks for the great tutorials and excellent sql's.  Site is working great now with no loss of data at all.  Thanks again.
#18: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: DELETED, Location: don't rush me PostPosted: Fri May 11, 2007 9:37 am
    —
glad to hear it dude...wish I could have helped but I didnt see your posts until now. Smile Anyway, all is well. Smile
#19: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Sat May 12, 2007 1:52 am
    —
nice going BEAR285, glad to hear that.
#20: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: SkIpErMan,  PostPosted: Thu Jun 28, 2007 3:58 pm
    —
I have trie to run above sql script! It looks like I dont have the table  nuke_evo_userinfo in the old evo relase I use!  Is this importent to have or could I just delete this textfield?

I am not shure if I fully have understund this manual! Do I need any other version like 2.01 2.02? The script above was not working for me to upgrade directly to 2.4 or 2.5!  I got a white site  Laughing

If I need any other version, then everybody needs it, so that would be nice if we could find needed version in the download area!

/SkIpErMan
#21: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: NICK_THE_HARI,  PostPosted: Sat Jun 30, 2007 5:41 am
    —
Out with the old in with the New
#22: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: mrsmith25,  PostPosted: Tue Oct 02, 2007 6:26 am
    —
Sad I read in depreciation where you said "there is no reason to still have 2.0.0"


That makes me a sad panda.. somehow thats the version I have. So I took a jab at running the sql code u linked to go from 2.0.0.-2.0.1. And it gave me these results.

in one window it said

Code:
Error
SQL query:

INSERT INTO `nuke_bbconfig`
VALUES (

'loginpage', '1'
);



MySQL said:  

#1062 - Duplicate entry 'loginpage' for key 1


Then in another window it said:

Code:
ALTER TABLE `nuke_evo_userinfo` CHANGE `position` `position` INT(10) NOT NULL;# Affected rows: 126
 
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');
INSERT INTO `nuke_bbconfig` VALUES ('loginpage', '1');


I am sooo not tech savy. is there any simple way to point me in the right direction? Thanks for even considering reading the "depreciated loser" post.



------ EDITED ------
Alright so I essentially went through the entire 2.0.1 to 2.0.5 process step by step clearing cache, lmprting sql, and replacing files. Earlier when I performed "VIEW NEW VERSION"  it said I had 2.0.0 and that the newest was 2.0.5.

Now when I hit the "VIEW NEW VERSION" button it says:

Nuke-Evolution Version

The current version is: 2.0.0 Basic
Your version is: 2.0.0 Basic
#23: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Rodmar,  PostPosted: Tue Oct 02, 2007 8:04 am
    —
You need to go trough each upgrade so this means from 2.0.0 to 2.0.1. Then from 2.0.1 to 2.0.3, from 2.0.3 to 2.0.4 and finally from 2.0.4 to 2.0.5. The first upgrade seems not to be included in the latest Evo package but all the rest is in there. All you need from Evo 2.0.0 to 2.0.1 should be explained here in this post:

http://www.nuke-evolution.com/modules.php?name=Forums&file=viewtopic&p=75715#75715

If you get an error regarding duplicated entry. Don't mind. This means, you already got that changed in your DB so that's fine already. Just take the next line and go on.

Also you may reread the whole topic here. It should be explained how you get to the latest version Wink

But be sure to make backups of your DB and files as well before you start with this procedure.

But I see, you say you already upgraded to 2.0.5 now but it looks like that you've missed something since your version still says 2.0.0.
#24: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Tue Oct 02, 2007 8:12 am
    —
it means you still haven't uploaded the new files or completed the sql upgrade.
#25: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: mrsmith25,  PostPosted: Wed Oct 03, 2007 1:07 am
    —
Rodmar wrote (View Post):
You need to go trough each upgrade so this means from 2.0.0 to 2.0.1. Then from 2.0.1 to 2.0.3, from 2.0.3 to 2.0.4 and finally from 2.0.4 to 2.0.5. The first upgrade seems not to be included in the latest Evo package but all the rest is in there. All you need from Evo 2.0.0 to 2.0.1 should be explained here in this post:


Yeah I might have branched off, but thats what i was saying in my post. I did the sql upgrade as suggested in this thread to go from 2.0.0 to 2.0.1, then I did all of the individual upgrades to eventually land at what was supposed to be 2.0.5

Quote:
http://www.nuke-evolution.com/modules.php?name=Forums&file=viewtopic&p=75715#75715  

yeah, thats the sql suggestion that I mentioned in my post that didnt seem pan out.


Ultimately the tone from the OP is that the 2.0.0 is way depreciated and support is no longer offered. Which I totally understand. ANd I would be more than happy to somehow do a clean install and take old user db and just update.

but here is my problem, I have no idea how to take an existing user database and just pop it into a clean installation.

I dont have any altered or magically modules in my installation. its just a basic install with a theme or two ive downloaded along the way + shoutbox.

One example of current issue that is prompting me posting in a "depreciated thread" =Fatal error: Call to undefined function: evo_mail() in /home/dawn2/public_html/modules/Your_Account/admin/approveuserconf.php on line 66

Cant seem to activate people who are trying to register. Havent really tried everything in the forums today, but noticed this as one of the recent failures
#26: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Tulisan, Location: Philippines (GMT+8) PostPosted: Wed Oct 03, 2007 1:47 am
    —
Rodmar wrote (View Post):
You need to go trough each upgrade so this means from 2.0.0 to 2.0.1. Then from 2.0.1 to 2.0.3, from 2.0.3 to 2.0.4 and finally from 2.0.4 to 2.0.5. The first upgrade seems not to be included in the latest Evo package but all the rest is in there.


You only need to do that on the database. As for the files, you can just upload the ones in the 2.0.5 package. if you're already lost on the database upgrade, you can just download you database (structure only) and using a file compare software i.e. winmerge, compare the tables of you database to the install/install.sql and to see what's missing in your tables.
#27: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Rodmar,  PostPosted: Wed Oct 03, 2007 10:34 am
    —
Yeah, forgot to mention Smile Only the DB has to get upgraded like that. The files you can use the latest one. No need to upload them everytime.
#28: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: mrsmith25,  PostPosted: Tue Oct 09, 2007 5:46 am
    —
aight - So I reran all of the dbsql upgrades (2.0.0.-2.0.1 + 2.0.1-2.0.3 + 2.0.3-2.0.4 + 2.0.4-2.0.5) and each showed duplicate entry. So then of course I went back and re-uploaded everything. Hitting refresh after each majory folder. It looks like a file was missing from the /modules/forums that caused my errors.

So at the moment everything is functional and appears ok. One slight hiccup - for whatever reason I have a "block" that I cant make go away. Or a setting that has default toggled and I dont know how or why.



What is normally set to "home" here ?  I have never had anything before that I Knew of. Now I cant seem to get rid of having an extra block screwing up my width.

*grabs another beer*
#29: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: Eyecu, Location: Canada PostPosted: Tue Oct 09, 2007 10:19 am
    —
News is usually the default home module.
#30: Re: Depreciation of Evo 1.0.1 & 2.0.0 RC1-2.0.0 Author: mrsmith25,  PostPosted: Sat Oct 13, 2007 5:04 pm
    —
Eyecu wrote (View Post):
News is usually the default home module.
Yes News was the trick. ty.  Smile
Nuke-Evolution.com -> 2.0.x Communiques


output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Page 1 of 1