URL to your eFiction: http://www.ffstories.net
Version of eFiction: 3.1.1 to 3.2
Have you bridged eFiction, if so with what?: No
Version of PHP: 5.2.0
Version of MySQL: 5.0.24-standard
Have you searched for your problem: No, but I did look through the latest topics regarding upgrade problems
If so, what terms did you try:
State the nature of your problem: Copy and paste any errors you are receiving.
I downloaded the new update and uploaded the files to my site.
Once the files were uploaded, I went to go to www.ffstories.net, and the following error came up;
Notice: Undefined index: link_key in /home2/ffstori/public_html/includes/pagesetup.php on line 84
Following Becca's suggestion of running update.php, I pointed my browser at www.ffstories.net/update.php and I received a page full of lines all saying the same thing, which was;
Warning: Cannot modify header information - headers already sent by (output started at /home2/ffstori/public_html/includes/dbfunctions.php:17) in /home2/ffstori/public_html/header.php on line 150
Once I re-uploaded the 3.11 files, everything worked again.
Therio
Turn the news and info blocks off then upload the files then run the update.
I did that, it still didn't work. I received the same errors.
I just noticed that you had posted an updated 3.2 file. I will download and try that one.
Therio
I downloaded the new update. I made sure the News and Info blocks were inactive, and then uploaded the new files and tried running the update again, but I try running update.php, I still get;
Warning: Cannot modify header information - headers already sent by (output started at
/home2/ffstori/public_html/includes/dbfunctions.php:17) in /home2/ffstori/public_html/header.php on line 150
Therio
It ran the update fine for me.
ETA Other than the index page which you seem to have set a 403 error on yourself. The site's up and running. So I'm marking this as closed.
I've been busy at work for the past couple of days so was unable to check back for replies. The site was up and running, yes, under version 3.11. However, you mentioned me having a 403 error set on myself. It reminded me of problems I had with 403 errors in the past due to Hotlink protection being enabled. So I disabled Hotlink protection and tried re-installing the update, and it worked perfectly 😀
Thanks for the help Tammy.
Therio
