Jump to:
| Project: | lm_paypal |
| Version: | 6.x-1.0 |
| Component: | LM Paypal Base |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
This is related to a bug that has had a fix committed, but not included in a release.
The original issue is here: http://drupal.org/node/356435
I posted my inquiry there but since the issue is closed I do not think anyone will see it and the "status" description tells me that I should start a new issue instead of un-closing the fixed one. Marking this as critical as receiving IPNs seems like a critical function of the module.
Here is my question (edited to make more sense):
Hello, this bug (http://drupal.org/node/356435) is causing my IPNs to fail to load on my production site that I took to D6 from D5. I see that a fix has been committed, but there has not been a release since the fix in April. I imagine that if I upgraded to the 6.x-1.x-dev version I would pick up the fix, but am hesitant to use a dev version on a production site. Am I safe to just manually apply the changes in the patch? I want to be able to successfully install the next release when it comes along. I guess I could turn it back?? Please advise. Thanks!
Comments
#1
I think you should be fine applying the patch.
Both the developers are very very busy with other things, and cannot support LM Paypal at this time.
#2
Yes, that is what I was thinking too. I applied the patch last night to a local copy of the website and it went fine. I just applied it to the live site and it seemed to succeed (we will have to wait for an IPN to be sure :)
My only remaining thought is what happens when a release comes along. I suppose nothing with respect to this change. update 6002 has been performed so when i go to update next it will just skip it.
Thanks for your support. It is greatly appreciated. No need to reply unless you feel I have it wrong.
#3
Automatically closed -- issue fixed for 2 weeks with no activity.