Well, if you are not using the authentication plug-ins like w3t, then you can muck with the links internals a bit more.
I would actually probably do it the simplest way I could, that would survive updates and upgrades with the minimal amount of effort.
That means, put the changes in the add/modify.cgi script, and leave everything else alone.
When the user submits a "new" link, if you have authentication on, you can do one of several things. Modify add.cgi so that if the user exists, they _cannot_ add a new link, they are forced to the modify form, showing their ONE link, where they are advised to create a new user ID if they want to add a new link. If they are not logged in, they are taken to the "log in" form, to either log in, or create a new user ID, so all that stuff doesn't have to be touched. (maybe just put a note that each link must have a separate User ID).
Personally, this is how I would do it. It means only changing add.cgi, using everything else in Links the way it is, and with luck, you'd only have to cut/paste a few lines of code between versions of add.cgi (maybe even be able to use the old version of add.cgi for the most part!).
Make sense for what you want to do?
PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
I would actually probably do it the simplest way I could, that would survive updates and upgrades with the minimal amount of effort.
That means, put the changes in the add/modify.cgi script, and leave everything else alone.
When the user submits a "new" link, if you have authentication on, you can do one of several things. Modify add.cgi so that if the user exists, they _cannot_ add a new link, they are forced to the modify form, showing their ONE link, where they are advised to create a new user ID if they want to add a new link. If they are not logged in, they are taken to the "log in" form, to either log in, or create a new user ID, so all that stuff doesn't have to be touched. (maybe just put a note that each link must have a separate User ID).
Personally, this is how I would do it. It means only changing add.cgi, using everything else in Links the way it is, and with luck, you'd only have to cut/paste a few lines of code between versions of add.cgi (maybe even be able to use the old version of add.cgi for the most part!).
Make sense for what you want to do?
PUGDOGŪ Enterprises, Inc.
FAQ:http://LinkSQL.com/FAQ
Forum:http://LinkSQL.com/forum
