Last seen: Mar 25, 2024
I just enabled PHP 5 on the server where I do testing. I've got two or three eFiction installs there and I didn't notice any differenc...
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...
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...
Not sure, no, but the best thing to do would be to follow the suggestions in this post:For certain you've got dbprefix in there when it shouldn...
Okay, so, my coauthors table looks good now. I had created it manually and the index was not right, but I've fixed it and the problem persi...
You can't directly access the data through eFiction. Most hosts let you access the database through a program called PHPMyAdmin. I...
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...
I believe it's in user/editbio.php, line 106 (approx). I've been trying to hunt down something else and I came across it.
I was getting a similar error, and I think that was the one that was caused by the database not having been upgraded properly. I'd check yo...
My mistake, sorry. It is update.php. (Eek, typos!)This error has been seen by several different people, and that's the only solution ...
Did you go through this entire thread (linked above) and make all those changes? It looks like it's the same issue.
Open stories.php and do a search and replace.Search for: .PENNAMEFIELD.Replace with: ._PENNAMEFIELD.Search for: .DBPREFIX.Replace with: .TABLEPR...
It looks like there's still a DBPREFIX in there. It should be TABLEPREFIX.
Saya had the same issue in that thread. - this one, right?) I haven't seen the solution.I'm curious to know if your stories are ...
You don't have the support information here so I'm not really sure what version you upgraded from and all that, but it looks like the upgrad...
