Have you tried re-uploading all your files? What version of eFic and of PHP & MySQL do you have? (Could you fill out the support request template?) Looking in the stories.php for 3.5, the line numbers of the messages you got don't match at all. The mkdir and chmod commands appear around line 250 and line 525, not 205. So either you've got some of the wrong files, or you're at an earlier version of eFic. (stories.php was changed a lot for 3.5.) Just trying to sort that out to best help.
This is the section(s) it's referring to (lines 250-253 of 3.5):
mkdir("".STORIESPATH."/$uid/", 0755);
chmod("".STORIESPATH."/$uid/", 0777);
}
$handle = fopen("".STORIESPATH."/$uid/$chapid.txt", 'w');
525-528:
mkdir(STORIESPATH."/$uid", 0755);
chmod(STORIESPATH."/$uid", 0777);
}
$handle = fopen(STORIESPATH."/$uid/$chapid.txt", 'w+');
The first is for saving to the database and the second is for saving to files.
So, what those messages are saying is that the folder for the user's uid inside of the stories folder hasn't been created. That's how stories are stored. Each chapter is inside a folder numbered after the author's uid. The first chapter of the story has the same id as the story id (ie. 3858.txt). Subsequent ones have their chapter ID as the number (I think).
The section of the script that assigns the uid-numbered folder must be failing. I'll try to find where in the script that happens when I have some more time (got to run now).
For the account that you are testing with, is there a folder inside the stories folder that is numbered with the account's uid? If not, consider creating it manually and then trying to upload. It'll be diagnostic, at least, until the reason why it's not making it automatically is sorted out.
Ah, terribly sorry, let me get all that information for you...
URL to your eFiction:
http://www.transfictions.net/tffics/index.php
Version of eFiction:
Version 3.3
Have you bridged eFiction, if so with what?:
No.
Version of PHP: can be found out from your host
PHP version 5.2.5
Version of MySQL: can be found out from your host
MySQL version 5.0.67-community
Do you have a test account for us?
Just created one...
Username: TestAcct
Password: testbeta
Hope that helps!
Okay, I'll take a look at that tomorrow. I think I have a copy of pretty much every eFic 3.0 release on my desktop at home (I am away from home until tomorrow). Did you look in the stories folder to see if a folder with the uid in question exists in there? (It should, since you moved your files over, but if it's an account that has never posted a story before maybe it doesn't have one?)
I've checked my stories folder. It's there, as are all the folders inside of it. I can open it with File Manager, go to the txt files, open them in an edit window and read the fics. I just plain can't understand why when I try a direct link, it says 404 not found. I'm just utterly puzzled on the matter. *shakes head*
Thank you for the assistance though! It's ever so appreciated.
I'd ask your host. It sounds like there's something wonky going on that they have control over. Point out you're trying to access one of the .txt (give them the direct link) and see what they say. I don't think there's any reason those should be giving you a 404. Whatever's causing that is probably also causing the script to not find the folder they're in.
You either don't have the stories folder created or you've got the folder path in your settings incorrect. It can't find the folder to create the sub-folder inside of.
The stories folder is right there where it has always been. When I go to admin and settings on the website, and go to submissions settings, it says "stories" in the stories path box. The stories are saved in files just like they always have been. I can go into cPanel to the Stories folder, open it, then open the subfolders and pull up the txt files and read the stories. But I can't direct link to them or get to them in any other way.
Any more thoughts? *wry grin* I'm more than ready to do whatever I have to in order to get my site back up and going.
Did you talk to your host? They can probably shed some light on why you can't even view the stories files when you directly access them.
