Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
securing the registration page in EE | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › securing the registration page in EE

securing the registration page in EE

Posted: January 15, 2014 at 12:34 pm

Viewing 5 reply threads


poumonAPQ

January 15, 2014 at 12:34 pm

hello,

I need to secure the registration page, but currently I have one domain setup with 3 subs on a wordpress multisite setup. my web host company does not allow me to get a wild card ssl certificate installed on the server to secure the sub-domains. Never having done this, I assume that even with a ssl certificate on the main domain, properly installed, the certificate would not secure the sub-domains, and my registration page is on a sub-domain.
All I want to do is secure the event-registration page for EE. the payment page is done on my payment provider company site, no problem with securing payments.

My question is, how could I secure/encrypt the event registration page with the least bit of hassle and without having to move to another host company?

thanks


Josh

January 15, 2014 at 1:41 pm

You should be able to get a wildcard SSL from GeoTrust:

https://www.geotrust.com/ssl/wildcard-ssl-certificates/


poumonAPQ

January 15, 2014 at 2:48 pm

that does not answer my question; as I said my web host does not allow me to install 3rd party ssl wildcards cert. I could install their own ssl cert, but they don’t support subdomains, which is my problem.


Sidney Harrell

  • Support Staff

    •

January 15, 2014 at 3:06 pm

The only way to secure a web page is with an ssl cert. If your host is keeping you from securing sub-domains, then there isn’t much you can do except change hosts. You could set up WP multisite using subdirectories, instead on subdomains, in which case you could use a single site ssl cert. So instead of site1.yoursite.com and site2.yoursite.com, you would have http://www.yoursite.com/site1 and http://www.yoursite.com/site2.


poumonAPQ

January 20, 2014 at 7:00 am

ok, I’ll try changing to sub-dirs.


Dean

  • Support Staff

    •

January 22, 2014 at 4:03 am

Please let us know how you get on.
Viewing 5 reply threads

The support post ‘securing the registration page in EE’ 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.

The original Forum description...

Status: closed

Updated by Dean 10 years, 12 months ago ago

Topic Tags

Tagged: , , , ,

Notifications

This topic is: not resolved
Event Espresso - Staging Server