Per this issue - http://drupal.org/node/996940, could you please clarify a few things?

Products can have classes, attributes, features to make them [apparently] just like subscription products.

Then there are subscription/recurring products which can be made [apparently] similar to products.

Yet, products have descriptions and don't show in subscriptions interface even it they have classes, attributes, features, etc. of a subscription/recurring.

And, recurring/subscription products are different content types, which DO show in subs ui, with no descriptions, with the same end result (or close) as products with classes, attributes, features, etc.

Can you please give us some clarity as to why:

Is there two different content types?
What is the best method?
Should we simply add body field to subs products?
Do products with classes get treated the same ways as subs products?
Does cron trigger both, or payment gateway?
Does both get treated same at checkout, e.g. rules, conditions, etc?

Thank you

Comments

IWasBornToWin’s picture

IWasBornToWin CreditAttribution: IWasBornToWin commented

The documentation for this module shows great information for using products. So I'm wondering where the difference, or added value to the subscriptions ui, product type, etc. are beneficial...thanks.

jsibley’s picture

jsibley CreditAttribution: jsibley commented
Issue summary: View changes

I find it confusing to have the option of a recurring non-shippable product as well as a subscription.

It seems as though I get error messages when attempting to use subscriptions that I don't get when creating a recurring product.

So, is it worth fixing the errors in subscription? Can anyone describe any pros and cons of using one approach or the other?

Also, is there a third option that involves a recurring class vs adding a recurring as a feature?

Thanks.