3 replies [Last post]
Sansui's picture
Offline
Joined: 06/05/2008
Juice: 154
Was this information Helpful?

I'm trying to figure out if there's a way that after completing checkout, a user can be promoted to a new level that I've set to allow access to other products + other content on the site. Is this easily doable with the workflow module?

The idea now is that a user can register on the site at the basic level, and I'm using protected nodes to allow only access to this one CD seminar. Once the seminar is purchased, they're allowed full membership into the site.

Suggestions? Thanks for your help in advance Laughing out loud

Ryan's picture
Offline
Joined: 08/07/2007
Juice: 15438
Re: Granting member access after purchase?

I'd start with the docs for selling site access and post any follow-up questions back in this thread. Smiling

Sansui's picture
Offline
Joined: 06/05/2008
Juice: 154
Re: Re: Granting member access after purchase?

It's quite possible you are awesome Laughing out loud

I love the fact you guys actually have some great and well organized documentation, shame on me for not hitting that up first! It's what made my first install so simple. Thanks again

kentr's picture
Offline
Joined: 07/18/2009
Juice: 27
Selling site access: questions / comments

Nice module and cart!

Some questions & comments:

  • Has the Role assignment settings form at Administer › Store administration › Configuration > Product settings > Product features changed? In mine, the Order Status field is missing. I'm guessing this is now in Conditional Actions...
  • Are default role predicates created automatically? What mechanism creates them? I'd like to know how to trigger their creation consistently in the future. I ask because at first, I didn't see one for granting roles and attempted to create my own. Then I went back to the conditional actions overview and saw the predicate I created plus an additional one that I was unaware of.
  • In the predicate that I discovered, there was an Order Status condition as well as Order Status fields on the Actions form. At first glance, this looks redundant. What's the difference in use between these parameters?
  • Suggestion: For less confusion when manually creating predicates, change the title for the action to "Grant / renew purchased roles" instead of "Renew purchased roles" and the category to "Roles" instead of "renewal".

Thank you.