Paypal subscription issue
Permalink Browser Info Environment
I own a license for this component and wanted to submit a ticket but was only offered the discussion option. Please let me know how to submit a formal ticket. Meanwhile problem is this.
A simple form with open payment amount returns this error from PayPal:
Invalid Regular period. You must specify valid values for the A3, P3, and T3 parameters for a subscription.
This should not apply since the payment is for a one time donation and not a subscription at all. I did not see any way to specify this on the form settings.
A simple form with open payment amount returns this error from PayPal:
Invalid Regular period. You must specify valid values for the A3, P3, and T3 parameters for a subscription.
This should not apply since the payment is for a one time donation and not a subscription at all. I did not see any way to specify this on the form settings.
| Type: | Discussion |
|---|---|
| Status: | In Progress |
Hi, would you mind PM'ing me a login to see/edit a demo page?
Sorry, what does PM'ing mean? Do you mean our admin login?
PM'ing means "private message" me.
Extremely frustrated with your lack of response. I inherited this site from a previous admin who installed the component and I may be missing some information. Your response of PM means "private message" is not helpful. Does "private message" refer to a feature on the support site? How do I do it. Should I submit my requests in another fashion? What am I supposed to do here!
(Duplicating this post in case I am replying in the wrong place)
(Duplicating this post in case I am replying in the wrong place)
I'm experiencing an additional problem. Some forms succeed in forwarding to PayPal but do not add the submission to the database or send emails. I sent up an additional test for to test this. It is set to sandbox mode. http://aftm.us/testpage
Attached screen shot file to demonstrate settings.
Attached screen shot file to demonstrate settings.
Having checked the database I see that the form information is added to the tables. But they will not display on the report page.
Still awaiting your reply to my posts.
Extremely frustrated with your lack of response. I inherited this site from a previous admin who installed the component and I may be missing some information. Your response of PM means "private message" is not helpful. Does "private message" refer to a feature on the support site? How do I do it. Should I submit my requests in another fashion? What am I supposed to do here!
I resolved this issue myself with considerable debugging efforts.
The problem we were experiencing in the ipn_listener.php script was due to the incorrect use of the mysql_real_escape_string() function.
Example:
mysql_real_escape_string(trim($receiver_email))
Fix:
$link = mysql_connect(DB_SERVER,DB_USERNAME,DB_PASSWORD,DB_DATABASE);
mysql_real_escape_string(trim($receiver_email),$link);
The first example was failing with a database connection error because, without the second parameter it was using default credentials to attempt the connection. In our case these default credentials were no longer valid,
See description of link_identifier parameter inhttp://php.net/manual/en/function.mysql-real-escape-string.php...
I am not really comfortable with this fix since the mysql_real_escape_string is now deprecated in PHP. I'm also unsure about the security of referencing the database constants in a /tools script. If you can recommend a better solution, please do.
This accounts for the database issues. I'm still looking at the 'subscription' issue, which may be unrelated. If I have further issues with that I'll open a new thread.
The problem we were experiencing in the ipn_listener.php script was due to the incorrect use of the mysql_real_escape_string() function.
Example:
mysql_real_escape_string(trim($receiver_email))
Fix:
$link = mysql_connect(DB_SERVER,DB_USERNAME,DB_PASSWORD,DB_DATABASE);
mysql_real_escape_string(trim($receiver_email),$link);
The first example was failing with a database connection error because, without the second parameter it was using default credentials to attempt the connection. In our case these default credentials were no longer valid,
See description of link_identifier parameter inhttp://php.net/manual/en/function.mysql-real-escape-string.php...
I am not really comfortable with this fix since the mysql_real_escape_string is now deprecated in PHP. I'm also unsure about the security of referencing the database constants in a /tools script. If you can recommend a better solution, please do.
This accounts for the database issues. I'm still looking at the 'subscription' issue, which may be unrelated. If I have further issues with that I'll open a new thread.