|
Giant Dwarf
|
March 12, 2017 at 11:48 pm
Recently we started serving our site via https. However, we’ve started receiving a number of complains from users that our payment page is not served securely. Although the page is served securely, the Chrome toolbar does not show “secure” causing the confusion. It turns out this is because the images for the payment methods on the page are served via http.
I’ve attempted to rectify this on the payment method page, but after changing the image URL’s to https the change won’t save, stating “That URL seems to be broken. Please enter a valid URL” on the image. Obviously it is a valid url, and it’s served from the same domain as the site. I’ve tried updating the string manually in the database, but that instantly gets overridden by EE. I’ve also tried implementing the code from this earlier support topic to switch off SSL checks which did nothing. https://eventespresso.com/topic/that-url-seems-to-be-broken-please-enter-a-valid-url/
How can we fix this?
P.S. I’ve noticed a large number of people reporting that PayPal payments are not being logged on their site in the support forums. We’ve had the same issue, and I’d guess it might be related to the fact that since Friday some PayPal servers have been stripping out values from the query string. http://stackoverflow.com/questions/42669566/querystring-values-removed-from-the-ipn-endpoint-by-paypal
|
|
Garth
|
March 13, 2017 at 12:05 pm
Can you provide the address of the https image please?
|
|
Giant Dwarf
|
March 13, 2017 at 5:17 pm
https://giantdwarf.com.au/wp-content/uploads/2016/11/card_button.png
and
https://giantdwarf.com.au/wp-content/uploads/2016/11/paypal_button.png
They’re the exact same urls as were being used on the payment methods but with an added ‘s’.
|
|
Josh
|
March 13, 2017 at 6:05 pm
Hi there,
The simple solution is host your images from another server that pass the https validation check on the Event Espresso Payment Methods settings page. For example, these should validate OK:
http://ee-screenshots.s3.amazonaws.com/2017/03/paypal_button.png
http://ee-screenshots.s3.amazonaws.com/2017/03/card_button.png
The developer that added the validation wasn’t able to figure out why the validation doesn’t pass on some servers that have SSL, we think it’s probably a server configuration somewhere that causes the validation to fail.
With regards to PayPal servers stripping out values from the query string, we’re aware of this, and that’s one of the reasons why we recommend using PayPal Express instead of PayPal Standard. The PayPal Express gateway isn’t affected by the issues with the PayPal IPN notify_url params getting stripped.
|
|
Giant Dwarf
|
March 16, 2017 at 6:01 pm
Thanks. I just added www to the domain name and that seems to have provided a decent workaround.
|
