after 5.2.63 EAN creation failed & renamed custom fields caused problems

  • Resolved malakontask

    (@malakontask)


    3 years, 5 months ago

    Hi,

    First of all i have to tell you that CTX Feed Pro is an awesome and the fastest XML creation plugin out there i have ever seen, almost without any problems..
    I have right now 2 problems after your latest update 5.2.63
    1. I used woo_feed_ean to update some marketplaces with XML created by your plugin, after this update XML feed couldn’t show the EAN field with “woo_feed_ean” bug ??
    2. I noticed that in 5.2.63 that you added more custom fields and i noticed also that you changed the custom field names from “woo_feed_ean” to “woo_feed_identifier_ean” and that caused me some problems because in XML creation you can choose only one Value to show EAN, the “woo_feed_ean” or “woo_feed_identifier_ean”, the problem here is that i have my old products on “woo_feed_ean” and my new products created after the 5.2.63 on “woo_feed_identifier_ean”. so how can i extract EAN with 2 values ??

    Guys please fix this mess!

    • This topic was modified 3 years, 5 months ago by malakontask.
    • This topic was modified 3 years, 5 months ago by malakontask.
    • This topic was modified 3 years, 5 months ago by malakontask.
Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Ohidul Islam

    (@wahid0003)

    Hi @malakontask This issue is solved into the latest version of the plugin. The latest version will first check the value of woo_feed_identifier_ean meta if the value is empty then it takes the value of woo_feed_ean meta

    Thread Starter malakontask

    (@malakontask)

    Thank you for your fast reply.

    Yes it does that in 5.2.63 but the EAN doesn’t showing in XML feed, i try both values “woo_feed_identifier_ean” and “woo_feed_ean”.
    The only value showing in the XML feed is only this —> <ean/> if the feed is filled with EAN or is empty.

    Hello @malakontask ,

    Please update CTX Feed plugin to the latest version. In this update we tried to solve EAN field issue. Now, woo_feed_ean value is showing value.

    • This reply was modified 3 years, 5 months ago by Mrinal Haque.
    Plugin Author Ohidul Islam

    (@wahid0003)

    Hello @malakontask

    Since we did not hear back from you, we are assuming that you found the solution. We are closing this support ticket.

    If you still need assistance or any other help, please feel free to open a new support ticket, and we will be more than happy to assist.
    Thank you.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘after 5.2.63 EAN creation failed & renamed custom fields caused problems’ is closed to new replies.