Hi @shunsai,

1. You can find the version checking this file: http://b2evolution.net/man/application-php
2. The upgrade process is prepared to go through large version leaps (as 2.x to 6.6.x), but there are many particular cases. So, the best option is trying it out and see what happens.
3. That database error message is warning you that the credentials you provided don't work. Please, make sure that you are typing the host, database, username and password correctly.

Regards!

@Manual Garcia,

Thanks for the reply, and I apologize for the extremely late followup.
I'm back to tinkering with this upgrade thing again. I managed to take care of the credentials problem. Now I'm attempting to upgrade.

Database schema is not up to date!
You have schema version «9910», but we would need «11486».

And after I attempt to upgrade my b2evolution database tables, it tells me:

Additional information about this error:
MySQL error!
The used table type doesn't support FULLTEXT indexes(Errno=1214)

Your query:
ALTER TABLE evo_items__item ENGINE=innodb

Does anyone have any suggestions as to what I should do next?

So I managed to find a copy of 2.4.6 to upload to my site and get my blog kinda working again. I still run into the same schema problems though when trying to upgrade to any higher version.

Also, in this 2.4.6, for some reason there are posts that show only the title, but the body shows up blank. In the backoffice, all the body is there and for all intents and purposes, they seem to have all the same attributes as other posts that do show. Does anyone have a clue as to why this might be? Could it have something to do with the database itself? Any suggestions on how I might fix this? Thanks in advance.

And sorry to @Manuel Garcia.. I misspelled your name in my previous post and couldn't find an edit button.

@shunsai I think you should try to fix the DB issue and finish the upgrade before to address additional issues.

I know this is not exactly the same version and error message you're getting, but this post may help you: http://forums.b2evolution.net/v6-or-v5-falied-to-upgrade-from-v. Basically it refers this post: http://b2evolution.net/man/unexpected-error-during-upgrade

In addition to that, the particular error you're getting seems to be related to the MySQL version. What version are you running?

@mgsolipa

It seems my host is using MariaDB 5.5.42.

I'm still not clear on why some posts show, but others show as blank, even though the text is there in the backoffice view. I'm still combing through those links you gave me, but is there any suggestion as to how I might fix my database?

@shunsai the suggestion are in the links I sent you before.

You should seriously dedicate more time trying to fix the upgrade than the missing content issue. I can't even think how b2evolution 2.x behaves running on MariaDB.

Please, let us know if you have any question.

Regards!

I recently upgraded a B2evolution V3.3.2 instance -- which was first migrated from a MySQL 5.x instance -- into an ephemeral (placeholder) local virtual machine running MariaDB 5.5.49. Subsequently B2evo v3.3.2 was upgraded to b2evo-ver 6.6.8.

According, if you can at least migrate to b2evo- ver 3.3.2, the upgrade to b2evo- ver 6.7.3 seems feasible -- based on my experience. Please note that the upgrade takes a while to complete and you may have to restart the upgrade routine several times -- as the upgrade routine (at least in a virtual machine) times out 4 to 5 times -- but it completes successfully.

Good luck!

Thanks, @nanahuatl. I actually tried this approach before with 3.3.2, and it was a no-go. I tried with 3.3.3 as you recommended just to be sure, but still getting the error:

Upgrading data in existing b2evolution database...
Loading: _core/model/__core.install.php
Loading: sessions/model/_sessions.install.php

Checking DB schema version... 9910 : OK.
Upgrading Posts table... OK.
Upgrading Categories table... OK.
Upgrading widgets table... OK.
Updating item types...OK.
OK.
Updating items table...
An unexpected error has occurred!

If this error persists, please report it to the administrator.

Go back to home page
Additional information about this error:

MySQL error!

The used table type doesn't support FULLTEXT indexes(Errno=1214)

Your query:

ALTER TABLE evo_items__item ENGINE=innodb

I'm trying to read through the Unexpected SQL Error during upgrade troubleshooting page that Manuel Garcia linked, but not meeting with success with that either. Basically that link says something I did corrupted my database, and I don't see how that could have happened. It suggested installing a clean install of the same version and comparing tables, but every time I try do a clean install alongside the one that's not working, I get:

OOPS! It seems b2evolution is already installed!

Any suggestions of what I can try next to compare or fix my tables? Is it a matter of the database originally being MySQL and transferring over to MariaDB? Is there a way to determine which version of MySQL the database was created on?