[CLIENT LOGIN]: Howto?

Primary tabs

6 posts / 0 new
Last post
paul.w's picture
Offline
Joined: 6 Sep 2007 - 4:26pm
[CLIENT LOGIN]: Howto?
0

My portfolio is undergoing some heavy changes, with a complete revamp estimated to be complete within the next month. One thing I've been asked by a client of mine is a page where they can actually log in and view progress on work being undertaken for them, which is easier said than done but I can definately imagine the benefits.

After continual searching on Google and indeed our own forum, I've been unsuccessful in finding any relevant information about creating such a system.

If any of you know of a decent resource with a tutorial or otherwise, and can indeed gauge the difficulty of setting up such a service with limited coding knowledge, I'd love to hear from you.

Regards,

Paul

Tomi K.'s picture
Offline
Joined: 22 Sep 2006 - 12:38pm
0

I would suggest using simple htaccess method. Here's a quick tutorial: http://www.besthostratings.com/articles/password-protection.html..

Using .htaccess is very simple. You don't even have to create a login page, because the browser will popup a login dialog, in which you can fill out name and password.

Mili Carr's picture
Offline
Joined: 17 Jun 2005 - 1:36pm
0

This may not be quite what you're looking for. The system is in use in some Finnish advertising agencies. The designer post a pdf for the client to review, the client can then make comments to it online. The history of comments stays in the archives.

http://www.kommentoi.com/content.asp?lang=eng

Dan Hall's picture
Offline
Joined: 13 Oct 2005 - 2:40pm
0

I'm going to look into the suggestions above. The method I have been using is very simple. I just create a directory for the client and email them the address to the file...

www.domain.com/proofs/client/filename.pdf
or
www.domain.com/proofs/client/filename.jpg

It's not secure, but without the filename no one is going to find it. And for my work it wouldn't matter if they did.

darrel's picture
Offline
Joined: 4 Feb 2003 - 6:03pm
0

There are dozens of way to handle this. The quickest is likely the htaccess method (if you are on an Apache server). Give each client a folder and password protect each folder.

The ones where a client logs in on the home page would be applications written in PHP or ASP.net or RoR or the like.

paul.w's picture
Offline
Joined: 6 Sep 2007 - 4:26pm
0

Thanks for the advice guys, some pretty intuitive suggestions which I'll take under consideration. I'm thinking I'll go with the htaccess method to display a knowledge of extra-curricular coding (I'm currently a student and our portfolios are graded by lecturers on a quarterly basis) so I appreciate the insight.