How not to show Add to Cart button to Products already bought???
I am selling files, and I am setting up Commerce File to make it ... it seems working.
When the User goes back to the Product Display of a Product he already bought (with granted license), than the file download link correctly shows up (nice!).
But still there is the Add to Chart button shown in the display for the file product (and this is not correct, as it might make the user buy or add to chart something he has grants to free download ...).
So, how to automatically hide (unactivate) the Add to Cart button for already bought products?
I don't know if this issue has yet been discussed (sorry in this case) ... and solved.
Any help if it is not or how to find the solution?
Thanks so much
Comments
I here attach a more explicit
I here attach a more explicit screenshot ...
I am trying to get more
I am trying to get more through this matter ...
and in the meanwhile that this has something to do with this issue: http://www.drupalcommerce.org/node/673
Feature Request
Itamar -
You might try adding this as a feature request (or perhaps bug report) in the Commerce File issue queue.
John / NEARDARK
Thank you neardark for your
Thank you neardark for your advice, that I am going to follow ...
Just one doubt: is this a concern about Commerce File module or Drupal Commerce itself?
Indicating Previously Purchased Products
That's a good question. I'mg guessing it would be a File module feature, but perhaps a module that tracks previously purchased products by users would be useful for not just file products but other products as well. I'd start in the Files issue queue and see where that gets you though.
John / NEARDARK
Hi, I´m interest in the same
Hi, I´m interest in the same issue pretty much.
Did you find a solution so far?
Kirk
the issue to follow for a
the issue to follow for a solution is http://drupal.org/node/1266132
There is a patch that disables the add to cart form; however, it is not ideal for all cases so the patch needs work
I solved it for my needs, and I shared my personal solution ...
Hi ... I really had to face this in my Drupal Commerce Project, I faced it and so far solved it for my needs, developing a mini/little (but efficient) module that I guess might be more generally applied.
Thus I shared my solution here: http://drupal.org/node/1266132#comment-5672306