This is based on discussions around the office as well as a re-read of the use cases thread.

This new feature would be able to coexist with the site feature on the same product, and would need to be migrates to reflect the new target platform for new sites. It would let people easily develop products like 'an OpenAtrium site' or 'a Drupal Commons site' without having to mess around with product kits.

Ultimately, it would replace the existing platform access feature.

Comments

sfyn’s picture

sfyn commented
Title: Replace "platform access" with a profile and platform binding feature » Let site products have predetermined profiles and platforms

So people have indicated to me that they need the platform access so I will leave it in, and instead, simple add this possibility to the site feature.

hadsie’s picture

hadsie commented

Hey @sfyn,

Yeah, I like this idea. And I've looked a little bit into making that happen already (though that was some time ago now), since it's quite a common need. But ya, it may need to be something added in for each feature as opposed to an overall thing (if that's what you were proposing).

sfyn’s picture

sfyn commented
Version: 6.x-1.0-beta3 » 6.x-1.0-beta4
sfyn’s picture

sfyn commented
Status: Active » Needs review

This is done and in the latest release, but, can fairly easily be circumvented if skipping site creation during purchase is turned on.

http://drupalcode.org/project/uc_hosting.git/commit/c88d8556a742

sfyn’s picture

sfyn commented
Version: 6.x-1.0-beta4 » 6.x-1.0

bumping version

sfyn’s picture

sfyn commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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