For the "finish one chapter" part, I don't see the problem. Did you want to lock people down to only one chapter at a time? If so... that can't be done natively as the tool has no concept of chapters, or finsihing, or way to know when you finish one and want to move to the other.

Personally, I wouldn't recommend doing that at all, as people might want to check previous chapters. However, if you want to, then I'd put the user into a master group (with my add-on) and then use something else to manage the chapter group. So Membership addon is responsible for putting them in (and taking them out, after a period of time) the "Student" membership, and then something else is responsible for managing the "chapter 1", "chapter 2", etc groups. I can't think of anything that would be able to this "out of the box", and unless you can request this in a very generalized way that might be more universally useful, I don't think see it being part of the membership addon.

As for recurring payment, no, this isn't currently supported. Users will have to manually re-subscribe.

Get what you mean regards the chapters, would be a sh*t to set up aswell!

That's a shame regards the lack of no recurring payments, is there any plan to add this? I've been really looking for something on C5 to do this and I thought this add-on was the answer, I don't want to do it in WP :(

I'd like to think it'll be released in the next few weeks, but there are no guarantees.

It's actually quite complex to manage, especially the corner cases (what happens when the credit card expires in 6 months? how to deal with reporting? what happens when they buy multiple subscriptions? etc.). And add in the fact that I've got to figure out a standardized way to do this (Paypal and authorize.net and likely the others have different approaches to subscriptions).

Are you using paypal or authorize.net?

If it's really important to you, we can discuss a custom development project, which will be easier and quicker than adding the feature to the package as we can limit the scope to exactly what you need (processor, not all feature, etc).

are you saying an auto recurring subscription payment method is in the works ??

No.

It's on my list, and likely the next feature to be added, but also quite complex to do it right as part of the whole package.

I was hoping that I'd have some downtime to attack it, but that never materialized, and paying projects are backing up.

So, as far as a public feature, it's coming at some point, but I can't say when...

When you say that the user would have to re-subscribe. Do you mean that they would have to enter all their info all over again. Or would it be stored and all they are doing is re-submitting a payment?