URL to your eFiction: http://www.fanlibrary.net/eFiction35/
Version of eFiction: 3.5
Have you bridged eFiction, if so with what?: No. Uploading stories manually
Version of PHP: 5.2.6
Version of MySQL: 5.0.1.6
Have you searched for your problem: (yes/no) Yes
If so, what terms did you try: mhSQL fatal error
State the nature of your problem:
As I convert my old site over to eFiction, I am manually uploading each author's stories. Not really a problem, I have the time right now.
However, I just had a problem develop that I really don't understand.
In the middle of upload a new chapter to a story already uploaded for one of my author's, I got the following message.
A fatal MySQL error was encountered.
Query: SELECT PENNAMEFIELD AS penname FROM DBPREFIXdbnamehere_coauthors AS c WHERE sid = '4' LEFT JOIN dbnamehere_authors as author AS a ON a.UIDFIELD = c.uid
Error: (1064) You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LEFT JOIN dbnamehere_authors as author AS a ON a.UIDFIELD = c.uid' at line 1
Note: database name has been changed for purposes of posting only.
I have verified that even though I get the above message, the files ARE appearing (in readable format) in the appropriate directory. I have also verified that this is continuing to happen even after I have logged off the server and then logged back in. One other thing of note. It doesn't happen when I go in to an existant file and edit it and save, only when I am first up loading it.
Do you have a test account for us? Not to my knowledge
Updated to correct the url. 12/2/2008
There is always more than one way to accomplish any job. True talent is picking the best way.
Hmmmm. While the error message seems very similar, the actions triggering the message see quite different, especially since the files seem to be there and be complete. I just can't take the site live with this message.
However, I now have a test account set up for you.
Penname: eTest
Password: testing
By the way, how do you "Lock" a member, and how do you remove an account. I checked the FAQ, the manual and the WIKI and found no info on this.
Thanks,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
It took me a moment to figure out why I couldn't get to your website (too many "w"s in it; It should be http://www.fanlibrary.net/eFiction35/).
To lock a member you go to Admin->Members
Click on Unlocked Members
Find the member you want to ban and click on their name
You will see a message that says Do you want to Lock this Member's account: Yes | No
Choose Yes and you're done.
Then when they try to log in they will be unable to do so. They will see the message: "This account has been locked by the adminstrators of this site. Please contact the site adminstrators for more information."
To delete a member is a little different. You have to click on Members (but not in the admin section). Click on the Members or Authors link that's part of your regular site's menu (you still stay logged in as Admin). Click on a member's name and you will see editing options as you look at their profile. You'll see
Admin Options: [Validate] [Edit] [Delete] [Lock Account] [Make User an Admin]
Select Delete and it will ask if you are sure. Select yes and you have deleted the member.
******************************************
Mucking around in eFiction since circa 2001 (ver. 1.0)
Now running v.3
It took me a moment to figure out why I couldn't get to your website (too many "w"s in it; It should be http://www.fanlibrary.net/eFiction35/).
oops. 😳 I really hate it when I typo like that and then don't catch it. *sigh*
To lock a member you go to Admin->Members
Click on Unlocked Members
Find the member you want to ban and click on their name
You will see a message that says Do you want to Lock this Member's account: Yes | No
Choose Yes and you're done.
Then when they try to log in they will be unable to do so. They will see the message: "This account has been locked by the adminstrators of this site. Please contact the site adminstrators for more information."To delete a member is a little different. You have to click on Members (but not in the admin section). Click on the Members or Authors link that's part of your regular site's menu (you still stay logged in as Admin). Click on a member's name and you will see editing options as you look at their profile. You'll see
Admin Options: [Validate] [Edit] [Delete] [Lock Account] [Make User an Admin]Select Delete and it will ask if you are sure. Select yes and you have deleted the member.
Thank you. I shall be printing out this post, so that I have you instructions at hand, for when the site goes live. Now if I could just figure out what's going on WRT the mysql fatal error message. *sigh*
Thank you again, I truly appreciate the help.
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
@datapard, no need to print them, they have been added to the wiki:
https://efiction.org/wiki/index.php5?title=How_to_Lock_Members
https://efiction.org/wiki/index.php5?title=How_to_Delete_Members
I was getting a similar error message on a lot of different actions related to stories.php. All I can say is that it seems DBPREFIX isn't right, it's meant to be TABLEPREFIX. So it's probably a good idea to try making those changes and see if it works.
Tried this, unfortunately it doesn't seem to help. *sigh* On top of this, I noticed that of the two authors that have stories in the Library, only one shows the count when you look at the members.
That is to say that, when you click on the Members link, what shows is:
Bard Wolf [0] Eva Beckwith [3]
Dagmar Buse [0] Ravan Asteris [0]
eTest [0]
When what should be showing is:
Bard Wolf [1] Eva Beckwith [3]
Dagmar Buse [0] Ravan Asteris [0]
eTest [0]
Yet, when you click on Bard Wolf, the story is there. This all appears to be part of the same problem, although I could be wrong about that. I'm also not sure if this is close to the problem one of the others posted in 3.0 Bugs or not.
Note: when I made the changes to story.php that were suggested in https://efiction.org/forums/index.php?topic=6674 I continued to get the error messages. Since I saved the original story.php file, I copied it back over the changed file and saw; no appreciable change to the error messages. Maybe I'm missing something from that other post, *sigh* or just being dense this month. *sigh*
If it's not too much trouble could someone give me an explicit list of all the changes that were suggested for story.php. Once I have that, I will again attempt to make the changes and see what happens.
Thanks all,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Open stories.php and do a search and replace.
Search for: .PENNAMEFIELD.
Replace with: ._PENNAMEFIELD.
Search for: .DBPREFIX.
Replace with: .TABLEPREFIX.
Search for: .UIDFIELD.
Replace with: ._UIDFIELD.
I was having similar problems to you and these changes fixed it for me. Also check your database against upgrade.php and make sure that all the changes were actually made. A couple people (me included) have had it where some or all of the changes didn't happen.
People have also said that replacing stories.php with the file from 3.4.3 helps, but of course if you can fix it another way I'd do so.
Open stories.php and do a search and replace.
Search for: .PENNAMEFIELD.
Replace with: ._PENNAMEFIELD.Search for: .DBPREFIX.
Replace with: .TABLEPREFIX.Search for: .UIDFIELD.
Replace with: ._UIDFIELD.
Done. Unfortunately, I am still getting:
"A fatal MySQL error was encountered.
Query: SELECT author.penname AS penname FROM library1fanfiction_coauthors AS c WHERE sid = '6' LEFT JOIN library1fanfiction_authors as author AS a ON a.author.uid = c.uid
Error: (1064) You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'LEFT JOIN library1fanfiction_authors as author AS a ON a.author.uid = c.uid' at line 1"
I got this even after emptying my browser cashe. *sigh* Not sure what to try next.
I was having similar problems to you and these changes fixed it for me. Also check your database against upgrade.php and make sure that all the changes were actually made. A couple people (me included) have had it where some or all of the changes didn't happen.
Okay. It looks as though I have another missing file. *sigh*
I could find update.php but not upgrade.php.
People have also said that replacing stories.php with the file from 3.4.3 helps, but of course if you can fix it another way I'd do so.
I'd be tempted to try this, except I don't have a copy of 3.4.3 to pull the stories.php file from, not to mention that I got the impression that there where some other problems that might arise if one did this. Am I incorrect?
Any further suggestions as to what I should try next.
TIA,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
My mistake, sorry. It is update.php. (Eek, typos!)
This error has been seen by several different people, and that's the only solution I've seen so far. I got the error too, but then I made those changes and fixed my database and it disappeared.
Using the older stories.php isn't necessarily the best idea for security reasons, but as someone else pointed out, neither is letting hackers see the info displayed by the MySQL errors. I'd suggest uploading and see if you still get errors; if you do it's likely a database thing. Others have used it and it has solved their issues completely, so at least it's a good diagnostic indicator.
You can download the old version here: https://efiction.org/downloads/eFiction343.zip
My mistake, sorry. It is update.php. (Eek, typos!)
It happens. So says the typo queen. 😀
(quote author=Lyndsie link=topic=6761.msg36226#36226 date=1228672532]
This error has been seen by several different people, and that's the only solution I've seen so far. I got the error too, but then I made those changes and fixed my database and it disappeared.
Using the older stories.php isn't necessarily the best idea for security reasons, but as someone else pointed out, neither is letting hackers see the info displayed by the MySQL errors. I'd suggest uploading and see if you still get errors; if you do it's likely a database thing. Others have used it and it has solved their issues completely, so at least it's a good diagnostic indicator.
You can download the old version here: https://efiction.org/downloads/eFiction343.zip
Hmmmmmmmmm. Downloaded eFiction343.zip, extracted stories.php and uploaded it to the site.
Now, the error message I'm getting is:
Parse error: syntax error, unexpected ')' in [directory tree actually listed here]/eFiction35/stories.php on line 158
Not sure what I did wrong, as I simply save it over the other stories.php.
Any ideas anybody?
TIA,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Parse errors generally mean some part of the code didn't get ended correctly or there's something in there that shouldn't be. Open up the stories.php file and find line 158 and see if there is an extra ) hanging around.
My Site:
eFiction: v3.4.3
PHP: 5.2.6
MySQL: 5.0.45-community
Mods: Challenges, Submit Time and Word Count
Parse errors generally mean some part of the code didn't get ended correctly or there's something in there that shouldn't be. Open up the stories.php file and find line 158 and see if there is an extra ) hanging around.
Well, I found the extra ")" and deleted it. No more "Parse error: syntax error, unexpected ')' in [directory tree actually listed here]/eFiction35/stories.php on line 158"
. . . . . . Also, a totally blank page if you click on "Add New Story" or "Manage Stories", but not if you click on "Add New Series", "Manage Series", "Edit Bio", "Edit Preferences", and "View Your Statistics". 😐
Some days I really hate the fact that if there is a problem in code, virtually anywhere in the code, I WILL trigger it. 😐
Help?!
TIA
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Right, that makes sense. The two things that aren't working are the two things that are handled by stories.php. It looks like the old one's not going to work for you. If you had a brand new copy then the error probably wasn't because there's anything extra in the code, but because it's not behaving well with something else.
Have you verified all the database updates?
