Thanks rthrash.
In broad terms, how would I go about protecting the content via a subscription system? Maybe... if I were to use eCart I could put some code to insert the users details into a database on the successful transaction page. The login system would then use the custom table/database to check their subscription status.
Is this a sound way of achieving it?
Basically you need to look at the web usergroup stuff (standard with MODx), add a Subscribers group, and restrict access to just that usergroup.
Ideally, your "payment successful" page would then add the user to the web user group. If you have experience with WA eCart, then use that - you just need to hit the db to put the right stuff in the right tables. You should at the same time save the "Subscription Expiry" date. In the long-term you’re going to need to run a routine daily to remove the privilege from expired subscribers. You’ll also need to be able to *extend* an existing subscription. But at the start all you need to be doing is saving the expiry date so that you have it when you need it.
I’ve done something similar but using Zencart:
The user purchases a product in the Zencart driven store.
When they try to log in as a web user, a custom plugin does the following:
- copies username and password from Zencart to web users - i.e. creating a web user if needed, or just updates password
- checks whether they have purchased the necessary product
- updates a web user setting to show which products they have purchased
I then use the products purchased information to configure their web user groups membership.
In order to make this work I had to change how MODx stores encrypted passwords to match the Zencart system (one uses salt, etc.).
Andy
Thanks for that Andy - appreciate the rundown. WebAssist has a customer registration feature, so I should be able to do a similar kind of thing.
As always, I’m open to any other advice and guidance. Thanks again.