Support » Plugin: Markup by Attribute for WooCommerce » Upgrade to Version 2.0 — Possible Issues

  • ResolvedPlugin Author Mark Tomlinson

    (@marktomlinson)


    Markup by Attribute for WooCommerce version 2.0 will be released tomorrow evening, July 12, 2018, after testing is completed.

    Because of significant changes in the way Markup by Attribute functions internally, there are some potential issues that may arise after upgrading from Markup by Attribute 1.x to Markup by Attribute 2.0. Although I suspect these will be extremely uncommon, they are known upgrade issues and I feel I should share them along with solutions.

    (For brevity, Markup by Attribute for WooCommerce will be referred to as MbA through the remainder of this post.)

    Option Markup Differs From Actual Markup

    Description

    First off, this is a bug with 1.x and not actually an upgrade issue. If you set a sale price on an item with MbA 1.x and had a percentage markup, then the markups that appear in the drop-down options box will reflect a percentage of the SALE price instead of the regular price.

    Does It Apply?

    This applies only if ALL of the following are true.

    • You have set sale prices while using MbA 1.x.
    • Items on sale include variations with a percentage markup (not a fixed amount).

    (We’ve had one customer report this issue without setting a sale price. You may want to check your own site.)

    Correction

    First, reset the regular price using the ‘Set regular price’ bulk variation function. Then, reset the sale price using the ‘Set sale price’ function. This will repopulate the drop-down box with correct values. This corrects the problem from version 1.x.

    Entire Variation Descriptions Bracketed in <span> Tags

    Description

    MbA 1.0 would completely overwrite variation descriptions with markup descriptions. MbA 2.0 now brackets markup descriptions in HTML <span> tags in order to replace the text without disrupting any other text that may be in the variation description. However, because MbA 1.x left the beginning and end of the markup description ambiguous, MbA 2.0 simply brackets the entire description in <span> tags during the conversion to version 2.0. This means any text you may have entered into variation descriptions while using MbA 1.0 may be within the <span> tags and can potentially be overwritten.

    Does It Apply?

    This applies only if ALL of the following are true.

    • You added descriptive text to variations that also included markup descriptions while using MbA 1.x.
    • You did NOT overwrite the markup description provided by MbA 1.x but included your own text before or after the markup description.
    • You change the regular price of the product causing MbA to rewrite the markup description.

    Correction

    You may correct this with EITHER of the following.

    • Manually edit the variations in question and move your descriptive text outside of the <span> tags before re-pricing products.
    • Leave the description alone until such time as the product is re-priced. Then re-enter your descriptive text outside of the <span> tags where necessary.

    Increase / Decrease Sale Price Does Not Work on Sales Price Set in 1.x

    Description

    MbA 1.x did not handle the bulk variation edit functions to increase or decrease the regular and sale prices correctly. MbA 2.0 has corrected this issue. But MbA 2.0 needs to record the base regular and base sale price to perform this function, and can not determine the base sale price if it was set in MbA 1.x.

    Does It Apply?

    This applies only if ALL of the following are true.

    • You set sale prices on products with markups while using MbA 1.x.
    • You intend to use either the ‘Increase sale price’ or the ‘Decrease sale price’ functions on these variations.

    Correction

    The easiest workaround is to use the ‘Set sale price’ function instead. If you prefer using the increase or decrease functions, you can reset the sale price to its current value and then the increase and decrease sale price functions will work properly from there on out.

Viewing 1 replies (of 1 total)
Viewing 1 replies (of 1 total)
  • The topic ‘Upgrade to Version 2.0 — Possible Issues’ is closed to new replies.