crazywolf2010
asked on
Drupal Billing Module
Hi,
I am developing a drupal 7 based CRM website. A client wants to charge end user for site usage.
I have used following Drupal modules
1. Drupal Webform for creating landing pages, contact forms
2. Drupal Forum to build a community
3. Drupal Blog to create blog pages
4. A content based download module
A free user will able to use 1 landing page + 1000 hits to this page, 100 forum posts, 10 blog pages + 1000 hits to this page and 100 MB of content hosting like images,videos.
Is there a drupal module to track user usage on these modules and restrict user to specified profile limits?
Thanks
I am developing a drupal 7 based CRM website. A client wants to charge end user for site usage.
I have used following Drupal modules
1. Drupal Webform for creating landing pages, contact forms
2. Drupal Forum to build a community
3. Drupal Blog to create blog pages
4. A content based download module
A free user will able to use 1 landing page + 1000 hits to this page, 100 forum posts, 10 blog pages + 1000 hits to this page and 100 MB of content hosting like images,videos.
Is there a drupal module to track user usage on these modules and restrict user to specified profile limits?
Thanks
There currently is no module that is really even close to what you are describing to the best of my knowledge. I believe you will need to custom-code this.
ASKER
Will this help ?
https://drupal.org/documentation/modules/statistics
https://drupal.org/documentation/modules/statistics
Not terribly well, unfortunately. The table structure they employ really isn't meant for keeping every record since the beginning of time for any site you might expect moderate traffic on. It also has absolutely no restrictions on access, e-commerce integration (with either ubercart, commerce, or anything else), any concept of roles, or any API to easily get data in or out of it in a clean manner, but I suspect you know this already.
What you effectively described in the OP is a form of a pay-wall, and by definition, it is somewhat challenging to build a system that can store that volume of data, be very responsive (remember, your access log dataset will only grow, so searches will only get slower), and be as solid as possible. If you do a google search for "Drupal paywall", you will find pretty much the same information.
What you effectively described in the OP is a form of a pay-wall, and by definition, it is somewhat challenging to build a system that can store that volume of data, be very responsive (remember, your access log dataset will only grow, so searches will only get slower), and be as solid as possible. If you do a google search for "Drupal paywall", you will find pretty much the same information.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.