leverager

Thanks for adding the fix!

I found another similar issue affecting the Ideal payment method, but this could also affect the other sources payment methods too, whereby the statement_descriptor by default appears to be empty instead of nulled when you submit a payment. This is what I get when trying to make an ideal payment:

The {
“error”: {
“type”: “invalid_request_error”,
“message”: “You passed an empty string for ‘statement_descriptor’. We assume empty values are an attempt to unset a parameter; however ‘statement_descriptor’ cannot be unset. You should remove ‘statement_descriptor’ from your request or supply a non-empty value.”,
“param”: “statement_descriptor”
}
}

Also I don’t see any options in the plugin options to set a statement descriptor for Ideal or the other new payment options.

Hope this helps!

Understood, just posting this as feedback to help improve the UX when it does go live. Keep up the great work.

Thanks for the heads up, I just thought I would mention it as many stores are setup to override this and let customers purchase without a phone number, and stripe does not require a phone number for orders to go through, but fails if the field is not set to null.

Thanks for the heads up, looking forward to that.

Chris

Thanks for the update, we look forward to this. Version 4.0 will be a game changer with secure 3D and the other payment options available out of the box.

Excellent, many thanks I look forward to this being implemented.
I would recommend getting in touch with the WPML team, they are v responsive and proactive in helping 3rd party plugin/theme devs implement WPML best practices.

Plus you’ll get featured for free in their Compatible plugins section & get a mention on their blog which should help spread the word about this great plugin you made.

Hi,

Normally with WPML there are two ways of translating strings: Using the string translation manager or some plugins enable you to translate their text by changing the WPML locale at the top of the screen from one language to another.

With AMP for WP neither of these methods work.

The APM for WP strings don’t appear in the strings translation manager, and changing the WPML language locale using the top dropdown and saving the translations within the AMP for WP translate screen applies the translations saved to all languages, instead of saving for each locale.

We are currently using WPML to translate our site into 10 different languages, and if I translate using the AMP for WP translate page using the French locale, these translations will show for all the other languages.

Does this help clarify the issue?

Thanks,
Chris

Hi,
I can confirm we are experiencing the same issue when you click from an amp link on google, there seems to be an incompatibility with Google’s own header link at the top, so the sticky header floats in the middle of the page as you scroll down obstructing the view. This doesn’t seem to happen when you preview an amp page by visiting the /amp link directly, but when the amp page is served from a google search result (where the google link header appears at the too.).

Please fix this as soon as possible as it’s annoying to users and causes a high bounce rate.

Also would be great to have an option to choose not have the sticky header (in other words for the header to remain at the top of the page so that it is no longer visible if you scroll down). This is what the majority of the news site do (for example the telegraph.co.uk) and for usability sounds like the best option as google already includes a header at the top which reduces the amount of screen real estate available.

Thanks
Chris