Jump to:
| Project: | lm_paypal |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
hey all
we are using an older version of 6.x-1.x-dev, from Nov 30 2008 (most recent files are actually datestamped Nov 29). many custom modifications have had to be made, to suit our application, and i am well aware that i will have to integrate these manually when i upgrade. that's ok, i know how to do that, and that's not the problem.
my question: how stable is 6.x-1.x-dev from Apr 8 2009? if i want to upgrade, should i be using this? or is it better to upgrade to 6.x-1.0 from Jan 3 2009?
we are not upgrading "just for fun", or for any specific new features... instead it's in attempt to solve the bug reported in this thread: http://drupal.org/node/591712 which is really the ONLY issue we are having with this code, it's stable otherwise.
cheers,
Peter 'Fish' Fisera
GoatVirus Technologies
http://goatvirus.com/resume
Comments
#1
To be honest, neither of the current maintainers have had much time for this module in about a year (we're too busy paying the bills, I suspect). I don't know why you could be experiencing that other bug (I commented there), but I don't know of a specific fix that would address it (other than, perhaps, the UID>65000 issue).
There haven't been too many changes in the 6.x-1.x branch - you can use the cvs browser to see in the 6.x-1.x branch, and perhaps apply these as a patch to your system.
#2
update on this issue: please see http://drupal.org/node/591712#comment-2254666
my conclusion at this point: LM Paypal IS stable, and worth using!
#3
ps: maybe try the 6.x-2.x version if you are starting from scratch... we are still using 6.x-1.x, there were so many customizations made it would be a bit of a task for us to switch to the 2.x, though maybe one day we will anyhow.
#4
@goatvirus -- lm_paypal 1.1 will be released in the next few weeks. I'm looking to fix the bugs that have been reported here over the last few years and push the feature requests off to the 2.x branch. I'm in the thick of triaging the 1.x issue queue now.
If you are still using the 1.0 version, you may want to track the 6.x-1.x-dev on a non-production server to ensure the 1.1 release upgrade is a smooth one.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.