Version: 1.00, by insanctus
Developer Last Online: May 2006
Version: 3.0.0
Rating:
Released: 05-06-2004
Last Update: 03-22-2005
Installs: 109
No support by the author.
What this does (added in first post)
With the current vbulletin subscription set up, it only charges your members one time. So if you have a pay based site, or forum area they have to keep subscribing, and causing them to waste time and effort (and maybe you lose money)
What this does, is give you the option if you want one time payment (standard vb) or reoccurring payment.
When you choose reoccurring the script has them sign up for a reoccurring payment, as paypal sends you confirmation each time you get a subscription payment, your system will now update their access time.
This will save your members from having to resign up all the time and hopefully save you some money
For instance, say you have a paying member?s only area, and you want them to have to pay $10 a month.
With this you can charge per month and it handles all the charges, and every month they send another payment automatically your script gets updated and sets their new expiration.
This has been asked for many times and IMO should have been in to begin with.
Enjoy and I will help as I can.
Note from the new supporter: This hack is now being actively supported again. I have updated the install instructions to work for version 3.0.7, and we can now begin to work out any existing bugs. This code is still raw and has not been tested extensively due to the difficult nature of testing paypal transactions.
Due to the criticality(sp?) of the release of version 3.07, and the fact that we were still running 3.03, I went ahead and upgraded this afternoon. This is one of only two hacks that I needed to reapply and they have modified the original code for the includes/functions_subscription.php file so that now the hack instructions are no longer valid. There is no
Quote:
function construct_payment($method, $cost, $currency, $subscriptionid, $title, $userid)
{
global $vboptions;
to replace any more.
I'll go back through this thread and see if this may have happened for releases 4-6, but until then (as I am not a decent coder lol) I am here to plead for help!
Due to the criticality(sp?) of the release of version 3.07, and the fact that we were still running 3.03, I went ahead and upgraded this afternoon. This is one of only two hacks that I needed to reapply and they have modified the original code for the includes/functions_subscription.php file so that now the hack instructions are no longer valid. There is no to replace any more.
I'll go back through this thread and see if this may have happened for releases 4-6, but until then (as I am not a decent coder lol) I am here to plead for help!
I had the same proble myself, but after looking through the functions_subscriptions.php file, the update just changed the variable $userid to $userinfo.
I had the same proble myself, but after looking through the functions_subscriptions.php file, the update just changed the variable $userid to $userinfo.
I've got this hack installed and when the subscription is about to end vBulletin sends an email letting that user know their subscription is about to expire, however now mine sends out about 20-30 emails to that user.
Has anyone successfully got this working with 3.0.7 and if so, would you be so kind as to detail how you possibly completed the task? I as well as many others would appreciate it very very much .
This does work with 3.0.7 with one minor modification.
Open /includes/functions_subscriptions.php
Find
Code:
function construct_payment($method, $cost, $currency, $subscriptionid, $title, $userid)
{
global $vboptions,$DB_site;
Replace With
Code:
function construct_payment($method, $cost, $currency, $subscriptionid, $title, $userinfo)
{
global $vboptions,$DB_site;
It's a simple variable change from $userid to $userinfo
Confirmed...works just fine in 3.0.7
The only thing I saw there Apophis that was different in the function construct_payment from the original code was the addition of $DB_site;
My original mistake was putting too much info in the Find bit so it couldn't find the doggone statement. As soon as I just used the keyword "payment" it took me right there. That's why I was freaked out earlier! hehe I thought the original statements for that paragraph may have changed....it didn't...I just couldn't find the bugger! lol
Oh...also... I tried changing from $userid to $userinfo and back again, and it seemed to make no difference. It was that $DB that made the difference.
Overall...I am very pleased that with just this, the SMTP hack, and "How many posts since last visit" one, our boards have all the features and functionality that we used to have to apply 10 or more hacks to achieve! This leaves room for the "would be nice ...but not critical" enhancements if I so choose. *Hats off to dem dere VB developers man*