Question

I've been installing a twiki for my intranet. I already have a list of login:crypted_passwd:full_name:email_address (the usual ypcat). I've installed TWiki with Kupu (added a "VisualEdit" to every page). I also installed \AuthBasic with a local htpasswd file (but the htpasswd does not give a complete user).

I'm building an engineering website where everybody can edit/view anything as long as they are authentified. (no view if no login). Rather than explaining to all my users that they need to register just to be able to see the webpage and edit the site, I would like to pre-populate the site with complete pre-registration. I also would like to disable self-registration (to avoid doublons).

I probably have to write a perl script that would synchronize some files daily with what is in ypcat.

Could you please give me some pointers on how to implement that ?

Environment

-- GillesEricDescamps - 13 Oct 2004

Answer

I'm near the end of a RegisterCgiScriptRewrite because I have a very similar goal. The code is a bit raw (I want to change the class structure) but it would probably help - I have a register.pm script that it is better modularised than the original register.pl script. The register stuff will now accept a hash of key-vaue pairs and more or less does the right thing with them.

Can you meet me on TWikiIRC?

-- MartinCleaver - 13 Oct 2004

met.

-- GillesEricDescamps - 13 Oct 2004