Like you, I spent some time trying to avoid this obfuscation for my users but had no luck -- obviously, Paypal has set it up that way on purpose to encourage Paypal usage. Not nice of them especially since a lot of my users are from an older demographic less savvy about Paypal/Web and less able to notice the little link allowing them to use a credit card. They get confused.
Seperately, from the recesses of my brain here's one more little "tip" if you adopt the plugin -- the plugin can override most any setting that you can set on the website. So, for example, if you change your ipn redirect url or anything in your "profile" on the website it will have no effect if you've also set it in your call from the rails app. I recently switched my site from http to https and couldn't figure out why PayPal kept sending my IPNs and PDTs to http even though I instructed https on the website. The answer was that I had forgotten that I was overriding the website with my orginal call from my app. -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
