Multiple sites need cart button to open to specific, custom page

[tvsmvp]

I need to place buy buttons on multiple sites - and so need to adapt that page that pops up when somebody click on "add to cart." (They'd call for a different site logo at the top, for instance.) With a paypal button, I can add a hidden field that says specifically which page to open to - but how do I do that with ejunkie?

[E-junkie_Guru]

If you use the standard version of our cart button codes and include at least one block of your View Cart code on every page, the cart should then appear as an overlay "inside" the page itself, so it fits within that site's existing branding; however, that would not allow adding items from different sites to a common cart order to check out together all at once.



If you use the non-javascript version of our Cart button codes, those will open the cart in a separate window/tab that can hold items added from separate sites to a common order together, but that cart could only display whatever custom logo/header you have uploaded to your E-junkie account. We have no way to alter the appearance of that cart nor the appearance of the checkout page for any type of cart implementation depending on which button on which site/page is clicked.



Buy Now buttons of course bypass the cart entirely and take buyers directly to instant checkout for just one item at a time, but they can't use any of our features that depend on the cart:

http://www.e-junkie.com/ej/help.buttons.buy-now.htm



You could at least make the cart and checkout page more generic by simply removing the custom logo/header image you'd uploaded to E-junkie. Just go to Seller Admin > Edit Profile, click Upload Your Logo, then use the Delete button on that screen to remove your custom header image. PayPal checkouts would then display whatever Business Name you have defined in your PayPal Profile, so you might want to change that to something suitably generic, and do likewise with the Display Name and Email settings in your E-junkie profile.



If you really want to maintain separate online business identities, you could really only do that with us by maintaining separate E-junkie accounts for each identity. Then you could specify a different Display Name/Email in each account's E-junkie Profile and upload a different custom logo/header image in each one. This would also allow you to set up each account with different account-wide settings under the Manage Your Seller Account section of their Seller Admin. If you still need to accept all payments to a common PayPal account for all sites, you would simply add secondary emails to your existing PayPal account and use those as the PayPal Email for each new E-junkie account.

[tvsmvp]

Thanks for the info -



I went ahead and put in a generic header. A nice improvement would be to give us the ability to choose a page skin.



A related question: Would I be correct in assuming that if I've only got one input (dropdown select in this case) that it must be named os0 - and that naming it os1 (skipping a lower number) would cause it to be ignored? Trial and error leads me to this - but I thought there might be some naming convention used that I might be missing. The buttons on my site are created "on the fly" - as some products require more than one dd (as originally mentioned above). Must I append the 0, 1, or 2 to the "os" and "on" dynamically?

[E-junkie_Guru]

First, every os# (option selection) value must be accompanied by a corresponding on# (option name) value -- e.g., <input type="hidden" name="on0" value="Slogan"/><input type="text" name="os0" maxlength="200"/> in an Add to Cart button form, or &on0=Color&os0=Octarine in the button's href=/action= URL (for our Cart buttons, any form field can instead be passed as a URL query parameter, or vice-versa -- i.e., GET and POST variables are interchangeable).



Furthermore, PayPal ignores higher-order on/os value pairs if lower-order on/os value pairs are missing -- e.g., if you had a text-entry field for os0 and a menu for os1, PayPal would ignore the buyer's menu selection if they'd left the text entry field blank; for this reason, we recommend putting menus first and text-entry fields last, and for multiple text-entry fields putting them in order of most- to least-likely to be filled.



If your cart button codes are dynamically generated by scripting in your site, you might consider the approach of determining the buyer's option selections separately from our button code, then just dynamically append their selection values directly into their Add to Cart button's href= URL like so:

https://www.e-junkie.com/ecom/gb.php?c=cart&i=XXXXXX&cl=11392&ejc=2&on0=Color&os0=Octarine

[tvsmvp]

Thanks, that's what I suspected. I went ahead and had php assign "the next higher" number to the selects as they're first created so it works fine now.