Support

I love your component ARS and the fact that it integrates with AMBRA Subs this is something we were gearing up to produce ourselves so you saved us a lot of time.

One thing I would like to see added would be a bugfix release option.

Our business model supplies bug fixes regardless of active subscription, if someone bought an extension from us we guarantee it to work and will fix bugs for free, our subscriptions merely cover new features. With that we have to manually send out fixes when we add them, it would be awesome if the item under a particular release could have a bugfix checkbox option which would allow access to the file regardless of active AMBRA group.

How I imagine it working is it would merely check if the user ever had an active subscription for that particular release (maybe verify against the release date and the range in which their subscription was active) it would allow the bugfix update. That way we could keep bugfixes constrained to particular releases.

Possibly, as long as it checks some sort of date in order prevent access to new releases which do not fall within their subscription period. Such as allow subscriptions which expired after the release date.

Every release could potentially have a bug fix which would be set to allow expired subscriptions, if it was too general and only checked for expired subscriptions but no dates someone with a subscription from a year ago could just wait for a new release to get a bug fix and get the update with all the new features using their expired subscription.

Our business model is unique and actually offers more than most companies offer, Which is why we are handling it manually at the moment.

We are on a 3 month release cycle where we guarantee 3 new features each cycle (per product). A feature is something significant like adding a shopping cart to our gift exchange component, or the ability to send gifts to a cell phone as a text, not just a bug fix or css fix.

There's nothing I hate more than having to pay for another month just to get something fixed which should have worked in the first place. I also hate having to pay for support which is how most business models work in a GPL community, so instead we've designed out model to support future development via subscriptions and release cycles.

The idea is that as long as there is interest in the product we will keep adding features and developing the product, the subscriptions mainly support the development of new features, We guarantee bug fixes and support for your particular release cycle(s) for the life of the product.

So if someone pays for a 3 month plan they will get 3 new features + support + bug fixes for as long as the extension is relevant.

What they are paying for is the new development, which is why we need a way to automate the guaranteed bug fixes for the particular feature set, if I have to we'll modify the business model but currently it works very well and everyone is happy, except me when I have to manually send out bug fix updates.