I am trying to come up with a better solution than having to hand edit every one of my 100+ buttons one by one using the cheezy PP editor which doesn't even allow opening a 2nd tab or anything while editing, every time I need to change prices or shipping cost I have those damnable 100 buttons to edit, there HAS to be an easier way when there's web sites and ebay pages with thousands of items on them that people have to manage payment buttons on, I can't imagine someone hand editing 1,000 prices on 1,000 buttons one by one! I thought, what if you use ONE PP code, and using the "options" drop-down, you have this ONE block of code on each web page maybe using php with an include so only one file is called up to the pages using the regular php tag in the HTML to do so? Most of my web site sales involve people buying ONE item, very rarely do people buy multiples. Let's look at this generated test code for 6 different items before I do a change to it: <form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top"> <input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="A-TEST-NUMBER-HERE-NOW"> <table> <tr><td><input type="hidden" name="on0" value="model number">model number</td></tr><tr><td><select name="os0"> <option value="a">Item 1 $149.00 USD</option> <option value="b">Item 2 $249.00 USD</option> <option value="c">Item 3 $178.00 USD</option> <option value="d">Item 4 $99.00 USD</option> <option value="e">Item 5 $89.00 USD</option> <option value="f">Item 6 $26.00 USD</option> </select> </td></tr> <tr><td><input type="hidden" name="on1" value="Suggested finishes available (default is the LIMESTONE">Suggested finishes available (default is the LIMESTONE</td></tr><tr><td><select name="os1"> <option value= "Limestone ">Limestone</option> <option value="Dirty Nickel">Dirty Nickel </option> <option value="Bright silver">Bright silver </option> <option value="Dirty Bronze">Dirty Bronze </option> </select> </td></tr> </table> <input type="hidden" name="currency_code" value="USD"> <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_buynowCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> <img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"> </form> That's one way, the options selected would actually be the item wanted and it's corresponding price, and can be done with one file in php as mentioned, though with 100 items, lets say 4 php files each having 25 items "options" so clients doen't have to scroll down the menu so far. My items are custom made and take 2-3 weeks to ship, so there is ALWAYS dialogue via email over confirming the item and finish wanted. The other way is this, just displaying ONE "option" for the specific item on each page, this would require editing every page to change prices, but easier than the PP editor: <form action="https://www.paypal.com/cgi-bin/webscr" method="post" target="_top"> <input type="hidden" name="cmd" value="_s-xclick"> <input type="hidden" name="hosted_button_id" value="A-TEST-NUMBER-HERE-NOW"> <table> <tr><td><input type="hidden" name="on0" value="model number">model number</td></tr><tr><td><select name="os0"> <option value="a">This Item $149.00 USD</option> </select> </td></tr> <tr><td><input type="hidden" name="on1" value="Suggested finishes available (default is the LIMESTONE">Suggested finishes available (default is the LIMESTONE</td></tr><tr><td><select name="os1"> <option value= "Limestone ">Limestone</option> <option value="Dirty Nickel">Dirty Nickel </option> <option value="Bright silver">Bright silver </option> <option value="Dirty Bronze">Dirty Bronze </option> </select> </td></tr> </table> <input type="hidden" name="currency_code" value="USD"> <input type="image" src="https://www.paypalobjects.com/en_US/i/btn/btn_buynowCC_LG.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> <img alt="" border="0" src="https://www.paypalobjects.com/en_US/i/scr/pixel.gif" width="1" height="1"> </form> So the question is: is there a limit on the number of "options" that can be added to this code, and will these two examples work?
... View more