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.
Okay. 🙁 Yes, the original install is the most recent version of eFiction.
Have you verified all the database updates?
Within eFiction, how do I do that?
There is always more than one way to accomplish any job. True talent is picking the best way.
You can't directly access the data through eFiction. Most hosts let you access the database through a program called PHPMyAdmin. I'm guessing either your fanfiction_coauthors table doesn't exist or maybe the index isn't defined properly. That's what happened to me.
After that, with the edited v3.5 stories.php and a recalculation of statistics (through the admin control panel, the 'archive maintenance' link, there are several different things to recalculate), you might be alright.
You can't directly access the data through eFiction. Most hosts let you access the database through a program called PHPMyAdmin. I'm guessing either your fanfiction_coauthors table doesn't exist or maybe the index isn't defined properly. That's what happened to me.
After that, with the edited v3.5 stories.php and a recalculation of statistics (through the admin control panel, the 'archive maintenance' link, there are several different things to recalculate), you might be alright.
Well, I have made the suggested changes to the original 3.5 eFiction's story.php. I am no longer getting the white screen, but I am back to:
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 have verified in phpMyAdmin that fanfiction_coauthors does indeed exist.
data is as follows:
| Field | Type | Null | Default | Comments |
| sid | int(11) | No | 0 | |
| uid | int(11) | No | 0 |
Indexes
| Key Name | Type | Cardinality | Field |
| Primary | Primary | 0 | sid/uid |
| uid | index | None | uid |
| sid | index | None | sid |
Space Usage
| Type | Usage |
| Data | 0 B |
| Index | 1,024 B |
| Total | 1,024 B |
Row Statistics
| Statements | Value |
| Format | fixed |
| Rows | 0 |
| Creation | Dec 08, 2008 at 04:15 PM |
| Last update | Dec 08, 2008 at 04:15 PM |
| Last check | Dec 08, 2008 at 04:15 PM |
Once I made the changes to story.php, and verified that the fanfiction_coauthors was there, I went in to Admin window for the website and recalced everything I could.
Can anybody see what I missed this process?
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Recalculating will fix the stats which I think you mentioned were computed wrong. So it's not as big of a deal as that error. I can't think of why it's still appearing for you. Check fanfiction_authors? The structure for it's in install/install.php.
Your indexes for coauthors are different than mine. Mine only has the first row, but I don't know enough about MySQL to say if that's a problem or not. It doesn't seem to make sense to have them as index both separately since it's PRIMARY KEY (`sid`,`uid`) but it might just be the way it's being represented in that user interface.
Sorry, not so helpful... I guess I'll keep my eyes open. : (
You're trying to help, and for that I am truly greatful.
I looked at install.php in my backup directory, and I noticed something. Some of the dbquery lines have ("CREATE TABLE `".TABLEPREFIX."(whatever table needs to be here)` and some have ("CREATE TABLE `".tableprefix."(whatever table needs to be here)`.
Could this be part of the problem? I'm not proficient enough in php at this point to know if it is case sensitive or not.
Thanks everyone,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
PHP is case-sensitive for variable names and such, but it depends on how they're defined in the script itself, and I honestly am not 100% sure if it matters.
Okay.
Just to add to the confusion, it appears that the problem only occurs when the author is a "Validated Member". *sigh* I hate having to "un"validate those members already in the system that are validated members, but it looks like that's exactly what I may have to do if I want to get the updated site on-line before Christmas.
With that thought in mind, and knowing that I have to bring the stories over from the existent site, I have to ask. Does anybody know of a way to upload stories to a site that doesn't require my doing it one file at a time? Also, is there a way to do a bulk validate if the need arises?
TIA,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Is the existing site an eFiction site? If so, then you can export the data from the database and then move over the stories folder. (HUGE asterisk, the way you do this depends on if you've already started putting stuff into your new site or not.) It can be done, but it could be tricky. If it's not an eFic site then it would probably be really difficult.
There's no way to do a bulk validate (that I know of) through the interface, but you could set it so that stories don't need to be validated. Or you could keep it so they do, but run a query in the database to turn all (or selected) validated to 1.
No, the site was not an eFiction site before. *sigh* Looks like it's going to be manual (1 story/chapter at a time) upload for this. Well, what is, is.
I wonder, is it possible to turn the need to validate stories on and off, like it is to change authors from having their stories automatically validated to needing to be validated? If so, I may go with that for now. (While still trying to figure out what the problem is with the install 🙂 )
Anyway, just know that I truly appreciate your assistance,
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
Yes, you can turn it on and off. Admin > Settings > Submission Settings. "Automatically validate all stories" turn to yes or no.
Just thought I would update everyone. Unfortunately, any form of auto validation triggers the error message, so it looks like I'm stuck with having to manually validate every chapter of the various stories as I put them up. C'est la guerre. :-] Ya do what ya gotta to get the job done. :-]
If anybody has any further ideas on what I can try to get the auto-validate to work as it should, I shall be happy to give them a try. Otherwise, I will just have to go as I am.
I truly appreciate all the help you good people have given me so far.
datapard
There is always more than one way to accomplish any job. True talent is picking the best way.
