| User | Post |
|
|
|
Here is the story
Tried an upgrade to 3.1 then got the same error I think, then reinstalled 3.03
and saw the warming not to upgrade to 3.1 that you were working on a patch.
I now tried to install to full upgrade 3.1.1
and got the following error.
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
SELECT user_id AS ID, display_name FROM wp_sfmembers WHERE pm = 1 ORDER BY display_name
So I reinstalled 3.03. it still works
But I can not upgrade. Is there another fix.
|
|
|
|
|
I really do not underatand why several people have expoerienced a problem with the creation of this table. Itls very odd. We have been adding tables without problem for a year and a half yet this one seems to be a problem.
Anyway - the answer to your question is in this thread - see post 4. Hope it works for you.
|
|
|
|
|
My sfbuild was set to 320. Should I still do the following:
So in this case you need to open the WP Optiions table and find the key value 'sfbuild'. It shoud be set to 336. You need to change that and set it to 323.
|
|
|
|
|
Thats a tough question to answer because it's impossible for me to tell at what stage the upgrade failed.
I guess I would try it set as it is although you say it has already failed like that. If I knew what the problem is I could be more specific. I think try it and be prepared to check all your options in case one or two get skewed.
|
|
|
11:11 pm
25 May 2008
|
Mr Papa
Moderator
| | Arizona, USA | |
|
| posts 1602 |
|
|
just for our records, what is your version of mysql?
|
|
|
|
|
Ok, I changed the sfbuild to 323
deactivated 303 and uploaded 3.1.1 and Activated 3.1.1 - got the same error
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
Checked the database the sfbuild is still at 323
———————————————-
Deactivated 3.1.1 and changed 323 to 336
activited 3.1.1 got the same error
Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
plus
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
SELECT * FROM wp_sfmembers WHERE user_id = 1
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
SELECT posts FROM wp_sfmembers WHERE user_id = 1
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
SELECT * FROM wp_sfmembers WHERE user_id=1
WordPress database error: [Table 'relax_wrdp1.wp_sfmembers' doesn't exist]
INSERT INTO wp_sfmembers (user_id, display_name, pm, moderator, usergroups, posts, lastvisit) VALUES (1, 'admin', 1, 0, 'a:1:{i:0;s:1:"2";}', 0, now());
Plus more select errors
for your information my system is wp 2.5.1
| Apache version |
1.3.41 (Unix) |
| PHP version |
5.2.5 |
| MySQL version |
4.1.22-standard |
|
Architecture
Operating system
|
i686
Linux
|
|
Any ideas now? Reloading vers. 303 for now - l checked the sfbuild - it is still at 336; forum still works fine under 3.03
|
|
|
|
|
Well we only support MySQL version 4.2 and above. Having said that, anything below 4.2 can sometimes work although support can be patchy and… sometimes the problem results in tables not being created or Table ALTER statements failing. This looks like your problem. You may need tp create the table manually for which we could give you a sql sxrpt to run
|
|
|
|
|
Well, the hosting company said they planned an upgrade to version 5 in july or august. So maybe it is best just to wait.
|
|
|
|
|
I can not even confirm if that is the problem - only that it has been a problem in the past. Oddly, quite often the initial install will go well but upgrading will not allow the creation of new tables or new coliumns on exisiting tables.
But I do think it is unreasonable that there are hosts out there taking peoples money yet still running what is, in software terms, very old versions.
If we find anything specific howver, we will post it here and publush an interim upgrade.
|
|
|
9:25 am
26 May 2008
|
Wistiti
Member
| | Wistiti | |
|
| posts 13 |
|
|
Hello, just to confirm you, my SQL version is 5.0.
|
|
|
|
|
Yes - but it still needs installing in the right order. There have been one or two more upgrade problems than we usually have and I really do not see why this should be although one suggestion was a timeout. We will try and look into that if possible to see if it may be a factor.
|
|
This forum is currently locked - access is read only
Forums
