I was just wondering if anyone has ever tried to make this work with a ecommerce type of setup allowing only paid customers into a private chat?

I'm trying to come up with ideas to make a online classroom type of setup for paid seminars. I know Ubercart has a module to pay for online content, but I think it's mainly for down loadable items. I think I'm envisioning something like when a user pays for a seminar, they either get a password to get into a restricted chat, or maybe the get a temporary role that allows them in, or something like that.

Comments

charlie-s’s picture

charlie-s commented

Use the Ubercart "Role" module (comes with Ubercart Core I believe) to make them pay for a role that has Chat permissions.

greggles’s picture

greggles
he/him
Primary language English
Location Denver, Colorado, USA
commented
Status: Active » Fixed

I think the solution by csdco works pretty well, actually.

What do you think, wxman?

wxman’s picture

wxman commented

Sorry. I've been so backed up with this project, I'm for getting to check these.
I looked into using roles, content access, ACL, node access product, node access, and a few others. All to control access to a chat room from the chat room module. Roles worked somewhat, but I need to control the date and time users are allowed to to view a chat room. So far roles offered me the best control for access, other than the time problems. The access control modules should work, but I'm doing something wrong. People can use the chat rooms if they know the address, even if they didn't pay for it. This shouldn't be this complicated, because I know it can be done.
So far, I have a local test site running:
Pressflow 6.20
Ubercart 6.x-2.4
Chat Room 6.x-2.13
Ubercart
and the module I pointed out above.
I might get around some of the time problems by using scheduler to turn the chat room on/off at the specific times. That way uses could pay for a days access, but they can't use it till it's published.
If others have ideas, I would love to hear them.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.