Hi Jayc
Thanks again for your help.
I tried the setting value that you suggested, but this time it removed the PayPal system completely from the product page (there was no message or PayPal button). So I guess I'm still at a loss as to how to get the message to show / change that iFrame issue.
PayPal Commerce odd iFrame issue stopping messages
- 117
- 1016
- 6/9/2014
- Australia
dashdesigns wrote:
Strange. On the site that doesn't work, its not selling any subscription services is it?
The iframe is rendered based on the javascript sdk config, and its all documented here:
https://developer.paypal.com/sdk/js/configuration/#link-queryparameters
So I guess I'm still at a loss as to how to get the message to show / change that iFrame issue.
Strange. On the site that doesn't work, its not selling any subscription services is it?
The iframe is rendered based on the javascript sdk config, and its all documented here:
https://developer.paypal.com/sdk/js/configuration/#link-queryparameters
- 115
- 635
- 12/7/2010
- Australia
So, I eventually got a reply from PayPal tech support who viewed this topic and saw the iFrame code. They then informed me that the code I am seeing is from the PayPal WPS (website payments standard) code and not the new PayPal Commerce iFrame.
I then checked my client's website plugins and saw that the Paypal Standard plugin was installed and disabled.
Now the interesting thing is the other website I referred to with the code that works earlier also has the PayPal standard plugin installed and disabled as well, hence why this did not ring any alarm bells. It appears that it must have been the order they were installed on the websites that caused the problem website to be seeing the WPS code first.
I simply deleted the WPS plugin and restarted the application. This in turn triggered the new calls to the PayPal API informing them that we were now using the new Commerce plugin. After 4 days, the change had taken effect and the paylater messages started to appear.
Thanks for everyone's time with the previous replies.
I then checked my client's website plugins and saw that the Paypal Standard plugin was installed and disabled.
Now the interesting thing is the other website I referred to with the code that works earlier also has the PayPal standard plugin installed and disabled as well, hence why this did not ring any alarm bells. It appears that it must have been the order they were installed on the websites that caused the problem website to be seeing the WPS code first.
I simply deleted the WPS plugin and restarted the application. This in turn triggered the new calls to the PayPal API informing them that we were now using the new Commerce plugin. After 4 days, the change had taken effect and the paylater messages started to appear.
Thanks for everyone's time with the previous replies.