One of the problems with technical writing is that the instructions you provide will eventually become outdated. Some details, such as the fundamentals of a programming language like C, Ruby, or PHP, change relatively slowly. Others, like libraries, frameworks, and browsers, change frequently. And so, it was not surprising to find out that PayPal changed some of their systems a while back in a way that will affect readers of my “Effortless E-commerce with PHP and MySQL” book. This issue first appeared last summer in my support forums, with Sean and Michael discovering the problem and the solution.
Continue Reading...Archives For paypal
In this edition…
- On the Web => Follow Me on Twitter!
- On the Web => Facebook and MySQL
- On the Web => 99Designs Contest for My Logo and Business Card
- On the Blog => Autographed Copies of “Modern JavaScript: Develop and Design” Now Available
- On the Blog => Using PayPal’s WebSite Payments Pro with “Effortless E-Commerce with PHP and MySQL”
- Q&A => Does It Make Sense To Use a Code Generator?
- Larry Ullman’s Book News => “Modern JavaScript: Develop and Design” and “PHP 5 Advanced: Visual QuickPro Guide” (3rd Edition)
In Part 3 of my “[intlink id=”1578″ type=”page”]Effortless E-Commerce with PHP and MySQL[/intlink]” book, I use Authorize.net to process payments for a site that sells physical goods. Authorize.net accepts credit cards and can be directly integrated into your site, so that the customer never leaves (unlike, for example, PayPal’s Website Payments Standard, used in Part 2 of the book, which goes through PayPal’s site). The code in the book was written in a very modular style, with the intent that you can use the components you need, and swap others in and out. A reader specifically wanted to know how you would use PayPal’s Website Payments Pro instead of Authorize.net, and that’s what I’ll explain here. Continue Reading…
