Yeah......
Let me see if I can figure this one out again.
All this stuff is hard coded, some in odd places. (hopefully this is one of the 'upgrades' in the next release, and why it's taking so long).
This is a pretty major hack. Are you not planning to upgrade to the 2.0?? <G>
There is no way this is going to a portable modification.
With the current speculation on the new authentication routines, what information is going to be stored in the users table is open.
If there is going to be a good/full users table, then all that needs to be stored in the "link" is an "owner".
The problem is that the "contact" information for the public link, may not be the owner information. For instance, many sites have an "admin" type person that handles the accounts, and placements (or a sales or pr person) and the "contact" name goes to Info, Support, Feedback or some other address.
Everyone has done different things with their sites. Not all 'links' contain the same sort of information, or serve the same purpose.
For _ultimate_ flexibility, there should be a User table, with all the auth data, and the 'user' owns the link. In the link, some sites may want to list the contact info. This may or may not be different from the 'owner.'. The program should be smart enough to check the 'contact' information slot, and if there is no email address there, then use the 'owner' information.
The admin routines (or modify routines) could do the 'fill-in' for you if the user checks the box "make contact info same as admin". Some sites may not want contact information displayed, or used in the listings. A global "turn off contact information" can be used in the Links.pm file, or for sites with an "optional" contact information a check box to "not display" contact information with the link.
I'm actually thinking about this, since I'm working on a newsletter mod. Because of the changing nature of Links with the next release, this will be an external mod, that I hope can be turned into a "plug-in" when the release comes out.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
Let me see if I can figure this one out again.
All this stuff is hard coded, some in odd places. (hopefully this is one of the 'upgrades' in the next release, and why it's taking so long).
This is a pretty major hack. Are you not planning to upgrade to the 2.0?? <G>
There is no way this is going to a portable modification.
With the current speculation on the new authentication routines, what information is going to be stored in the users table is open.
If there is going to be a good/full users table, then all that needs to be stored in the "link" is an "owner".
The problem is that the "contact" information for the public link, may not be the owner information. For instance, many sites have an "admin" type person that handles the accounts, and placements (or a sales or pr person) and the "contact" name goes to Info, Support, Feedback or some other address.
Everyone has done different things with their sites. Not all 'links' contain the same sort of information, or serve the same purpose.
For _ultimate_ flexibility, there should be a User table, with all the auth data, and the 'user' owns the link. In the link, some sites may want to list the contact info. This may or may not be different from the 'owner.'. The program should be smart enough to check the 'contact' information slot, and if there is no email address there, then use the 'owner' information.
The admin routines (or modify routines) could do the 'fill-in' for you if the user checks the box "make contact info same as admin". Some sites may not want contact information displayed, or used in the listings. A global "turn off contact information" can be used in the Links.pm file, or for sites with an "optional" contact information a check box to "not display" contact information with the link.
I'm actually thinking about this, since I'm working on a newsletter mod. Because of the changing nature of Links with the next release, this will be an external mod, that I hope can be turned into a "plug-in" when the release comes out.
http://www.postcards.com
FAQ: http://www.postcards.com/FAQ/LinkSQL/
