Support » Plugin: Markup by Attribute for WooCommerce » Conflict With Other Plugin

  • Resolved mikeward

    (@mikeward)


    This looks like the PERFECT solution for the issue I have been wrestling with, but… My site is using WooCommerce Attribute Swatches by Iconic and activating this plugin deactivates the swatches for the Iconic plugin and reverts them to the drop downs.

    Any ideas on a work around. I think your plugin solves a big issue for me, but I have put a ton of work into the swatches already.

    Thanks in advance!

Viewing 13 replies - 1 through 13 (of 13 total)
  • Plugin Author Mark Tomlinson

    (@marktomlinson)

    I’ll need to download the free trial of WooCommerce Attribute Swatches and cancel before I am billed. That will give me two weeks to test.

    But first, can you try something for me as a workaround?

    1. Go to WooCommerce > Settings > Products > Markup by Attribute
    2. Under Option Drop-down Behavior, select Do NOT show the markup in the options drop-down box.
    3. Let me know what happens.

    The results will give me an idea of how to fix the issue.

    Mark,

    First thanks for the very quick turnaround!

    I took the actions you suggested and it appeared to have no effect on the behavior.

    If you wish, I can turn it on and send you a page to view, but it is a busy season for me, and I would prefer not to leave it on too long, so would like to arrange some time to do that.

    Let me know and thanks again!
    Mike

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Okay, so they are using the ‘woocommerce_dropdown_variation_attribute_options_html’ filter to display the swatches, which is what I use to add the markup in the dropdown box.

    I believe I can modify Markup by Attribute so that the ‘Do NOT show the markup’ setting will not override the swatches with a dropdown box. But that would mean the swatches would not display the markup.

    Would that be workable?

    (P.S. I do have a heavy-handed idea of changing the tag names. For instance “Blue” turns into “Blue (Add 2%)”. Since the slug would remain “blue” I think it might work without breaking everything. Maybe. But I’d rather go with the above solution for the short-term.)

    Mark, 

    Wow, thanks, but you are a little over my head here. I have been doing this a long time, but I more of a front end guy.

    Can I say, whatever you think best?

    Let me what I can do or if there is more info you need from me, and thanks.

    Mike

    Mark,

    Understanding you are probably still looking into this, just checking in to see how it is going.

    Thanks again!
    Mike

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    I hope to have a patch for this later today. It may not be downloadable till Monday, though, because I’ll have to do some pretty thorough testing.

    No worries Mark. Just truly appreciate your attention to this.

    Try to enjoy your weekend.

    Mike

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    You might want to check version 3.3, which I just pushed out.

    Now, if you use Do NOT show the markup in the options drop-down box option, WooCommerce Attribute Swatches should work.

    But, I figured that was not good enough and a bit obtuse. So, go to WooCommerce > Settings > Products > Markup by Attribute and look for Include the Increase (Decrease) in the Term Name. This option will put the markup amount or percent in the attribute term name when you save the attribute, and then it will disable the code to overwrite the drop-down box. And, it means you can still have the markup appear with the swatch name if you want.

    To make it work, you have to open and save each of the attribute terms with a markup. This will force Markup by Attribute to rewrite the name with the markup appended to it. Also, you’ll want to select an option other than Do NOT show the markup in the options drop-down box since Include the Increase (Decrease) in the Term Name respects the Option Drop-down Behavior selection.

    Please let me know if it works for you.

    Mark,

    First, I truly appreciate the effort. You are going way above and beyond the typical ‘disable the other plugins’ responses that I seem to get with other devs.

    That said, I am not sure it is working as designed quite yet. Here is what I am seeing.

    I reactivated the plugin, did all the settings as you mentioned. I went into add an attribute price to an attribute and three things happened:

    I got an error message at the top of the page that said: “Sorry, an issue occurred when attaching the image you selected. Please try again.” This message was repeated twice at the top of the page, and reattempts caused the same error, even when I did not set an attribute image (left swatch set to none).

    Although it gave me the error message, the icon appeared, but was extremely distorted, like the resolution was wrong.

    The markup I added did not stay set. That block appeared empty after the save, and when I closed out and came back in.

    I have a screenshot of this if you are interested.

    Let me know your thoughts, and once again, thanks for the effort!

    Mike

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Sigh. I thought for sure this would work. But apparently, the conflict runs deeper than I imagined. We both must be stepping on each other in the attribute term update routine.

    Unfortunately, since the issues you mention are mostly coming from the other plugin, I’m helpless in trying to diagnose them. I have no idea how I would change Markup by Attribute’s update routine to avoid the conflict.

    You may want to reach out to Iconic to see if they have any suggestions, but I’m guessing they’ll tell you to disable Markup by Attribute. Unfortunately, I may have to come to the same conclusion.

    🙁

    Mark,

    Truly appreciate the effort. I will dig and let you know if I find anything out.

    Cheers.
    Mike

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Not hearing anything else, I’ve decided to close this issue.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    Closing issue.

Viewing 13 replies - 1 through 13 (of 13 total)
  • You must be logged in to reply to this topic.