Support » Plugin: Markup by Attribute for WooCommerce » Markup : +20 – the description taking over title on options

  • Resolved kak009

    (@kak009)


    Hi Mark,

    Amazing plugin, thank you for all the effort. Once through this, will donate πŸ™‚

    The issue: I tried all your suggestions (in fact several times) by deleting and creating new attributes and variations. Later on, I set the regular price (from dropdown).

    Am getting the “Markup: +20” on a variation (Mouse over)
    https://imgur.com/a/a6bcwWx

    How do I rid this?
    The settings disable isn’t helping.

    Some variations i have disabled in the PHP file before updating the variation.

    Thanks

    The page I need help with: [log in to see the link]

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

    (@marktomlinson)

    Yes, this is a problem with the plugin. The theme you are using pulls up the attribute description, and the ‘Description Behavior’ setting only applies to the product description, not the attribute description.

    Unfortunately, I don’t have any workarounds. This is going to require an update to the plugin, and that will take a few days. I hope to have a new version out to you the first part of next week.

    Thank you for pointing this out.

    Thread Starter kak009

    (@kak009)

    Thank you for the response… Didn’t expect this fast πŸ™‚

    Sure, will wait. Until then I will comment out it in plugin src

    Cheers.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    That should work until I can get a better fix in place. I’ll save you the trouble of hunting for it. Comment out line 229 in markup-by-attribute-for-woocommerce/src/backend/term.php

    228            // Update term description so markups are visible in the term list
    229            // $description .= PHP_EOL . ATTRB_MARKUP_DESC_BEG . $markup . ATTRB_MARKUP_END;

    Afterward, you can just remove the markup information from the attribute descriptions, and the rest should take care of itself.

    • This reply was modified 6 months, 1 week ago by Mark Tomlinson. Reason: Corrected line number
    Plugin Author Mark Tomlinson

    (@marktomlinson)

    After a quick round of testing, I modified the post above to comment out a different line. Please try commenting out line 229 rather than line 242.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    I have released Version 3.10. It should correct your markup-in-the-description problem.

    The reason the markup was in the description is so that it would be visible in the admin attribute list view. I was not aware of any themes or plugins that used the attribute term description, so I (carelessly) reused the field. Version 3.10 remedies the issue by creating a sortable Markup column in the attribute list.

    Version 3.10 does not, however, remove any preexisting markup notations from the description upon installation. You will still have to open each marked-up term and click the [Update] button. Version 3.10 will remove the notation as it updates the term.

    Hope this helps!

    Hi Mark,

    Thanks for putting this plugin together. It’s super helpful!

    I have a similar problem to the one described above even though I have version 3.10.1 of the plugin: I save the attribute description as “10 inches by 10 inches”, but when I click “update”, the markup is automatically added and it becomes “10 inches by 10 inches (Markup: +[value])”

    I’ve tried removing and re-installing the plugin to no avail. I also tested creating a new attribute, but it had the same problem. Any ideas/input on why this is happening would be appreciated.

    Plugin Author Mark Tomlinson

    (@marktomlinson)

    I have no idea how that’s even possible. When you edit an attribute, the table of terms on the right should have a sortable Markup column. If it doesn’t, then there’s some sort of version issue.

    Nevertheless, I have a new version (3.10.3, for WordPress 5.9, WooCommerce 6.1.1, and PHP 8.0.15) that I’m testing right now. I should be releasing it tomorrow. I’d suggest upgrading to that when it’s available, and let me know if it resolves the issue.

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