Google Checkout Button Not Working

Hi Dawna,

Have you tested your button code on a non-CMS Builder page to make sure it works? Get it working on a separate page without any CMS Builder code on it (just a plain HTML page), then send me a link. Then we can compare the two and see what's different. :)

I've done a couple things that will hopefully help problem solve. First, I pasted the Google button code using the CMS and then also pasted the Google button code on the same PHP page but not through the CMS. The Google button on the top is displayed through the CMS and the one underneath of it is outside the CMS tags on the page. The button on the bottom works. The button that's being displayed through the CMS doesn't. Go to: http://www.life-benefits.com/test_page.php. I have also pasted the same google button code on a plain html page at the same domain and it also works. You can see that by going to http:/www.life-benefits.com/test.htm

I hope this helps. :)

Well, I can tell you that the reason why your CMS Builder WYSIWYG-pasted button doesn't work is that the <form action> attribute is being removed, but I can't figure out why that would be since my local copy won't filter that attribute.

What version of CMS Builder are you using?

Thank you Chris! It's v 2.04

A ha! I was able to reproduce this issue using Internet Explorer. This is, unfortunately, a limitation of the WYSIWYG component we use.

I can think of two workarounds for you:

1. Use Firefox. ;) I realize it may not be possible to get all your users who have access to editing payment buttons to use another browser.

2. Use a textbox field for your payment button and paste in HTML. You may end up needing to split your content field into two WYSIWYG fields: "before payment button content" and "after payment button content".

I hope this helps! Please let me know if you have any questions.

I had the same problem with a PayPal Standard button. I consider this to be a major flaw, a real drawback with clients...any chance of elevating it/listing as a bug or supplying a different WYSIWYG editor?