• Resolved fermont

    (@fermont)


    When reading an order using the Woo REST API the line_items meta_data does not include the Unique Option ID which is programmed at the PPOM fields.

    Currently
    – the ‘key’ contains the data_name of the PPOM field
    – the ‘value’ contains the name of the selected options

    In the ‘past’ the ‘value’ contains a JSON array including option, price and id.

    Is this change depending on a specific version of the PPOM add-on?

Viewing 7 replies - 1 through 7 (of 7 total)
  • Hi @fermont,

    can you pleas check in which version you were able to see JSON as value when requested via WC API?

    Thread Starter fermont

    (@fermont)

    Hi,

    Don’t know which version number but when I was creating our internal documentation on PPOM on November 2, 2018. For sure it was working on that date.
    Does this help?

    Is it possible to download an older verion of PPOM somewhere?

    Thank you.

    Thread Starter fermont

    (@fermont)

    Hi,
    I’ve tried with versions 15.2, 15.1, 15.0, 14.3, all the same result.

    “meta_data”: [
    {
    “id”: 118,
    “key”: “select_modifiers”,
    “value”: “No ice”
    },
    {
    “id”: 120,
    “key”: “_reduced_stock”,
    “value”: “1”
    }
    ],

    From a customer that is working perfectly I receive the following meta_data.

    “meta_data”:
    [{“id”:7933,”key”:”velg_mellom”,”value”:”[{\”option\”:\”Kylling\”,\”price\”:\”0\”,\”id\”:\”p49\”}]”},{“id”:7934,”key”:”styrke”,”value”:”[{\”option\”:\”Styrke 1 Chilli\”,\”price\”:\”\”,\”id\”:\”m21\”}]”}]},

    Because of holidays I cannot get in contact with that customer Woo administrator.

    What might create the difference in creating the format of the meta_data?

    Thread Starter fermont

    (@fermont)

    Update.

    I have the version numbers of a working installation.

    Woo 3.5.1
    PPOM 15.1
    WP 4.9.15

    Hope this helps!

    Ok thanks for sharing, actually in latest version we have updated the way we saving meta in orders. We will have to check in order change meta format for options.

    Thread Starter fermont

    (@fermont)

    Ok, thanks for your reply.
    But, what is the solution?
    Will the Unique Option ID be included in the meta again?

    Thanks.

    Hi @fermont,

    Sorry, we have to check it that why this change is made and if there is not big issue to turn it back we can put it back.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Missing unique option id where reading order using API’ is closed to new replies.