Partly my fault. I forgot to backup my database after converting from 3.02 to 3.24. I was getting some odd stuff so I thought I'd go ahead and reset everything.
Well, now I query wsnlinks_settings and it is empty.
I am in need of a manual way to repopulate the settings table.
Nevermind, I got the queries out of the setup.sql file and inserted them manually, replacing where necessary.
The reason it happened was because I removed the setup.* files. I don't like to keep setup files on my system since they can be abused. It might be a good idea to make a note that setup.sql should NOT be deleted. I didn't see it noted anywhere in the docs, and if it was, it wasn't clear.
I can't make a manual entry saying "don't delete index.php, don't delete comments.php, don't delete [list of every file]"... it'd be confusing and a little absurd.
It is impossible to run setup without knowing the database info, as you can see for yourself (try this forum's https://www.webmastersite.net/forums/setup.php ). If somebody knows your database info, well, you have worse problems than them running setup.
If I were to rate potential security issues, setup.php would be at the bottom. config.php would be at the top as if it's inside your web root it can give away your database info if your server's apache install has a certain kind of problem when it's being altered or upgraded and the like and something goes wrong (hence the manual entry on avoiding that potential issue).
0/5
1
2
3
4
5
This thread is closed, so you cannot post a reply.
Comments on "Panic" restore blew away my settings
Usergroup: Customer
Joined: Jul 17, 2003
Total Topics: 39
Total Comments: 100
Partly my fault. I forgot to backup my database after converting from 3.02 to 3.24. I was getting some odd stuff so I thought I'd go ahead and reset everything.
Well, now I query wsnlinks_settings and it is empty.
I am in need of a manual way to repopulate the settings table.
Regards
Nigel
Usergroup: Customer
Joined: Jul 17, 2003
Total Topics: 39
Total Comments: 100
Nevermind, I got the queries out of the setup.sql file and inserted them manually, replacing where necessary.
The reason it happened was because I removed the setup.* files. I don't like to keep setup files on my system since they can be abused. It might be a good idea to make a note that setup.sql should NOT be deleted. I didn't see it noted anywhere in the docs, and if it was, it wasn't clear.
Regards
Nigel
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
I can't make a manual entry saying "don't delete index.php, don't delete comments.php, don't delete [list of every file]"... it'd be confusing and a little absurd.
It is impossible to run setup without knowing the database info, as you can see for yourself (try this forum's https://www.webmastersite.net/forums/setup.php ). If somebody knows your database info, well, you have worse problems than them running setup.
If I were to rate potential security issues, setup.php would be at the bottom. config.php would be at the top as if it's inside your web root it can give away your database info if your server's apache install has a certain kind of problem when it's being altered or upgraded and the like and something goes wrong (hence the manual entry on avoiding that potential issue).