I have a situation where I want to have subscriptions based on products but allow the subscriber to purchase more than one of the products. The process is: - sign-up for a single product - this allows them to go to a page that lets them create an entry (which gets displayed on the website) - they may then buy a second subscription to this product - when they go to the product page they will see the first one and be allowed to add a second. I guess this will be something based on the count of payments against a product for a given member. Has anyone done this sort of thing where you save the payment reference in the product to enable cross-referencing. Not sure if I am over complicating this, any advice appreciated. Thanks, Ian.
Ian, This is going to be tough to do with aMember. You can configure aMember so that the same subscription product could be bought at the same time, one per transaction. The problem is having aMember control that a person could enter content on a webpage. This sounds more like a classified ad model. I suspect if you looked around you could find specialized software for online classified ads. Good Luck!
Thanks, classified applications are no good as each product is totally different and the information they enter is held in a database, that then drives a dynamic site. I think I have worked a way to do it. When I enter my product page I can count number of payments for a given product and I can then count number of records they have. If payments > records prompt them to add new record, if payment < records then notify them to make a payment. I can also create a simple cron job that does the same and sends out an email warning to all those where payments are less than records - ie. they have ignored renewal.