-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Darcy Brodie wrote: <snip> > > Although I had purchased this program from a company who claimed it was > written for linux, I would now have to assume that it was actually > written for linux on a dos / windows computer. As soon as I ran > dos2unix on all the cgi programs, all my problems went away. > > I recognize that I could just use .htaccess / .htpasswd to secure the > web page, however, a couple of the features that the organization this > is for wants, is for users to be able to change or retieve their > passwords when they forget them (and they do forget their passwords - on > a regular basis) This program is "supposed" to do that (after all the > hassle that I have gone though, it had better), as well as it has mysql > database backend to it, and I am hoping that I can join the > authentication together between the CMS and the members area of the web > site. > > If it had not been for some documents (primarily PDF files) that the > association want in the members area, I could have used the CMS to > restrict access to certain pages > That sounds exactly like the job a CMS does. Most modern CMSs support the idea of multiple roles and providing content based on the authenticated (or unauthenticated) role.
Something to keep in mind for the future. > Again, thanks for all the suggestions np -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAks6po8ACgkQwRXgH3rKGfPHngCgnQDrNDz1qI9dSUzPmaaMmFOX Ad4Anjz1loB50xbwZXpQUaYCMvFsQd25 =NZbf -----END PGP SIGNATURE----- _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
