Richard Bozman wrote:
Gunnar Hjalmarsson wrote:
Basically there is no reason to password protect the access to the
customized HTML code. I remember that the old WebRing system had a
way to access the code which only required the site ID. I'm
inclined to think that it would be better to do the same thing,
i.e. add a method to access the customized ring code on the web
without logging in.
I disagree, any admin. between the cgi and account owner should be as
is secure from outsiders.
Hmm.. Did you realize that I'm only talking about read access to the
customized code, which is intended to be publicly displayed on the
member site anyway?
What I would really like is the ability to send various emails to a
user from the ring admin. area. Example: test rings response page
del/edit/view/email here or any other emailer button when clicked
would display a list of templates to send this site including no
template. What templates? Welcome, Warning Error in test, Last
Chance Warning, bye-bye, Notice you need to update your code etc.
Selecting this way would use the site id to fill in the [alias
words]. The Customize button could access the email templates same
as customize code module does. The template file name list could be a
var. in config. $template =
("welcome","warn1","warn2","byebye","newcode","thanks","newversion");
I suppose all hard coded emails could be changed to templates with
possible exception of any language specific items. Language needs in
templates would be handled by the template writers own language. Full
use of all the [alias words] in the template text supported.
This would be a real nice convenience for ring leaders for fast and
easy interaction with site owners. A send template "X" to all users
could be also incorporated, example; To all users, we have upgraded
to a new version, please review these new features blaa blaa blaa.
What you suggest is possible, of course. Personally I don't find it
worthwhile trying to convert Ringlink to an email sending tool, since
there are plenty of email clients for the purpose. If you are using a
good email client, you can well store as many Ringlink related templates
in it as you like.
But that's just my view. If somebody who is of another opinion, and has
enough Perl and CGI knowledge to make the necessary code changes, s/he
is welcome to join the Ringlink Project and start working with it.
/ Gunnar