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
Server does not support session. How to use cookies instead? | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Server does not support session. How to use cookies instead?

Server does not support session. How to use cookies instead?

Posted: March 31, 2014 at 1:32 pm

Viewing 9 reply threads


Delray Wannemcher

March 31, 2014 at 1:32 pm

I am hosting my site on WP Engine, but they do not support php session ids. The host has recommended using cookies instead. Here’s their documentation: http://wpengine.com/support/cookies-and-php-sessions/

Can I force the plugin to use cookies and work without php sessions? Could we create some kind of wrapper around the php cookies API to try and trick the plug-in into using cookies, replacing what is currently used for handling sessions?

Thanks,

Alex

WP 3.8
EE4
Live site: https://www.fsxinterlinked.com/register-now/broker-dealer-registration/
Site is not currently hosted on WP Engine


Lorenzo Orlando Caum

  • Support Staff

March 31, 2014 at 1:49 pm

Hi Alex,

You can use WP Engine but you’ll need to request no cache rules setup for your Event Espresso critical pages:

http://wpengine.com/support/wpengine-ecommerce/

http://staging.eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/

I also use WP Engine (USA & Japan) for some personal projects including an ecommerce store so I do know that PHP sessions are working.


Lorenzo


Josh

March 31, 2014 at 1:52 pm

Hi Delray,

It turns out that we tested EE4 on WP Engine and there have other users of EE4 using WP Engine and it works fine as long as caching is configured to allow Event Espresso pages (including the page with the [ESPRESSO_CHECKOUT] page) to be served dynamically.

The key part of the documentation that you linked to that applies to what you need to do to use Event Espresso on WPEngine is this:

Another special case where caching needs to be disabled is for eCommerce sites. Sections of the site, such as product pages, the cart, and the checkout page, need to be un-cached for all visitors. Because these settings can vary from site to site, we currently require you to submit a ticket to request pages on your site be un-cached.


Delray Wannemcher

March 31, 2014 at 2:28 pm

Hi Josh, Lorenzo,

WP Engine already excluded the following from the cache:
^/registration-checkout/
^/transactions/
^/thank-you-2/
^/registration-cancelled/
^/wp-content/plugins/event-espresso-core-reg/
^/events/

But I am still having problems. Any suggestions?

When I select a ticket and refresh the page my queue becomes empty. Does this imply caching is still occurring?

THanks,

Alex


Josh

March 31, 2014 at 3:55 pm

I don’t believe the ee plugin folder itself should be excluded from the cache:

/wp-content/plugins/event-espresso-core-reg/

but the checkout pages should be excluded from the cache.

When I select a ticket and refresh the page my queue becomes empty. Does this imply caching is still occurring?

Possibly. Is the page that you’re testing the ticket selector on included in the list of pages set to no-cache?


Delray Wannemcher

March 31, 2014 at 4:55 pm

The page that I am testing the ticket selector on is no in the list of no-cache pages. I am using the shortcode. But I’ve had problems with testing the reg process from /events


Josh

March 31, 2014 at 8:58 pm

Hi there,

Any page with a ticket selector shortcode should be added to the do not cache list. Can you verify that you are having issues with the events page when testing staging? WPEngine’s staging servers are not cached.


Delray Wannemcher

April 1, 2014 at 2:57 pm

There are no issues that I am aware of with the events on staging as seen here: http://fsx.staging.wpengine.com/events


Delray Wannemcher

April 1, 2014 at 3:35 pm

I think I have narrowed down the problem to occurring on the production pages using the shortcode ticket selector. I am testing the WP Engine production site by changing the host file.


Josh

April 1, 2014 at 5:27 pm

Hi Alex,

The pages with a ticket selector shortcode can be added to the do not cache list on the production site.

Viewing 9 reply threads

The support post ‘Server does not support session. How to use cookies instead?’ 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.

Event Espresso - Staging Server