Import CSV Slug “Type” failure

  • Resolved ccsachs

    (@ccsachs)


    6 years, 8 months ago

    I am attempting to use the built-in WooCommerce Product Import feature. Each time I get a notice that it failed to import and provides a link to see the import log. There I see the reason for failure is that the slug “type” is not allowed because it is a reserved term. It then asks me to change it.
    Image of failure here

    I get this error for each line in the document. I get this when trying to update existing product. I get the same when trying to add new product.

    Seeking help with built-in WooCommerce product import. I am getting slug failures related to “type”.

    Woo: 3.6.5
    WP: 5.2.2
    On localhost (laptop for testing before going live)

    To make sure I was using the correct field headers, I first used the built-in export feature and generated a CSV file. I then added items in empty rows below and added some additional data in empty fields on the existing products. The file was saved as a UTF-8 CSV file.
    In theory this should work.

    This is confusing as “type” was a header in the exported document and, when mapping fields, it was given type as an option. Plus, I need to use the type field to point out that these are simple items, not variable.

    Yes, I know I can probably solve this problem using a paid for plugin. However, this feature is built into Woo. Why pay for a plugin when the feature is included and should work?

    As a test, I removed all the “new” items from the file and attempted to just update the existing items with data I added to empty fields. I received the same failure.
    I also saw on forums that I should try to change the file type to txt, which I did, and had the same failures. I then changed the column header from Type to Derp and made sure to map it correctly for import. Same error. I ran the CSV file thru csvlink.io and no issues. I’ve tried saving the file from Excel and from Google Sheets. I even tried using Notepad, Wordpad, and numerous other software. Same problem.

    I am not having any issues manually entering products. It’s only the import function that is causing issues.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter ccsachs

    (@ccsachs)

    6 years, 8 months ago

    Partial solution found.
    My CSV file had an attribute name called Type. I changed this to TType and the import worked. It appears that this atttribute name was causing an issue with the slug Type.
    So, next issue: my viewers know this attribute as Type, not TType. Any suggestions on how to get past this conflict so that I can use the attribute name “Type”?

    Thread Starter ccsachs

    (@ccsachs)

    6 years, 8 months ago

    And final solution found.
    On the Attributes page on WP I changed the name of the TType attribute to Type and left the slug as ttype. I can now import updates as needed.
    I just have to remember to add the Attribute to Woo on the live site and edit it before trying to import when I get to that stage.

    Phillip C. a11n

    (@phillipwoo)

    6 years, 7 months ago

    Hi,

    Thank you for updating this thread with the solution you found. I’ll mark this issue as resolved now. If you have another issue please feel free to open a new post. 🙂

    Thanks!

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

The topic ‘Import CSV Slug “Type” failure’ is closed to new replies.