Support Forum

I'm moving out because Envo suck a lot!
So, someone will be so kind to tell me the more safe steps to migrate?
I just use Mysql and will be fgreat keep datas intact.
Thank you guys!

Envo was based on .714 so an upgrade to .726 selecting .714 was the base would be a good place to start. If you have any data in modules not supplied by default in PN but supplied by envo (e.g. subjects ) then you'll need to grab these from thier original sources.

The important thing to stress here is to perform the process on a test setup first. Don't do this on your live site without testing the results. Even more importantly BACKUP YOUR SITE before doing anything on the live copy!!!!!!!

-Mark

Ok, great answer mark.
I'm not a newbie, i do always a safety backup
Anyway..my last question is... what about table prefix "envo_" should i change them BEFORE upgrade or just the upgrade will ask me which prefix should i use?
Thank man, u r very kind and smart :D

But, of course, you realise that I have to say it just in case .

The prefix doesn't matter. In any of the PN type CMS's the prefix is arbitrary. Just make sure when upgrading that you use the envo prefix instead of nuke.

-Mark

I'm sorry no good news...

here what i did locally using EasyPHP

- uploaded PN files
- dumped the original envolution DB and inserted in new DB created locally
- run the installer setting the prexix as "envo__"
- selected UPGRADE
- selected PN .71
- Error: Unable to update envo___users
ok...

- deleted envo__users
- inserted new row nuke_users
- dumped data inside
- renamed as envo__users
- Error: the same...
let's try again...

- read this board found thsi topic: http://forums.postnuke.co...opic&t=4098&highlight=
- followed GRUMPFISH info
- surfed CVS and dl the newer version of pn7.php
- modified it following post
here the code:

READ BELOW THIS CODE IS TOO LONG FOR ONE MSG (LOL)

post of entire file removed - markwest

By the looks of what you've copy and pasted (from the first of the two posts) there's a second _ in the table names. So you've entered your prefix as envo_ rather than envo. The _ is inserted automatically.

-Mark

post of entire file removed - markwest

- Error: SAME!

I dunno what to do LOL!
Help me MASTER!

Please don't post entire files. This makes it impossible to follow the thread and to help. When posting code only post the relevant lines.

-Mark

Sorry, usually is appreciated
Anyway..i try to change the prefix hold on man

-----
Luxia Network

------
Moderator @ Tom's Hardware Guide Italia
[COLOR=indigo]Microsoft Technical Beta Tester (ID

Code is appreciated when someone takes the time to isolate the relevant lines. Simply posting an entire file doesn't help at all. Masses of code in a forum is impossible to read as there's no syntax highlighting, the line wrapping gets broken etc.

-Mark

Ok... now here another stop error: Unable to update envo__banner

What you suggest me when this "UNABLE TO UPDATE error" appear? Delete the table and reacreate it following POSTUKE MYSQL file and after renaming them...or something else?

-----
Luxia Network

------
Moderator @ Tom's Hardware Guide Italia
[COLOR=indigo]Microsoft Technical Beta Tester (ID

If you look closely there are still multiple underscores in the table name 'envo__banner' <- two underscores here. Don't forget after each failed attempt to bring to database back to a known good state i.e. restore you envo DB.

-Mark

No no ENVO table HAVE 2 "_ _" is normal. So i put "envo_" (1 undescore).
I'll restore DB and try again
Thanx a lot for your "not deserved" quick support!
BRB

-----
Luxia Network

------
Moderator @ Tom's Hardware Guide Italia
[COLOR=indigo]Microsoft Technical Beta Tester (ID

I see - so on the envo install you put a envo_ as the prefix? This is not an envo thing. The _ doesn't need stating in the prefix of either PN or envo. So if you do add an underscore to the prefix you'll end up with double underscored table names in both envo and PN. This isn't a problem but it helps if you state things like this.

If it then doesn't work zip up and send me a copy of your envo DB and i'll be better able to advise. I'm guessing a little as i'm not aware of what changes have been made through the different envo versions. You may like to try a .72 upgrade path and see if this helps. Again restore a clean copy of your envo DB after each attempt.

-Mark