Tagged: Add-Ons, Migrating add-ons, Woocommerce
- This topic has 14 replies, 2 voices, and was last updated 6 years, 2 months ago by Sean P.
- February 20, 2017 at 1:35 am #8950
I have a lot of global add-on set up on a store but want to use your plugin for simple client side default options on the add-on fields.
Although the plugin recognises the original add-ons created via the official woo version of product addons it will not display them on the front end.
New addons i create will display correctly.
Can you please suggest a fix for this.
(I installed your new plugin – deactivated the original Woo plugin – activated your new plugin)
Note: i could not find any directions or instructions for your plugins at all (such as installation instructions). Can you also please advise where this documentation might be accessed from.February 20, 2017 at 1:59 am #8951
I am also finding that any new global addons will not display if a category is set.
It will only display based on displaying via All Products in the tags section.
I need help with this asap and/or a refund as i need to be able to trust this plugin on the live site.
ChrisFebruary 21, 2017 at 3:59 pm #9025
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.
– SeanFebruary 22, 2017 at 1:40 am #9029
I have multiple dev environments you can test this on.
The are expressly for testing woocommerce… http://woo.simplecsr.com is a good example.
I can provide full admin access to this site and you can test anything out there.
Can you please provide an email or secure system to send you the site admin details.
The issue is specifically when there is no selection made in the Tags section of global addons.
I am using a radio field type.
This dev site did not have any existing addons and is a fresh install of your plugin with a new global addon created.
This site is on a default theme. I have disabled all plugins except this addons plugin and woocommerce. It is latest woocommerce and wordpress.
Please let me know how i can supply private access to you.
ChrisFebruary 22, 2017 at 9:56 am #9033
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.
– SeanFebruary 22, 2017 at 11:43 am #9034
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)
– SeanFebruary 23, 2017 at 1:17 pm #9045
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.
– SeanFebruary 27, 2017 at 1:38 pm #9221
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.
ThanksFebruary 28, 2017 at 12:58 am #9230
I have tried the download link from https://mystyleplatform.com/my-account/downloads/ and the same issue exists. (as before it will work with tags but not with categories)
I suspect I am downloading the old version of the plugin.
Can you please check – or supply a new private direct link to the current version of the plugin.
(i have installed this on the http://woo.simplecsr.com test site to check.)
ChrisFebruary 28, 2017 at 10:06 pm #9240
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.March 1, 2017 at 12:05 am #9243
I can verify the download has v1.0.1 in the link – however having tested the performance is identical to before.
Exactly the same issue – that categories selections including All Products will not display the addon. It requires a selection to be made in the tags section before it will work.
Please use the dev site i setup to verify this version is not working and please feel free to delete the current version of the plugin and install another version to test this.
Once signed in the direct link to a new global addon i created is: http://woo.simplecsr.com/wp-admin/edit.php?post_type=product&page=global_addons&edit=229 – you will be able to see this should display on all products but does not.
(My actual requirement uses categories and my use of this plugin is only to add a default pre-checked box to each addon (which a site admin could easily adjust rather than being hard coded) – something the core woo plugin does not do without additional custom coding.)
ChrisMarch 1, 2017 at 12:50 pm #9244
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
– SeanMarch 1, 2017 at 12:58 pm #9245
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!March 6, 2017 at 5:26 pm #9279
Just following up.
Did this workaround to set the “All Products” value work for you?
– SeanMarch 12, 2017 at 5:04 pm #9383
Just following up one more time to see if you got this working OK with the “All Products” setting.
- The topic ‘MyStyle Product Addons wont display existing Global Addons’ is closed to new replies.