URL to your eFiction: efictiontest.verilyviridian.com
Version of eFiction: 2.0.7, upgrading to 3.01
Have you bridged eFiction, if so with what?: no
Version of PHP: 4.4.4
Version of MySQL: 4.1.21-standard
Have you searched for your problem: yes
If so, what terms did you try: step two, table prefix
Have you looked at the FAQs: yes
State the nature of your problem:
The error message generated by step two was a fatal MySQL error; it couldn't insert the data into the table:
Error: (1146) Table 'fanfiction_settings' doesn't exist
Well, the problem is that I had to create the table manually, because it wouldn't do it automatically. The automatic version of step one asks you for the prefix, but the script doesn't when you do it manually, so it doesn't know that the table is actually called 'testfanfiction_settings', with a prefix.
I don't know that much about mySQL, so is there a way I can fix this? I'd change the table name and leave out the prefix in the 'tableprefix' field until upgrade finished, but I don't know if the upgrade script is going to need to look at the other tables (which all have the prefix) or not.
Any advice on how I should best proceed would be great.
I had the same problem, and I just changed the table name to what the script was looking for. I've completed the installation now, and it doesn't seem to be a problem to have that table minus your prefix, and the rest of the tables with the prefix.
Thanks for the help, sicokitty. I went ahead, and the install has completed successfully now. I've got another issue, but this one is solved.
The settings table has a separate prefix than the rest of the tables. This was done so 2 eFiction installs could share the settings table as well as the authors table. You're asked for a settings table prefix in step 1. That goes with your settings table. It is not the prefix you assigned previously to your 2.0 tables. It can be, but it will be stored separately so that you have the option of having it be different.
That's the prefix it's ignoring though, the one you assign in step 1. It looks for the settings table minus the prefix.
I don't understand how though. Others are getting through the install just fine. I myself have set a prefix for the settings table on each of my test runs. Did you perhaps set a prefix that wasn't alpha-numeric? Maybe something with quotes or symbols?
I don't understand either, I didn't have the problem when I tested the earlier beta version. My prefix was just jfic, no quotes, just letters.
I'm running the install on the live site now, so if it happens again, I'll screenshot it for you. It may be a really simple thing I'm overlooking.
ETA:
Sorry I got a little confused between the steps in the manual and auto table create.
So if you go the manual install option, you don't get a step to assign the settings table a prefix, and when I put it in manually, I gave it a prefix, and the script was looking for one minus prefix. That was easy enough to work around once I figured out what the script wanted me to name it.
The real problem is probably just that the auto install for tables isn't working. It's trying to drop the settings table, which wasn't a part of the mySQL tables in 2.0.
You set the settingstable prefix in step 1 (at the same time you set the database name, password, etc) BEFORE you manually installed the settings table in step 2.
Really? The first step I got in the upgrade was asking me if I wanted to install the settings table automatically, or manually. There was no step to set the database settings. If you chose auto, there was a drop table error, and if you chose manual everything went fine so long as you left the settings table without a prefix. The next step I got after manually putting in the tables, was to set the key, then it moved on to all the settings.
I'm stumped as to how best to show you this. Something went wrong, and maybe it was something I did, but I'm really not surer, I followed everything it asked me to do very carefully. Twice! Hehe. Maybe I'll run the test upgrade again and record it or something so you can see what I did.
This is the error that I'm receiving:
A fatal MySQL error was encountered.
Query: DROP TABLE fanficsfanfiction_settings
Error: (1051) Unknown table 'fanficsfanfiction_settings'
This shows up after I try to insert the settings table prefix after choosing the automatic option.
Yea that's the same drop table error I got when I went with the auto install.
Okay I finally get it. You actually are getting an error. It'll be fixed in the next update.
Bump. This should be fixed now with the latest release. If no one replies in a week with the same problem, I'm going to close the thread.
It's been a week, so I'm marking this as closed. If the original poster comes back and is still having problems, please feel free to continue the thread.
