http://drupal.org/sandbox/farald/1406994 (Drupal 7 only)
This module enables commerce to sell copies of existing nodes.
- Admin activates a node reference field for usage by this module by editing its field preferences.
- Admin creates one or more product that refers to one or more nodes that should be copied.
When this product is bought & paid for, a rule is fired that performs the actual copying of the node.
The module is an attempt on creating a simplified system for selling nodes, to allow for totally customized nodes.
Project is somewhat similar to Commerce Node Checkout, but differs in the way nodes are handled. In Commerce Node Checkout, nodes are created before added to cart, and then programmatically added to order. Node is then published on purchase complete.
In this approach, the Admin creates a default node & adds it to a product.
Good thing about this approach is that you can have an advanced node structure with hidden fields etc that determines how the node is handled in the system. No need for fancy configuration, just create a node and reference it on the product.
See sandbox page for more info on usage.
Reviews of other projects:
Enityconnect
ShrinkSections
Commerce add to cart popup
Going Down
Commerce Moneris
Comments
Comment #1
eugene.ilyin commentedHello. I spent a Review of your module.
ventral.org/pareview is not work now and I did it manualy.
if (is_array($line_item->{$field_name})){
$node = node_load($nid,null,true);
Comment #2
farald commentedThanks, cleaned out those coder issues.
Comment #3
Robertas commentedIt appears you are working in the "master" branch in git. You should really be working in a version specific branch. The most direct documentation on this is Moving from a master branch to a version branch. For additional resources please see the documentation about release naming conventions and creating a branch in git.
The following git branches do not match the release branch pattern, you should remove/rename them. See http://drupal.org/node/1015226
Review of the master branch:
This automated report was generated with PAReview.sh, your friendly project application review script. You can also use the online version to check your project. Get a review bonus and we will come back to your application sooner.
Source: http://ventral.org/pareview - PAReview.sh online service
Comment #4
farald commented- Added readme files
- Used http://ventral.org/pareview to remove the errors.
- Removed files from master.
Comment #4.0
farald commentedSome modifications for clarifying purpose.
Comment #4.1
farald commentedAdded reviews
Comment #4.2
farald commentedNew review.
Comment #5
farald commentedTagging, in reference to #1410826: [META] Review bonus
Comment #6
farald commented+Commerce related.
Comment #7
klausimanual review:
But that are just minor issues, otherwise looks RTBC to me. Removing review bonus tag, you can add it again if you have done another 3 reviews of other projects.
Comment #8
patrickd commentedjust to get a little more picky :P
I've tested it's functionality with commerce kickstart and it works good
But the usage instructions could be a little better.
I don't think there are any relevant security aspects..
So, also from my side this can be fixed.
Comment #9
patrickd commentedAs said in #8 I agree with klausi that this is ready-to-go.
Thanks for your contribution, farald! Welcome to the community of project contributors on drupal.org.
Don't forget to have a look at the non-blocking issues noted above.
It also seems to me that you're not correctly authenticated to git (have a look at the git instructions page on your project page for more info).
I've granted you the git vetted user role which will let you promote this to a full project and also create new projects as either sandbox or "full" projects depending on which you feel is best.
Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.
As you continue to work on your module, keep in mind: Commit messages - providing history and credit and Release naming conventions.
Thanks to the dedicated reviewer(s) as well.
Comment #10.0
(not verified) commentedNew review