|
Serdar Ugurlu
|
October 14, 2018 at 8:37 am
Hello Support Team,
recently we are confronted with an error when trying to checkout for an event booking on our site http://www.phototours4u.com.
It states:
The stored data for session ee_ssn_e8rdfkf failed to pass a hash check and therefore appears to be invalid.
We had such problems in the past when we used a caching plugin which we dont use anymore.
So I wonder where I can check possible reasons for this behauviour ?
Thank you for your Help.
The Error occurs in Step 2 Payment option during the Checkout Process when one clicks the Invoice Radio Button.
The Error Log on our Server states:
Sun Oct 14 16:35:27 2018] [-:error] [pid 793] [client 95.223.45.111] [host http://www.phototours4u.com] PHP Notice: Die verwendete Konstruktor-Methode f\xc3\xbcr WP_Widget in dorayaki_headerinfo ist seit Version 4.3.0 [strong]veraltet[/strong]! Verwende stattdessen [pre]__construct()[/pre]. in –removed–/wp-includes/functions.php on line 3916
[Sun Oct 14 16:35:27 2018] [-:error] [pid 793] [client 95.223.45.111] [host http://www.phototours4u.com] PHP Notice: Die verwendete Konstruktor-Methode f\xc3\xbcr WP_Widget in dorayaki_video ist seit Version 4.3.0 [strong]veraltet[/strong]! Verwende stattdessen [pre]__construct()[/pre]. in –removed–/wp-includes/functions.php on line 3916
Thanks for your Help
-
This topic was modified 6 years, 1 month ago by
 Tony. Reason: Removed duplicate notices and server path
|
|
Tony
|
October 15, 2018 at 3:29 am
Hi there,
I’ve removed most of those PHP notices as they were all the same, unfortunately, those notices are not linked to the problem but they do mean that either your theme or a plugin needs to be updated to correctly create widgets (something on your site is using an ‘old’ method of creating widgets).
There is one important bit of information from those notices:
PHP Notice: Die verwendete Konstruktor-Methode f\xc3\xbcr WP_Widget
We see text like this ‘f\xc3\xbcr’ when opcache is enabled on the server, have you recently updated the server to use PHP7?
If you go to Event Espresso -> Maintenance -> System information
Search for ‘opcache’, do you see any settings for it?
|
|
Serdar Ugurlu
|
October 15, 2018 at 11:19 am
Hello Tony,
My Provider is planning to switch to PHP 7 in October 24 as far as I know right now our Site is running with php 5.
Coming to your question concerning OP Cache. I have checked it an searched for the String opcache but could not find no matches for that. Then I downloaded the text and opened the resulting html file in an editor and searched again. There is no reference to opcache whatsoever.
Sorry
|
|
Josh
|
October 15, 2018 at 11:38 am
It’s actually OPCode Cache, but there are other types of caching that involve compiling the PHP code to bytecode (like APC). What you can do is check with your web host and ask them which types of caching are activated on the server. If they’re using any type of bytecode caching then that should be disabled. Any other types of caching should be limited to static pages on your website. In other words, the registration-checkout page must not be served from a cache in order to prevent errors like the one you’ve reported here.
|
|
Serdar Ugurlu
|
October 15, 2018 at 12:39 pm
Hello Josh,
Hi There Tony,
I opened a Ticket with Hosteurope which is my Provider, they said that there is no caching used on the server.
I am really not aware of a Cache Plugin which I am using because since the day we have this site we never used one because EE does not like it at all.
Is there anyway to find out which tool or plugin could be using some kind of caching mechanism ?
Thank you
|
|
Tony
|
October 16, 2018 at 3:40 am
Generally when we see that error, its some form of caching, be it a plugin or server side.
In terms of detecting caching or using a tool, I don’t know of any and it really depends on how it’s been set up if they would work.
The error you are getting is basically a check from the stored session data and the current requests session data, they should match, but on your site they do not.
The check is only performed when WP_DEBUG is enabled on the site, so you could set WP_DEBUG to false, however, the fact that you are getting that error means that you will likely run into other issues when you disable it (but those errors may also help narrow down the issue further).
You can try disabling the hash check to see if another error is shown using:
add_filter('FHEE__EE_Session___perform_session_id_hash_check', '__return_false');
to a functions plugin and activate it. (Leave WP_DEBUG enabled to see if any other errors are thrown)
As mentioned if data is being served from a cache on the server you’ll likely see other problems.
|
|
Serdar Ugurlu
|
October 16, 2018 at 12:47 pm
Tony,
Thank you Mate !
I deactivited the WP Debug Mode and made a Test est voila it works.
I put this one on resolved.
Thank you guys may your day be a good one !
|
|
Tony
|
October 17, 2018 at 5:37 am
I’d recommend using the above code I included above:
add_filter('FHEE__EE_Session___perform_session_id_hash_check', '__return_false');
As that will disable the check but still allow you to enable WP_Debug when needed to troubleshoot, you can add that to a custom functions plugin on the site:
https://eventespresso.com/wiki/create-site-specific-plugin-wordpress-site/
Up to you either way, but I’m glad it’s working.
Thank you guys may your day be a good one !
You’re most welcome and the same to you.
|
