hudson2001 wrote:

Or is there another way? Thoughts?

Upload v4.0.5 files to whatever.com/blog_new/ then duplicate the database and upgrade it (not the original db!). Fix all problems, tune it up and then rename "blog_new" back to "blog".

Just remember [u]to not make[/u] any changes (create posts etc.) after you duplicate the database cos they won't be reflected on the new system.

So it's as easy as keeping everything where it currently is, creating and installing 4.whatever as a NEW blog as blog_new, then renaming it when done with just a simple F2/rename command? Everything will be in the right place? That seems too easy. :)

I guess the hard part comes with duplicating the database. Is that the technical term for just making a copy of it locally in case I mess up? Or is it having my host do a backup? Do I just copy everything in my FTP program to the same directories (media, etc.)?

I'm sorry if this is obvious to you, but it's confusing to me and I obviously don't want to screw it up. :)

FYI I am currently attempting to install 4.0.5 in a new blog directory. I'm scared. Hold me. :)

Yeah, this is what I didn't want...pure confusion. :(

I uploaded everything into a new folder and ran the install file. To me, it seems like it will overwrite or add to the current b2evolution database I have (I only get one on my host). So I thought "Okay, I will just backup the database. Or export it. Or something." So I logged in there and although there's a nice Export tab, all the options are greek to me and there's no way to figure it out without outside assistance.

http://i52.tinypic.com/169fg4z.jpg

Any guidance? Or can I safely install 4.0 in the same database? I wouldn't think so, but...

Sigh.

I knew it couldn't be THAT easy. :(

Okay, I found help for that (http://forums.b2evolution.net/viewtopic.php?t=14421) so am backing that up now.

[u]Never upgrade[/u] working database. Always upgrade a duplicate copy first and make sure it's working.

You can easily duplicate the database in phpmyadmin

- go to cpanel and create an empty database
- assign an existing db user to newly created db
- open phpmyadmin, select source db on the left then click Operation tab on the right
- find "Copy database to" field and enter target db name there e.g. usename_newdbname
- select "Structure and data" and remove "CREATE DATABASE before copying"

After that you must use the second dbname in b2evo 4 during the upgrade.

Save your time and don't export the database, just make a copy within phpmyadmin.

Except I cannot create another database--I'm only allowed one. I guess I could ask if I could temporarily have another.

Then you should use different table prefix e.g. "evo4_" instead of "evo_"

Export the database to your hard drive, open it in text editor (never open with Windoze notepad or M$ Word)

Replace all instances of evo_ with evo4_ and import the database back. Then use different table prefix in b2evo 4 when you upgrade (this is whole another story and I'll need to write more instructions for you) :)

I think my brain just exploded. :)

I wrote my host to see if they'll give me another database. I don't see why they wouldn't - I'm not a huge user sucking the data or anything.

BTW there are plenty of hosting copanies that offer cpanel hosting for under $5/month

So glad that you started this post; unfortunately, I'm in the exact same position with 2.4.7! Scared and reading the many things to do IS confusing.... you're not alone. After being ill, it did something to the brain cells and I'm not as snap-to-it as I use to be. :(

I use cPanel and it is pretty easy, but I'm still scared to do anything. I know that I need to make an update, but not sure how this is going to work out. It seems overwhelming. I'll be following you. Thanks again for this open and honest post. :)

Tosca

Just to quickly update...I have decided against upgrading at the moment, for a few reasons. 1) My host hasn't gotten back to me about a temporary database...but more importantly, 2) my husband just got orders so we'll be moving in a month or so and I just don't have the time or energy to deal with this.

If anyone else tries this, please let us know of your success or failure. :)

Upgrades are always good, but does anyone know if this has to be done -- as in, "must"?

Back to my original thought... if I had a new domain, what would be the process to bring over all the old posts, if at all? I have six separate blogs - can I export/import each one individually to the same blog on the new site?

I am still envisioning that this will be terrifying and completely confusing...which is why I am still using 2.4.7.

hudson2001 wrote:

My b2evolution Version: 2.4.7

I have a thousand posts throughout five heavily-customized blogs and honestly, I'm not prepared for the trauma that comes with a major upgrade and an entirely new way of doing every little thing. I don't have a lot of time to play with it and my personality doesn't really handle change well. :)

I have been contemplating getting a new domain (so the blogs would now be located on mynewblogsite.com instead of mycurrentsite.com/blogs) so I am wondering if there is a way/if it's at all possible to install the current version at the new domain then move all the old posts? That way I can make sure everything is working right (new widgets, new skins, etc.) before taking the chance that all my blogs will disappear (or look crappy) and I'll have heart failure during the transition.

But that seems too easy.

Or is there another way? Thoughts?

I upgrade every time there's one available (I've been using b2evolution since 2.4.5) and have never had any problems (the admin interface hasn't really changed since then, AFAIK; it's just gotten new features). Actually, I did have one problem with one of my plugins in 3.3, but it was an easy fix (only retrieving settings if there are settings to retrieve; you can definitely tell I'm an amateur). Anyway, you just replace the files and run the upgrade script. Transferring to a different domain should be easy too; just edit your conf/_basic_config.php file and if it's on a different host, export your database (via phpmysql or whatever your host has) and import it into your new host's. Easy peasy.

If you have plugins or skins that don't work, you should contact their authors to get a fixed version. In the meantime, I'm sure you can live without them.

I'll just leave with the final thought that upgrading is always a good idea. You don't want old vulnerable code that bad guys can use for evil purposes on your server.

hudson2001 wrote:

I have six separate blogs - can I export/import each one individually to the same blog on the new site?

At the very least, you can put them into different tables in the same database. Just change the value of $tableprefix in conf/_basic_config.php .

How does it work the database writing in the new version? Where is the documentation of that? (specially, the global cache table) Im having some troubles with a migration, and I need some documentation! :D

Thanks in advance guys! :D