- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I get the error "unsupported variable shipping2" in create button dialog for "add to cart" buttons, advanced variables section, this happens when I try to re-save existing buttons that have had the variable set up and working correctly in the past. I get the same error if I try to set up new buttons. The shipping2 variable is supposed to allow a different shipping rate for second and subsequent items in the cart. This was working properly for me in the past and I use it successfully on multiple "add to cart" buttons. I only get the error when I try to resave a button after changing something e.g. the item price.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have the same problem: Paypal shows the error: "Unsupported variable no_shipping" in edit of standard legacy addtocart button, under Advanced Variables section.
I am having issues with customers missing the single line shipping input at the top of the checkout page or thinking it is the billing address and proceeding to the next screen which completes sale and they don't get a chance to change shipping address to their new address. I wish to force shipping address input by user. I was told to use no_shipping=2, but Paypal will not allow me to use this as a variable. I also can not find the page the tech is referring to, to add no_shipping=2. I asked the question in a different way and same tech responded with same guidance, but no links, and the pages he mentions do not exist in the Paypal that I have access to.
If anyone figures this out, please post.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I talked with a PP manager yesterday (7/4) and it turns out that they have simply begun disabling the 'old' button functionality and suggest you implement the entire 'smart button' solution. So now if you create a new button - or edit an existing button - there will be no option to set weight. So if you had previously set up a weight-based shipping profile, the customer purchase will go through with $0 shipping. The Advanced Variables for 'shipping' and 'shipping2' no longer will work. Be very careful not to edit any old button or the weight-based shipping will be wiped out and process as $0
I asked what merchants like myself were supposed to do with 50+ buttons already created, the smart button paradigm not a trivial solution to set up, and no advanced notice? Basically I was told I am SOL. So now I have to eat about $200 in shipping costs from yesterday's orders.
I've concluded that PayPal is no longer a real business solution and I am now moving as quickly as I can to another eCommerce solution. This also isn't a trivial process but at least I'm going to work with a vendor that understands the importance of not acting in any way that can adversely affect a live production site and that should such a dramatic change be necessary, they would provide lots of notice and assistance to help merchants make any necessary changes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I fixed my buttons!
support pointed me to a legacy page where I was able to edit advanced variables using the old interface and it worked for me, I was able to reinstate lost variables there. I would describe this as alife-saving work-around for those who are losing money right now, can't say I have much confidence that this solution will be available in the long term, but it might help patch up the mess until you have a better solution. Legacy button manager here:-
https://www.paypal.com/us/cgi-bin/webscr?cmd=_button-management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thanks @vraquila. Your link worked for me using the Advanced Variable "on5". What a pain that PayPal is putting us through! We will be looking for another solution. PayPal should reconsider these recent deprecations. What were they thinking?
- « Previous page
-
- 1
- 2
- Next page »
Haven't Found your Answer?
It happens. Hit the "Login to Ask the community" button to create a question for the PayPal community.
- HTML variable for "use donation for" dropdown item in PayPal Payments Standard
- PayPal integration with Next, Lambda and API Gateway - 400 Invalid Request in Sandbox Environment
- Using Sandbox credentials at checkout loops PayPal to sign up page in Sandbox Environment
- HTML variables syntax and examples for Donate Button. in PayPal Payments Standard
- Help with HTML button variables syntax in NVP/SOAP APIs