Forum Replies Created
-
Posts
-
Hi Chris,
Just following up.
Did this workaround to set the “All Products” value work for you?
Thanks,
– Sean
Hi Chris,
I got a fast response from the dev team on the new ticket. He says there is a workaround for you. This is the response from our lead / Senior WP Dev:
Sorry, I didn’t address this before (multiple bugs were in the same ticket).
This behavior is somewhat expected as designed. For both the Categories field and the Tags field there is a special entry for “All Products”. This is a carryover from how the original WoOCommerce plugin did it.
The “All Products” option tells the plugin to apply the add-on to all products regardless of category. Or in the case of tags, to apply the add-on to all products regardless of tag. “All Products” is the default for both of these fields.
Most likely because the admin was using the original plugin first, they probably have global add-on entries that now are missing a value for the tags field – ie the special “All Products” setting that should be default if you use our plugin from day 1 instead of switching. Not having this setting to tell the system to apply to all products will break it, as it tries to apply to null or empty values. It expects a list of values or the “All Products” entry to work properly, and this seems to be another oversight of the original WooCommerce version.
The easiest solution would be to edit all of the global add-ons in the system and set the Tags field to “All Products”. If you are unable to do that, we could maybe alter the plugin to handle the blank/null field scenario, but it is complicated though if I remember correctly, this was set up this way to try to stay close to the WooCommerce plugin’s settings, because of how the built-in WordPress query system works.
Chris can you try this approach to fixing the “other” setting that has no value, and see if it works for you?
If not, we may need to do a custom development for you so that the plugin can handle this edge case of old WC plugin vs new MS plugin handling the null setting exceptions.
Let me know if that works for you or if we should quote out a custom dev project for a few more hours of development, testing, and deployment. Normally this type of stuff is covered in your MyStyle License where we cover all support costs, but in this case you’re only using the standalone plugin that doesn’t require a license. Unfortunately our year of support on this product does not include new developments for edge cases like this. I don’t think it will take too long to add in more logic to workaround this situation, but setting your add-ons up properly might be a lot faster, easier, cheaper etc than going that route just yet – so let me know!
Thanks!
Hi Chris,
Yes the “default” selection for any add-on seems like it should have been a feature included in the original, which is why we chose to fork it and add that. Otherwise, people do get confused why they can’t just buy what they see in front of them without making selections first – especially if there’s going to be a lot of product options on the page.
I’ve re-opened another ticket for this once more. I know we corrected this bug on our end last week, but we did not test in your specific environment, so this time around that’s exactly what we’ll do.
Are you able to grab your server’s actual errors from your error log after loading the product page to produce the error? That would give us your environment-specific error exactly, so that we can fix it more specifically around your system this time. Your log file is typically found in like apache2/logs/*error*.log
Thanks,
– Sean
Hi Chris,
My sincere apologies, our dev team did in fact put up the old version by mistake. This has been corrected and you can verify that your download link now has “v1.0.1” in the zip filename.
If this does not work for you for any reason this time, I will email you the zip file directly myself.
Hi Matt,
I’ll take the silence as a good sign that you’re not having any issues now.
Closing this ticket. Please open another if you still have any issues we can help with.
Thanks,
– Sean
Hi Brad,
Please reach out to your account manager if you’d like to move forward with more customizer modifications, we’re here to help!
I’m closing this thread now, it’s been over a month since your last response.
Thanks
– Sean
Hi Chris,
The new version of this should fix this problem, it was put up Friday and has passed testing.
Can you please remove the old plugin, download the current version from our site and install and test that? It should fix this bug for you, but I need you to verify on your environment.
Thru your My Accounts page you should have your download link there from your previous purchase, that link will be the new version. Be sure to clear your cache to make sure you see the most recent version of the page.
Thanks
Matt,
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.
Thanks,
– Sean
Hi Chris,
Thanks for opening your ticket and providing access. I can see our dev team has received it and will be investigating and fixing it today / tomorrow.
Thanks,
– Sean
Hi Matt,
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?
Thanks,
– Sean
Hi Chris,
Do you have SSH access on your server, are you able to copy the server error log output for exactly the page with the issue so our dev team has the exact line numbers and everything for the errors? You can email it with your ticket or you can paste it here.
(Please do not post your server access credentials or login info in the forums, of course)
Thanks,
– Sean
Hi Chris,
You can send your site access information to CustomerService@MyStylePlatform.com, that will create a ticket. Please paste a link to this thread in your email for our dev team to reference your description of the bug.
We are allocating a developer for the project today (busy current dev schedule rolling out new HTML5 customizer upgrades this week for the mystyle custom product designer). We are hoping to have the fix in place tomorrow or Friday.
We will post the update in our marketplace and make a post about it when it’s done.
Thanks!
– Sean
Hi Chris,
Sorry I wasn’t able to reproduce this error in my environment, even though I do have existing add-ons, they seem to work OK on the front end.
Are you using a custom theme, or other custom plugins that may have collisions?
What versions are you on of WP / WC? You can paste your WooCommerce diagnostic here if that’s easier.
Do you have access to your server’s error logs? Can you copy me the server errors that occur on the product page when the boxes fail to show, if any?
Are you using Select boxes with Options or other type of product add-on display (radio, etc)?
Do you have a dev site or can we have access to the site to look directly at it?
If this is a bug, it should be in the bugs forum so our devs take a look at it, but if I can’t reproduce it, I’m not sure they will be able to either unless we have your exact setup to replicate the environment you’re running.
Thanks,
– Sean
Hi Mat,
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.
Thanks
