February 17, 2017 at 12:19 pm #8917
I can help you debug.
Note: I moved your post to a new thread since it’s a different error than the “access denied” SSL thread it was originally posted in.
This is not an error we have in our Unit Testing, so it may be an environment related issue. Can you clarify what version of WP, WC, and MyStyle are you using at the moment? Can you link me to your website so I can take a look?
FYI you shouldn’t need to “delete” mystyle if there is an issue with running it, you can simply disable the plugin in your WP Admin and it will not run in any way.
Do you have a dev site we could use to debug?
Are there any other plugins running that manipulate products in WooCommerce?
– SeanFebruary 17, 2017 at 3:09 pm #8921
This is still not clear whether or not you have an issue in your environment causing this error or not. I can say we have tested the latest version of the plugin and are not able to reproduce the error in a standard wordpress / woocommerce environment.
Here’s some more information from our dev team:
The code indicated in the error message has to do with the MyStyle session that the plugin is using to track the user. To get the session, it first looks in php’s built in $_SESSION and if it’s not in there, it looks in the user’s cookies for a session id and rebuilds the session object by pulling session data from the db (using the session id).
This specific error is:
“The script tried to execute a method or access a property of an incomplete object”.
We’ve never seen this error before. I’m guessing that it has to do with trying to build the object from the $_SESSION and that the data coming back from $_SESSION is somehow corrupt.
One idea is to clear all session data in case for some reason there is corrupted session data from other plugins (you would most likely need ssh access to the server to do this).
This post seems relevant: https://stackoverflow.com/questions/1055728/php-session-with-an-incomplete-object
We’re still doing more investigation, but I may need access to your site to pinpoint the issue if it’s not with our plugin code.
ThanksFebruary 22, 2017 at 1:51 pm #9035
Just circling back with you on this bug. Our high priority lead dev team is scheduled to work on it tomorrow.
That said, were you able to figure out why your session data would be corrupted / modified? Seems that is the root cause of the issue as is related to your environment, that does not happen in our test environment or unit tests. I am curious if there is a plugin or theme or something that is known to corrupt the session in this way. Are you able to paste your WC diagnostic here so we can see your versions and plugins list?
– SeanFebruary 23, 2017 at 5:48 pm #9206Joey SommerMember
Hello, we have just released plugin version 1.6.3 with fixes that address your issue. Please update your plugin and let us know if you see any other issues or require more support. Thank you!February 25, 2017 at 11:03 am #9216
Just a little more info on how to update your plugin-
You should be able to go to “My Account” and then see your available downloads from your purchases. That link for the plugin should already be the new version, so just go ahead and download it from there to update.
Note: Your WP-Admin will not show the typical automatic “update” link in your plugin list, you need to deactivate and remove / delete the old plugin from your plugin list, and then upload the new one from your download link in your account page.
Let me know if you have any issues with this. I can also email you the zip file if you have any issues.
- The topic ‘Fatal error: MyStyle_SessionHandler::get()’ is closed to new replies.