The upgrade of my test site went very smoothly, but when I tried to bridge the site back to SMF, I encountered this error. I have no idea what it means, but I think it may be something on my end. Can anyone help?
If I change the files back to the unbridged version, the site works fine again.
A fatal MySQL error was encountered.
Query: SELECT * FROM fanfiction_authorprefs as ap RIGHT JOIN smf.smf_members as author ON ap.uid = author.ID_MEMBER WHERE author.ID_MEMBER = '1'
Error: (1142) SELECT command denied to user '******'@'*.dreamhost.com' for table 'smf_members'
Upgrading from 3.2.1 to 3.3
Site is Bridged with SMF
This is on the test site: Info in my sig.
I looked around in the recent post for the problem, but I didn't use the search engine and didn't see anything like this. When the site isn't bridged, it works perfectly. I left it bridged so that someone can take a look if they have to.
It's something to do with your config files. It's saying that the username you supplied to connect to the database doesn't have permission to do select statements.
Yeah, I thought it looked like something on my end. I've been playing around with it, but I can't find anything wrong. The script connects with the original version of queries.php and everything works. The forum is working perfectly. No errors or anything. The SELECT command is used in both versions...
I'll play around with it for a while, but if you have an insight on the matter I'd be most appreciative. And thanks for checking this out for me. I know how busy you must be.
Should this part have the smf twice like this?
FROM smf.smf_members
Hey Tammy, I don't know how safe this is but I got it to work by changing this line in bridges/smf/queries.php
define ("_AUTHORTABLE", $db_prefix."members as author"); // Do not change the aliasing (the "as author" part)!
I change it into this:
define ("_AUTHORTABLE", "smf_members as author"); // Do not change the aliasing (the "as author" part)!
and that seems to have fixed the problem. I'm not going to use it on my main site until you tell me if it's safe or not like that.
Might seem like a silly question, but how did you define your smf table prefix [line 4] in the queries.php file?
Not silly at all. At first I didn't change anything but the path to smf. I didn't know I was supposed to. Anyway, this is what line four of queries.php says:
$db_prefix = "smf.smf_";
Does that need to be changed?
"smf.smf_" is telling it to look in a database called "smf" for a table with a prefix of "smf_". Considering your error and what did work for you I think you want it to be just "smf_".
Thanks Tammy and Chelle. Tammy, you do know that the 'smf.smf_' is written into the file, right? Before I changed line 18 (I think), the only thing I touched in the file was the path to my smf install. The version of 3.3 I have was downloaded on the 15th of this month. I just thought that I'd let you know, since I'm not sure if this is an error or just something weird with my hosting setup.
Ah. Sorry. No I didn't. I remember experimenting with 2 separate databases using "smf.smf_". I guess I never changed it.
