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
PHP Handler: DSO vs. FastCGI? | Event Espresso - Staging Server

Support

Home › Forums › Pre-Sales › PHP Handler: DSO vs. FastCGI?

PHP Handler: DSO vs. FastCGI?

Posted: June 16, 2013 at 8:43 pm

Viewing 2 reply threads


Ira Feldman

June 16, 2013 at 8:43 pm

Hi –

In running the Event Espresso Requirements Tool I get  Espresso Requirements Check could not find apache_get_modules.

In checking with my hosting company (Site5.com) this is because apache_get_modules is not supported by FastCGI but only DSO (which they don’t support). I know a large number of hosting companies are now running FastCGI. Is DSO a requirement for EE? Or will FastCGI work? If so, with FastCGI what else do I need to check in terms of configuration? Not much listed on https://staging.eventespresso.com/wiki/known-third-party-plugin-theme-conflicts/ in terms of requirements.

Thanks,

Ira


Ira Feldman

June 16, 2013 at 8:53 pm

Sorry, pasted the wrong “requirements” page it is https://staging.eventespresso.com/requirements/ …


Josh

June 17, 2013 at 1:32 pm

You could probably run WP along with Event Espresso. The requirements check plugin is an automated check that will make recommendations based on what it can find. When it was developed FastCGI wasn’t taken into consideration.
Viewing 2 reply threads

The support post ‘PHP Handler: DSO vs. FastCGI?’ 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.

Status: closed

Updated by Josh 11 years, 7 months ago ago

Topic Tags

Notifications

This topic is: not resolved
Event Espresso - Staging Server