I hope you'll be able to help me. I don't want to post in the "Attached images do not appear" since its not related anymore.. anyway, I figured something went wrong during database upgrade even though I didn't have any error messages. The attachments table is empty and I can't pull up any old attachments, so basically I will have to go through each of them and fill into the table. But first I need to figure what's wrong with the attachment function at all because I can not attach anything either.
So, having all that mentioned above I installed the new wsnlinks 3.22 and comparing tables with the one I had incorrectly upgraded.
Here is first question:
Do the tables should be exactly the same as you install it fresh or upgrade from 3.15 to 3.20? Why I'm asking, because I have a lot of extra fields in the upgraded tables comparing to the one I installed brand new.
Do the tables should be exactly the same as you install it fresh or upgrade from 3.15 to 3.20?
I don't understand the question. The tables should have all the fields they need. Any other fields would be things you added.
Anyhow, attempting to use the script without a proper upgrade is useless as it will only lead to countless more problems and I can't really support it. You'd be better off copying all your old 3.1x data over into the tables of a new install with phpmyadmin, if new installs at least work for you. Then once that was done you could go back and run the upgrade for the attachments.
Paul wrote: You'd be better off copying all your old 3.1x data over into the tables of a new install with phpmyadmin, if new installs at least work for you. Then once that was done you could go back and run the upgrade for the attachments.
Ok, I've done it twice now - I installed 3.15 (what I had before) without any data - then submitted one link (just to have something) (I followed all the instructions exactly - everything is CHMODed as supposed to be) then I overwrote with the 3.22 files as instructed in the readme.txt (first time I overwrote templates, but the second time I left the old ones) - then I ran upgrade.php and got blank page.
I don't know - am I repeating the same error over and over or there is something wrong with the upgrading script. Here is the URL of the 3.15 with the overwritten files from 3.22 - can not run upgrade.php http://www.myrhomes.com/temp/wsnlinks/upgrade.php
3.15 was installed just fine - no errors. Can install 3.22 without problems, but can not do upgrade.
Must be a host issue then, I guess. Have a phpinfo file? Or, if your host is good about support, any chance of asking them why a file would go blank like that on their server?
The upgrade.php file is virtually the same one as 3.16 used, no important changes. Try uploading your 3.16 upgrade.php to your 3.20 directory and running that.
Am I happy or what upgrade from 3.16 worked! I'm getting a lot of
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 'ADD topicid int default '0' NOT NULL' at line 1
messages though.
Will try to upgrade my database with the data and see what happens. So, looks like it has to do with the scripting in the file..
Interesting. I copied the whole data from my main site into different account with the same host. Installed 3.15, imported all the data - all looked fine. Then I upgraded to 3.23 (had to use upgrade.php from 3.16) - looks all neat and pretty, feel s good and seams like no problems. Tried to attach a picture to a listing - no luck - no errors no messages at all just refreshes the edit page and that's it - I checked the tables - no filed were uploaded. Was going to move the whole thing into my main account, but since attachments still don't work I'm putting it on hold. Do you thik it might have something to do with the upload.php from 3.16?
Did you remember to update your usergroup permissions to let the usergroup upload at least 1 file? And you're using 3.2 templates, no 3.1x ones in there?
Anyhow getting errors on upgrade is odd and must still indicate something being wrong.
I've just observed that a way to cause upgrade.php to be blank with no debug output is tp place your config.php in another path and forget to update the file to indicate that.
I'm not really following the idea. What path are you talking about? I have my config.php in the exactly the same place where it always was - I also noted before that I tried installing brand new directory and upgrading it without any adjustments and the effect was the same, so I don't really understand what you mean. Would you explain please? I also tried upgrading my mirrored version after I used upgrade.php from 3.16 (successfully) to 3.24 and got blank upgrade page again. I don't know if I can use upgrade.php from 3.16 again - I noticed it is different in size..
well.. ok, I tried the /home/my_host/public_html/wsnlinks/ too - it worked but till here
Warning: updatedatabasefields(/home/my_host/public_html/temp/wsnlinks/http://www.mydomain.com/temp/wsnlinks/config.php): failed to open stream: No such file or directory in /home/my_host/public_html/temp/wsnlinks/upgrade.php on line 141
There's no point in specifying a path to the config if you're just leaving it in the WSN Links directory. The point is to put it outside of the web root, as the manual describes.
So anyhow if this is why your upgrade.php is blank, stop doing it -- use the default prestart.php.
I guess you're missing what I've been saying - I have config.php in the wsnlinks folder by default and never changed any paths until you pointed it out as an option if config is moved... every upgrade.php after v.316 giving me blank page.
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on incorrectly upgraded
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
I hope you'll be able to help me. I don't want to post in the "Attached images do not appear" since its not related anymore.. anyway, I figured something went wrong during database upgrade even though I didn't have any error messages. The attachments table is empty and I can't pull up any old attachments, so basically I will have to go through each of them and fill into the table. But first I need to figure what's wrong with the attachment function at all because I can not attach anything either.
So, having all that mentioned above I installed the new wsnlinks 3.22 and comparing tables with the one I had incorrectly upgraded.
Here is first question:
Do the tables should be exactly the same as you install it fresh or upgrade from 3.15 to 3.20? Why I'm asking, because I have a lot of extra fields in the upgraded tables comparing to the one I installed brand new.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Do the tables should be exactly the same as you install it fresh or upgrade from 3.15 to 3.20?
I don't understand the question. The tables should have all the fields they need. Any other fields would be things you added.
Anyhow, attempting to use the script without a proper upgrade is useless as it will only lead to countless more problems and I can't really support it. You'd be better off copying all your old 3.1x data over into the tables of a new install with phpmyadmin, if new installs at least work for you. Then once that was done you could go back and run the upgrade for the attachments.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
You'd be better off copying all your old 3.1x data over into the tables of a new install with phpmyadmin, if new installs at least work for you. Then once that was done you could go back and run the upgrade for the attachments.
Ok, I've done it twice now - I installed 3.15 (what I had before) without any data - then submitted one link (just to have something) (I followed all the instructions exactly - everything is CHMODed as supposed to be) then I overwrote with the 3.22 files as instructed in the readme.txt (first time I overwrote templates, but the second time I left the old ones) - then I ran upgrade.php and got blank page.
I don't know - am I repeating the same error over and over or there is something wrong with the upgrading script. Here is the URL of the 3.15 with the overwritten files from 3.22 - can not run upgrade.php
http://www.myrhomes.com/temp/wsnlinks/upgrade.php
3.15 was installed just fine - no errors. Can install 3.22 without problems, but can not do upgrade.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
I just installed plain 3.22 and went to upgrade.php - blank page. Is it supposed to be like that? Is it something with my host?
P.S. Installed 3.20 and also no output from upgrade.php...
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Must be a host issue then, I guess. Have a phpinfo file? Or, if your host is good about support, any chance of asking them why a file would go blank like that on their server?
The upgrade.php file is virtually the same one as 3.16 used, no important changes. Try uploading your 3.16 upgrade.php to your 3.20 directory and running that.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
Am I happy or what
messages though.
Will try to upgrade my database with the data and see what happens. So, looks like it has to do with the scripting in the file..
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
Interesting. I copied the whole data from my main site into different account with the same host. Installed 3.15, imported all the data - all looked fine. Then I upgraded to 3.23 (had to use upgrade.php from 3.16) - looks all neat and pretty, feel s good and seams like no problems. Tried to attach a picture to a listing - no luck - no errors no messages at all just refreshes the edit page and that's it - I checked the tables - no filed were uploaded. Was going to move the whole thing into my main account, but since attachments still don't work I'm putting it on hold. Do you thik it might have something to do with the upload.php from 3.16?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Did you remember to update your usergroup permissions to let the usergroup upload at least 1 file? And you're using 3.2 templates, no 3.1x ones in there?
Anyhow getting errors on upgrade is odd and must still indicate something being wrong.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
I've just observed that a way to cause upgrade.php to be blank with no debug output is tp place your config.php in another path and forget to update the file to indicate that.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
I'm not really following the idea. What path are you talking about? I have my config.php in the exactly the same place where it always was - I also noted before that I tried installing brand new directory and upgrading it without any adjustments and the effect was the same, so I don't really understand what you mean. Would you explain please? I also tried upgrading my mirrored version after I used upgrade.php from 3.16 (successfully) to 3.24 and got blank upgrade page again. I don't know if I can use upgrade.php from 3.16 again - I noticed it is different in size..
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
I went to prestart.php and filled the $pathtoconfig = "http://www.mydomain.com/wsnlinks/"; I tried without trailing slash - still getting blank page.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
That is not a file path.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
well.. ok, I tried the /home/my_host/public_html/wsnlinks/ too - it worked but till here
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
There's no point in specifying a path to the config if you're just leaving it in the WSN Links directory. The point is to put it outside of the web root, as the manual describes.
So anyhow if this is why your upgrade.php is blank, stop doing it -- use the default prestart.php.
Forum Regular
Usergroup: Customer
Joined: Oct 30, 2003
Total Topics: 54
Total Comments: 197
I guess you're missing what I've been saying - I have config.php in the wsnlinks folder by default and never changed any paths until you pointed it out as an option if config is moved... every upgrade.php after v.316 giving me blank page.