Roelof,

If im reading this phrase right "a client comes to the counter " , the end
client does not login right ? Then all you have to do is use the same
ecommerce solution and let your staff "impersonate" your clients .

Look at this https://github.com/rcook/user_impersonate2 gem.

On Tue, Dec 23, 2014 at 2:08 PM, Roelof Wobben <[email protected]> wrote:

> I can do that but most of the gems I see are working with the fact that
> the person who is logged in is also the person which "owns" the shopping
> card. With me that is not true.
> So I try to find a way to resolve that problem.
>
> Roelof
>
>
> Op dinsdag 23 december 2014 08:33:41 UTC+1 schreef Vivek Sampara:
>
>> Hi ,
>>
>> Instead of implementing it from scratch try to include any ror ecommerce
>> gems and let it handle the cart and sessions. i personally like the
>> simplicity of piggybak <https://github.com/piggybak/piggybak> .
>>
>> Cheers
>>
>> On Tue, Dec 23, 2014 at 12:33 PM, Roelof Wobben <[email protected]>
>> wrote:
>>
>>> Hello,
>>>
>>> I have this situation.
>>>
>>> I m a volunteer on a toy library and I want to write a financial /
>>> borrow app for the toy library.
>>>
>>> Now I have two seperate roles : staff member and client.
>>>
>>> Staff member can log in and put things into the system.
>>>
>>> Client is not allowed to do anything in the system.
>>>
>>> Now I try to make it work in a sort of ecommerce site, where the
>>> shopping cart is the place I want to keep track of what the client borrows.
>>>
>>> So my staff member logs in, a client comes to the counter to tell that
>>> he wants to borrow a toy-car.
>>>
>>> Then the cart of that client must contains the toy-car.
>>>
>>>
>>> How can I achieve this  with sessions or another way ?
>>>
>>> Roelof
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "Ruby on Rails: Talk" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to [email protected].
>>> To post to this group, send email to [email protected].
>>> To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/rubyonrails-talk/b367bc31-2f9f-4e5e-8c56-
>>> 56bbf1fb74a4%40googlegroups.com
>>> <https://groups.google.com/d/msgid/rubyonrails-talk/b367bc31-2f9f-4e5e-8c56-56bbf1fb74a4%40googlegroups.com?utm_medium=email&utm_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "Ruby on Rails: Talk" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/rubyonrails-talk/3b782a6f-2882-4c95-94d9-879ad755a2a2%40googlegroups.com
> <https://groups.google.com/d/msgid/rubyonrails-talk/3b782a6f-2882-4c95-94d9-879ad755a2a2%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/rubyonrails-talk/CAFKVRj856fsFUDg7O2MiMf3%2BP%3DR1gu6OE90KnM98FLa41ir1Hg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to