Hello and welcome to our community! Is this your first visit?
Register
Enjoy an ad free experience by logging in. Not a member yet? Register.
Results 1 to 4 of 4
  1. #1
    New Coder
    Join Date
    Nov 2010
    Posts
    49
    Thanks
    7
    Thanked 0 Times in 0 Posts

    Website Login System

    I want to build a simple (but effective) front-end website which will enable people to download additional content (such as software and manuals) for our website. I'd also need a back-end for me to be able to modify the data.

    I'm not overly experience with PHP/MySQL so I wonder if anyone knows where I can start? The site will use an existing layout but will be www.mydomain.com/customers. The customer will then login and have access to all the info and data they need. Also what about using SSL?

    I'd appreciate any ideas/advice, or maybe even a book I could go and buy???

    Thanks guys.

  • #2
    Senior Coder
    Join Date
    Jun 2008
    Location
    New Jersey
    Posts
    2,546
    Thanks
    45
    Thanked 259 Times in 256 Posts
    There's really no need to buy a book on this: googling 'PHP login system' will give you plenty of guides to get you started.

    But before that, I would recommend just googling for tutorials on PHP basics (I recommend against W3Schools, even though that will be near if not at #1 for most searches, I much prefer NetTuts and random blogs), and basics on MySQL (again, avoid W3Schools IMO).

    Once you get a decent understanding of the basics, try to build a system that allows someone on a page to upload/save content to the system (db and files), essentially your admin panel. Then go for the login system, looking into cookies vs sessions, etc.

    SSL isn't really necessary here if its a basic login system and you aren't transmitting secure information (like credit cards, etc). You can get an SSL certificate if you want, but I wouldn't bother to start.

  • #3
    New Coder
    Join Date
    Nov 2010
    Posts
    49
    Thanks
    7
    Thanked 0 Times in 0 Posts
    Quote Originally Posted by Keleth View Post
    There's really no need to buy a book on this: googling 'PHP login system' will give you plenty of guides to get you started.

    But before that, I would recommend just googling for tutorials on PHP basics (I recommend against W3Schools, even though that will be near if not at #1 for most searches, I much prefer NetTuts and random blogs), and basics on MySQL (again, avoid W3Schools IMO).

    Once you get a decent understanding of the basics, try to build a system that allows someone on a page to upload/save content to the system (db and files), essentially your admin panel. Then go for the login system, looking into cookies vs sessions, etc.

    SSL isn't really necessary here if its a basic login system and you aren't transmitting secure information (like credit cards, etc). You can get an SSL certificate if you want, but I wouldn't bother to start.
    Hi Keleth,

    Thanks! I did begin watching a video on NetTuts and it seemed quite useful.
    The system wouldn't be transmitting credit card data but it may contain broad personal details such as a customer name, address and telephone number and/or email address (so they can request a new password etc).

    When they login they will see details of items they have bought from us (a bit like an after-sales thing) and then clicking on that item will give them the relevant downloads for that item etc.

    As for the primary key, I would like to use the lead numbers from our existing PC-based database, although not every contact on there will have access to this section of the website, so can I create custom primary keys that don't auto-increment?

  • #4
    Senior Coder
    Join Date
    Jun 2008
    Location
    New Jersey
    Posts
    2,546
    Thanks
    45
    Thanked 259 Times in 256 Posts
    Well, unless you have to keep your clients confidential, people don't generally bother with SSL if its common information like names, addresses, etc. Now mind you, the security conscious will go ahead and secure that anyway, and I applaud them for it, SSL just costs a bit, and is a bit harder to work with.

    As for keys, yes. Learn from my mistakes on that one I always used to use an auto_incremented primary key, even when a natural key existed in my data (such as an address if you're only allowing one user per location or if you have a table of votes, you can only have one vote per user per question, so you have an obvious natural key there). Use an auto_increment key if no natural key exists or the natural key is too inconvenient to use (usernames will be unique, but given they might change, be deleted, etc, don't make the best primary key). Since you already have unique data to use as a key, it only makes sense to use that.


  •  

    Posting Permissions

    • You may not post new threads
    • You may not post replies
    • You may not post attachments
    • You may not edit your posts
    •