Error 403 when importing product csv selecting ; as delimiter

Hi @bigblack

Thanks for reaching out!

I understand that you are encountering a 403 Forbidden error when trying to import products using a CSV file with a semicolon (;) delimiter after updating WooCommerce to the latest version.

As a first step, can you please confirm if you are using the built-in Product CSV Importer and Exporter here? If so, please share with us the CSV file you are using here for us to check this further.

Meanwhile, please check that you are following the correct format for your CSV file as discussed on this support documentation.

Otherwise, if you are using a third-party plugin or a custom code, it would be best to reach out to the developers for further assistance here.

Thanks!

Hi, yes I’m using the built-in Csv Importer, the file is not changed. I’ve used it yet with previous Woocommerce import. Exactly 2 hours befere the update. If i put the comma import go on to the column selection screen. If i put the semicolon I get 403 error. So i’ts not a csv file problem but a woocommerce kind of bug.

Hi @bigblack

In this case, I would like to suggest the “Import All Pages, Post types, Products, Orders, Users as XML & CSV” – ( https://www.ads-software.com/plugins/wp-ultimate-csv-importer/ ) plugin.

This plugin is a popular and reliable solution for importing CSV files into Woocommerce. It supports multiple file formats and allows you to import a wide range of data types such as products, orders, users, and more.

It’s also worth noting that this plugin has received positive reviews from its users and has a good track record of compatibility with the latest Woocommerce updates.

I hope this information helps you in finding a suitable solution for your import needs. If you have any further questions, please don’t hesitate to ask on this thread.

Hi @bigblack

For us to investigate this further, can you please share with us the CSV file you are referring to here so that we can take a closer look?

Thanks!

Problem solved by the siteground customer care. It was a line in htaccess. I didn’t changed nothing in it but maybe a plugin write something wrong on it.

Hi @bigblack

I’m glad you were able to find a solution to your inquiry here and thanks for sharing it with the community too! ??

Meanwhile, if you have a moment to spare, we would love it if you could share your thoughts with us by leaving a review or feedback. Your experience and feedback are important to help us improve and ensure we’re always providing the best possible support.

Thanks!