I tried to install the 4.1.69, not in the wsnlinks subcategory like the script suggested, but on root where i wanted it. I entered as db-prefix a name with two dashes. The installer stopped saying that this is not possible and then automatically deleted the entire installation. In this case wiped the entire domain, with all the other scripts i had installed, thank god nothing important.
You should change this immediately, before someone loses something important.
You had other scripts in subdirectories of your WSN install location? Disabled the deletion... but this creates an alternate problem, since you can't properly reinstall until you remove the old install. I could save any subdirectories, but then you might be putting other scripts in files.
You had other scripts in subdirectories of your WSN install location?
Yes, when the directory is the main site, all other scripts go into subdirectories.
Disabled the deletion... but this creates an alternate problem, since you can't properly reinstall until you remove the old install. I could save any subdirectories, but then you might be putting other scripts in files.
In this case, I think the best solution is to delete only the files/directories that the script uses. The script knows what files/directories uses, doesn't it?
The best solution would be to prefix all files/directories (wsn_)
Especially for new webmasters, who won't think to check first the zipped file for file/directory names they already have (admin, templates..), before they use the installer.
Comments on Major installer problem
Experienced
Usergroup: Customer
Joined: Feb 22, 2004
Total Topics: 47
Total Comments: 88
I tried to install the 4.1.69, not in the wsnlinks subcategory like the script suggested, but on root where i wanted it.
I entered as db-prefix a name with two dashes. The installer stopped saying that this is not possible and then automatically deleted the entire installation. In this case wiped the entire domain, with all the other scripts i had installed, thank god nothing important.
You should change this immediately, before someone loses something important.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
You had other scripts in subdirectories of your WSN install location? Disabled the deletion... but this creates an alternate problem, since you can't properly reinstall until you remove the old install. I could save any subdirectories, but then you might be putting other scripts in files.
Experienced
Usergroup: Customer
Joined: Feb 22, 2004
Total Topics: 47
Total Comments: 88
Yes, when the directory is the main site, all other scripts go into subdirectories.
In this case, I think the best solution is to delete only the files/directories that the script uses. The script knows what files/directories uses, doesn't it?
Experienced
Usergroup: Customer
Joined: Feb 22, 2004
Total Topics: 47
Total Comments: 88
The best solution would be to prefix all files/directories (wsn_)
Especially for new webmasters, who won't think to check first the zipped file for file/directory names they already have (admin, templates..), before they use the installer.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The script knows what files/directories uses, doesn't it?
Only if I waste hours generating a list of them and make sure it gets updated.
The best solution would be to prefix all files/directories (wsn_)
People would really hate those URLs, and not having an index.php would be a disaster.