Posted: April 17, 2013 at 9:33 am
|
Hello I have a few questions: My host is WPEngine and they have a feature called a “staging site”. Essentially it allows you to replicate your live site, into a separate staging site in which you can make changes and test out functionality etc, before it goes live. Which license do you recommend if I’m only going to use Esspresso on one site, but it will be copied over to a staging site multiple times as I test things out? Are there ramifications with testing on a staging site (will all the functionality still operate correctly such as payment systems etc)? Also, am I correct to assume that I’ll need HTTPS enabled for my site if I start accepting payments? Thanks in advance. |
Hi Desmond, You’ll need one single support license since it’s for one live site. The support license includes a license key and you can use it on the live or staging site, but not both at the same time. The domain with the license key will ping the Event Espresso server and get automatic update notifications. The domain without the license key will function without the key. HTTPS is recommended if you’ll be accepting payments on-site. If it’s an off-site payment option like standard PayPal or 2checkout, it’s not needed. If you do end up using HTTPS, getting this to work on WPEngine can be tricky. Here are a few things to know about using on-site payment methods if you’re hosted on WPEngine: WPEngine has their own way of redirecting pages to https, so a plugin like WordPress HTTPS can not be used to make pages secure: http://support.wpengine.com/disallowed-plugins/ In that case they’ll set up the https redirect for you. We’ve found that in the case where the site is using Pretty permalinks, it will force the Event Espresso Return payment page to use pretty permalinks, which then requires a slight modification to the gateway’s payment form. If you end up using a payment method that requires https and you’re using pretty permalinks let us know and we can walk you through how to make the modification. |
|
|
Great, thanks for the reply. So it looks like if I have Espresso running on both the live and staging site, only one of them will be functioning with a valid key, and thus the only install that can receive updates? I’m a little naive when it comes to pretty links, as I thought it was something else then it is. So if I’m using %postname% as my permalink structure, that is considered a pretty link? If so it looks like I’ll have to make a modification as suggested. Thanks again. |
Hi Desmond, I’ll try to clarify a few points below:
They will both function with or without the key. The installation with the key will get update notifications, the installation without the key will not get update notifications. The installation with the key will be able to have 1-click updates. The installation without the key can be manually updated by deactivating, deleting, and uploading the new versions as they become available. So in practice it will take a few more minutes to update the site that doesn’t have the key set.
There are a few more factors involved. One is the gateway/payment method. Some of the payment methods may need an adjustment, others do not. The standard PayPal gateway doesn’t seem to be affected as an example. One thing you can check with WPEngine support on is whether or not they can set up the https redirect without forcing the pretty permalink. If they can set it up without forcing the pretty permalink, then the gateways should work out of the box. |
|
|
Great, I think you’ve explained everything really well. I’ll get in touch with WPEngine and clarify how they handle HTTPS redirect. It looks like in any case, I’ll be able to use Espresso and get it working (it might just require a little work depending on what payment system I use). Thanks again! |
You’re welcome! |
|
The support post ‘Development on staging server and https’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.