|
wmnf
|
September 30, 2015 at 1:25 pm
I need to confirm how to handle the WordPress HTTPS plugin setup. I’ve been made aware of duplicate emails and find the day they started was the same day we installed that plugin. When I installed, I added the checkout slug only to the URL Filters and enabled Force SSL Exclusively, but today found your document on the subject….
https://eventespresso.com/wiki/espresso-sslhttps/
I tried to setup as shown, but it doesn’t secure our ticket selector page on individual event pages. I added these to the HTTPS URL Filters section, the first three taken from Critical Pages in EE settings:
/registration-checkout/
/thank-you/
/transactions/
/wmnf-events/
Our website was designed by a third party, so I am not familiar with the template setup. The Events navigation leads to the last entry above, however, the ticket selectors are on the individual event pages and not being secured. Can you help identify what settings are needed?
http://www.wmnf.org/wmnf_events/
I have removed all entries including checkout slug from the URL Filters now hoping the issue is due to only the one being added initially. I would like to get the checkout page enabled. We are using Mijireh for CC processing.
|
|
wmnf
|
September 30, 2015 at 1:48 pm
Something else I forgot to mention. When I enabled HTTPS using the filters above, I received a browser warning that resources on the page were not secure. If you have any information on how to handle that as well would be helpful.
Since it is disabled now, I have not been able to review source and address links, but all common links that cause the same warning when securing our Woocommerce install are resolved already. We have it successfully using HTTPS without the warnings on the cart and checkout.
|
|
Tony
|
October 1, 2015 at 3:57 am
Hi there,
Your events are using the slug /wmnf_events/ (note the underscore) however within the filter it looks like you have /wmnf-events/ (note the dash) so the filter won’t apply to your events currently. You will likely need:
/registration-checkout/
/thank-you/
/transactions/
/wmnf_events/
When securing the front-end you will also need to make sure your admin is https exclusively to so that the ajax requests work as expected.
Something else I forgot to mention. When I enabled HTTPS using the filters above, I received a browser warning that resources on the page were not secure. If you have any information on how to handle that as well would be helpful.
That can be any img, script, css etc loading via HTTP on a page loading via HTTPS. We will need to see the page when the error is happening to be able to help further with those errors but basically you need to ensure all resources are loading over HTTPS.
If you fix the filter above and enable the page I’ll take a look and see what shows up.
|
|
wmnf
|
October 1, 2015 at 6:28 am
Ah, I didn’t even notice, but the correct link to our events is with a hyphen as in….
http://www.wmnf.org/wmnf-events/
But when you click on an event link on that page, you get with the underscore. There is another archive page with the underscore. I added both and now its working.
I also tracked down the cause of the browser warning, it is due to the search in the admin toolbar. The warning only appears when you are logged in, so we won’t worry about it since that is only internal staff.
However, we still get duplicate email messages with or without the HTTPS enabled. We use Sendgrid and I see they are all separate messages going out. We get exactly two of the Event Approved messages for each registration and the second one always comes in about an hour after the other.
|
|
wmnf
|
October 1, 2015 at 6:56 am
Actually don’t think we’ve had a good test with HTTPS fully functional, I believe the forced admin SSL might have been playing a part without HTTPS. We’ll wait for the next registration to see if this is resolved. Thanks!
|
|
wmnf
|
October 1, 2015 at 8:47 am
Unfortunately, the duplicate emails continue with HTTPS fully enabled.
|
|
Tony
|
October 2, 2015 at 5:28 am
Regarding /wmnf-events/ and /wmnf_events/
It sounds like you have a PAGE (likely using the [ESPRESSO_EVENTS] shortcode) using the slug /wmnf-events/ and have EE setup to use slug /wmnf_events/
That right? If so then yes then that explains why you need both thost strings… it won’t effect the emails I’m just curious as to why that’s happening.
However, we still get duplicate email messages with or without the HTTPS enabled. We use Sendgrid and I see they are all separate messages going out. We get exactly two of the Event Approved messages for each registration and the second one always comes in about an hour after the other.
Hmmm, that sounds like a cron is triggering the emails to be resent.
I’ll do some investigating but are you running any caching on the site? Be it plugin or server side through your host?
|
|
wmnf
|
October 2, 2015 at 6:42 am
Makes sense about the pages. I did not design the site, but I’m sure you are right and I haven’t had time to investigate the code.
The bigger issue being the emails, I do have W3 Total Cache with Database caching only. I just disabled to see if that helps. PHP APC cache remains enabled.
|
|
wmnf
|
October 2, 2015 at 8:11 am
Still getting duplicates as I noted before with W3 Total Cache deactivated.
|
|
Tony
|
October 2, 2015 at 10:59 am
I’ve been looking over this and it looks like the cron we setup on the transaction to check if its been abandoned (runs after 45mins, when a user visits the page) is triggering the additional email.
I’ve issued a ticket with our developers to investigate and will update this thread with any feedback.
|
|
wmnf
|
October 3, 2015 at 9:10 am
Yeah, something is amiss, we got an approved email this morning for a registration over 24 hours ago. This appears to be affecting all email templates.
|
|
wmnf
|
October 3, 2015 at 9:28 am
Never mind that last comment, seems the registrant paid 24 hours after they registered. We don’t want people paying after the cutoff time for those tickets they purchased, instead pay at the door price. Would we just disable the Registration Pending Payment somehow?
|
|
Tony
|
October 5, 2015 at 9:47 am
So you only want users to be able to pay at the time of registration with no ‘return payments’ at all?
|
|
wmnf
|
October 14, 2015 at 1:14 pm
We just don’t want them paying after the cut-off time of the event and especially after the event has already started. We usually enter an Advance price and Door price with cut off time for Advanced tickets when setting up the event. We don’t want anyone paying for that event after that cut-off time.
Also, FYI – I updated to version 4.8.14.p and we are still getting duplicate emails for every order. Still about 55 mins apart.
|
|
Tony
|
October 15, 2015 at 5:13 am
The duplicate email issue should be fixed in the next version of Event Espresso.
Currently there isn’t a way to set a specific date in which a payment option will be available for a specific ticket, by cut off date do you mean the ‘Sell Until’ option set within the ticket editor?
|
|
wmnf
|
October 15, 2015 at 6:54 am
Yes, the ‘Sell Until’ date.
|
|
Josh
|
October 19, 2015 at 12:40 pm
Hi there,
The fix for the multiple registration notification email is included in Event Espresso 4.8.15.p, which was released earlier today.
Regarding how to stop them from paying after the Advance ticket cut off date: You can set their registration to Not Approved or Declined if they haven’t paid by the cut off date. Then they will not be able to pay.
|
