An endless loop of penis errors sounds like the story of my life :'(

I hate when these errors happen because they seem to not want to ever correct. Here is something you can TRY with minimum risk: go to your host and access your actual database. Select the evo_antispam table and EMPTY it. NOT "drop" but "empty".

Wait first I need to ask the "is it plugged in" question.

Did you select "upgrade" on your installation menu? I ask because the bit you quoted below seems like stuff that gets done only when you install b2evolution. In other words, upgrading should not try to build the antispam table and populate it with a few keywords.

In fact emptying that table will probably do nothing more than get you a few steps down the path before it gets confused by having another table with entries that already exists.

EdB wrote:

Did you select "upgrade" on your installation menu? I ask because the bit you quoted below seems like stuff that gets done only when you install b2evolution. In other words, upgrading should not try to build the antispam table and populate it with a few keywords.

In fact emptying that table will probably do nothing more than get you a few steps down the path before it gets confused by having another table with entries that already exists.

USUALLY I use the Installatron that my hosting service (hostpc) uses. BUT a couple of months ago something got really corrupted with my service, so now it no longer thinks it ever installed it. So I had to select new.

BUT I did select the database that B2evo was already using.

AND last weekend when I tried upgrading by downloading B2evo, uploading it, running the install, etc, I got the SAME problem combined with a host of other problems.

I can try doing THAT again and post THOSE issues if that's better.

Okay so this helps explain what's going wrong. When you select "new" it knows it has to make all the tables in your database. The problem is that those tables are already there, so it freaks out. "HEY I can't create and populate this table because it already exists and has the stuff in it I was going to put there" is what it is saying.

Do you have a backup of your database from BEFORE attempts to upgrade to 1103? If so I *think* it is in your best interests to restore the database and try upgrading.

"New" has the potential to kill all your existing content! I don't KNOW that it will, but telling it "new" is telling it you have nothing there now so make the basic stuff.

Maybe the upgrading process is smarter now, but in years gone by if you got halfway through an upgrade it was almost impossible to figure out how to get it to either finish or revert. Therefore I really hope you have a backup of your database handy. If so you should restore it THEN use the installer to 'upgrade'.

The scary thing is that if your database is half-way upgraded and you try to tell it 'upgrade' again it'll get scared because it will try to do something that's already been done. HOPEFULLY the upgrader portion of install is smarter now.

Please tell me you have a backup from when it was a happy 1.9.3 installation!

EdB wrote:

Please tell me you have a backup from when it was a happy 1.9.3 installation!

Yes, I did a backup.

BUT how do I upgrade it? I can't use the Installatron because it won't give me the upgrade option. And when I tried to just upload ALL the B2evo files before, I got error after error.

Also, I just discovered I have Itron (installatron) backups that my system must have automatically done.

I'm going to email my hosting service's support and ask if they can do something on their end to make the Installatron know that some stuff was already installed so I can just upgrade.

I doubt they'll be able to (the royally corrupted file was ROYALLY broken), but it's worth a shot.

As I expected, they can't back install uninstall restall. ;)

Unfortunately this isn't something we can fix. Once the install logs are lost we can't recreate them. Your either going to have to upgrade manually or install a new copy and migrate your old content to it.

Okay that's good (and bad) news. The good news is that you have database backups. The bad news is you seem to have no confidence in your host.

So here is where we are at: IF you can restore you database to a working version when you had 1.9.3 files that will be GOOD but it will not work with files from the 1.10.3 release. To make it work we have to upgrade the database to match the files. Does that make sense? Please do not be offended if you think I am "talking down" with you, but I do not know your skills or comfort level with advanced stuff online. Heck *I* don't understand advanced stuff and my personal blog is a wreck that I don't know how to fix!

IF you are able to restore your database to "the 193 days" AND you have files from the 1103 version THEN we will have to figure out how to make the database update to match the files. They work together yah? The files need to know the database so that it can add the right bits to your web page is what I mean.

Let's both hope a smart person comes along to help us out here. Tween now and then I'll do the best I can to help you. My skill level says you need to have a valid database AND valid files. MY understanding is that we can make your database match the files. It should be as easy as clicking stuff, but that did not work for you. So let's get it correct. Together. Slowly.

Or pray that one of the smart people here come around here and offer some help. ;)

EdB wrote:

Okay that's good (and bad) news. The good news is that you have database backups. The bad news is you seem to have no confidence in your host.

I have confidence in HostPC. I just know how many help tickets and tries and back and forthing it took to fix/uncorrupt the corrupted files, so I expected that we wouldn't be able to get back the already installed whatevers. ;)

So here is where we are at: IF you can restore you database to a working version when you had 1.9.3 files that will be GOOD but it will not work with files from the 1.10.3 release. To make it work we have to upgrade the database to match the files. Does that make sense? Please do not be offended if you think I am "talking down" with you, but I do not know your skills or comfort level with advanced stuff online. Heck *I* don't understand advanced stuff and my personal blog is a wreck that I don't know how to fix!

HA HA HA! But you've done so well at fixing mine!

No, not offended at all. My level is very low. I am just good at taking directions. When they're written in dummy+ level.

What you're saying is that we'll install 1.10.3 and then make the database match that?

IF you are able to restore your database to "the 193 days" AND you have files from the 1103 version THEN we will have to figure out how to make the database update to match the files. They work together yah? The files need to know the database so that it can add the right bits to your web page is what I mean.

You mean the 1103 files that I download from B2evo?

Let's both hope a smart person comes along to help us out here. Tween now and then I'll do the best I can to help you. My skill level says you need to have a valid database AND valid files. MY understanding is that we can make your database match the files. It should be as easy as clicking stuff, but that did not work for you. So let's get it correct. Together. Slowly.

Or pray that one of the smart people here come around here and offer some help. ;)

Hey smart person! 빨리 와 주세요! (Please come here quickly!)

:)

So is my first step to go restore the backup?

I HAVE canceled the installatron install (did NOT click finalize) AND used the Installatron's "uninstall" option to get rid of it.

B2evo is working for me like always. Awww, my good little B2evo...

So your blog is operational again? If this is true then either your backup is already restored OR your upgrade is successful. You can find your version by scrolling down to the bottom of any of your back office pages.

Also, the way it works is that your files know what version they are, and your database has a "schema" that needs to match what the files expect. There was a line in your first post that mentioned this.

You have schema version «9340», but we would need «9350».

By the way I don't know what an installatron is. I'm guessing it is some kind of program that installs programs? I use Fantastico a lot to build databases, but it always has old versions, so after it makes a database I throw away all the files and do my own upgrades. That's where we would be at if you have 193 running again: toss aside installatron, send (most) of your 193 files to never never land, then get your database up to speed with the 1103 files.

EdB wrote:

So your blog is operational again? If this is true then either your backup is already restored OR your upgrade is successful. You can find your version by scrolling down to the bottom of any of your back office pages.

Works perfectly, still 1.9.3.

By the way I don't know what an installatron is. I'm guessing it is some kind of program that installs programs? I use Fantastico a lot to build databases, but it always has old versions, so after it makes a database I throw away all the files and do my own upgrades. That's where we would be at if you have 193 running again: toss aside installatron, send (most) of your 193 files to never never land, then get your database up to speed with the 1103 files.

It's some sort of one click (OK, more like three) install that HostPC has. You click "INSTALL" and it asks which website, what you want the /extension to be, what database you want to use or builds a new one, etc.

Thus we should ignore installatron. It is a tool that works for what it does, but if your needs are more than it can handle then a better tool makes sense yah?

This is my suggestion. First read the manual page, linked as "Docs" above, about upgrading. Second, make sure you have backups of both your database and your files. Third, grab 1.10.3 from the "Download" link above and unzip that on your computer.

How you actually upgrade is up to you. Heck IF you upgrade is up to you, but it's a good idea. My method is to edit the NEW conf/_basic_config.php file to have the same connection info as the old one did. You can also CHMOD that file and edit it via the install/upgrade feature. Again the method is up to you.

Anyway you then delete all your files on your server EXCEPT your media folder and upload the new ones. You then run the "install/index.php" file and tell it you are upgrading. IT will take care of tuning up your database (the "schema" thing) without choking because something is already there. You then delete your "install" folder and - if all went well - you will have 1.10.3 running your blog.

But please move slowly and carefully. It's a lot easier to read and ask more before clicking stuff than to undo the 'damage' later on.