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
Does EE require exec() / exec.php or url_fopen functions? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Does EE require exec() / exec.php or url_fopen functions?

Does EE require exec() / exec.php or url_fopen functions?

Posted: September 17, 2013 at 12:54 pm

Viewing 1 reply thread


wharrah

September 17, 2013 at 12:54 pm

We are looking to move our website to a WP managed hosting provider. The provider has asked us to verify that EE does not require exec() / exec.php or url_fopen functions, which have been disabled in their hosting environment, for security reasons. (They do support CURL as an alternative to url_fopen).

Thanks!


Dean

  • Support Staff

    •

September 18, 2013 at 2:50 am

For the most part this will be ok. The only areas I can see that would have an issue with it is the PDF generator for tickets. I will raise a ticket on this as really it shouldn’t be reliant on this.
Viewing 1 reply thread

The support post ‘Does EE require exec() / exec.php or url_fopen functions?’ 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 11 years, 4 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server