www.webdeveloper.com
Results 1 to 4 of 4

Thread: Allowing Non Members Use A Service

  1. #1
    Join Date
    Jul 2006
    Posts
    653

    Allowing Non Members Use A Service

    Hi, my site allows my members to create a fundraising page so that they can raise money for their chosen charity.

    The home page of my site has a banner which includes a big 'Create Fundraising Page' button. If a user is logged in, they will be brought to the /create-page section of the site when they click the button, HOWEVER if the user is not logged in, they will be redirected to the /sign-up page.

    I've been asking some of my users for feedback lately and some of those suggested that i should allow a user to start creating their fundraising page regardless if they are signed in or not, which would probably bring a higher conversion rate.

    I don't want to add another status to the Fundraising pages as this would mean that i would need to revisit / adjust a lot of queries around the site to take the new status into account SO i was thinking of adding temp fundraising table that would store the fundraising page details and then move them to the live fundraising table once the user signs in or signs up after they create their mission...

    I need to think how i can relate the user to the temp record so that i can move it to the live table when they sign in / up. I was thinking of using a session which would mean that the user has to sign in / up immediately after creating their fundraising page or else the mission is lost and they would need to start again...

    Can anyone suggest a better method or have any other relevant advice, thanks in advance...

  2. #2
    Join Date
    Jul 2013
    Posts
    29
    PHP session is based on cookies, so you only need to set a cookie that will not expire on browser close but will have a long lifetime, like 1 year or 10 years. Of course cookies will only work if a user later logs in or registers from the same machine using the same browser, but you have no other way to track a person reliably enough.

    Storing projects in temp table is quite a good solution.

  3. #3
    Join Date
    Jul 2006
    Posts
    653
    Ok thanks... what about storing the session in the database?

  4. #4
    Join Date
    Jul 2013
    Posts
    29
    The only thing you need to know about client is his cookie ID. This ID should be present in the record which is put into temporary project table. Why bother running whole session handling mechanism just to save/fetch a single value?

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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



Recent Articles