WC 3.0

Hi @dima-stefantsov

Can you please elaborate on which function(s) we’re using that have been deprecated?

Hi. Looks like it was my code that was using $product->id instead of ->get_id(), not your. Was going to wait for current import completion to be 100% sure I was wrong. Sorry.

Your code still has

[06-Apr-2017 05:36:06] WARNING: [pool www] child 65027 said into stderr: "NOTICE: PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's'' at line 1 for query SELECT slug FROM wp_terms WHERE name = 'Let's' made by do_action('admin_init'), WP_Hook->do_action, WP_Hook->apply_filters, PMXI_Plugin->adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMWI_Import_Record->import, wp_insert_term, sanitize_title, apply_filters('sanitize_title'), WP_Hook->apply_filters, ctl_sanitize_title"

[06-Apr-2017 05:43:19] WARNING: [pool www] child 65029 said into stderr: "NOTICE: PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's Cook'' at line 1 for query SELECT slug FROM wp_terms WHERE name = 'Let's Cook' made by do_action('admin_init'), WP_Hook->do_action, WP_Hook->apply_filters, PMXI_Plugin->adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMWI_Import_Record->import, wp_insert_term, sanitize_title, apply_filters('sanitize_title'), WP_Hook->apply_filters, ctl_sanitize_title"

[06-Apr-2017 05:44:40] WARNING: [pool www] child 65037 said into stderr: "NOTICE: PHP message: WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 's'' at line 1 for query SELECT slug FROM wp_terms WHERE name = 'Rubik's' made by do_action('admin_init'), WP_Hook->do_action, WP_Hook->apply_filters, PMXI_Plugin->adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMWI_Import_Record->import, wp_insert_term, sanitize_title, apply_filters('sanitize_title'), WP_Hook->apply_filters, ctl_sanitize_title"

which was hard for me to reproduce on your test servers, but it just happened few minutes ago on big 150MB .csv file.

There’s also two more issues:
1. latest chrome v57, no extensions (tried in incognito mode) using more and more RAM over time, may crash (chrome dead face x_X crash) during import process.

2. continuing import from where it was last time takes WAY too much RAM. After 70000 products was processed, looks like it is trying to read all products (I notice 300 selects / second in mysql), and it also looks like it stores everything in it’s php memory. PHP process grows about 5GB in size before it loads all 70000 previous products and goes on in small batches of 20, by default, which goes easy on my RAM.

If I’d import files with few hundreds thousands of records, I will run out of RAM if I try to continue. Coupling with Issue #1 this is quite serious.

Hi @dima-stefantsov

Your code still has [errors] which was hard for me to reproduce on your test servers, but it just happened few minutes ago on big 150MB .csv file.

Can you please open a support ticket at https://www.wpallimport.com/support/ with details about this issue, and include the URL + login details for the test site so that we can look into this?

There’s also two more issues:

1) If your browser is crashing during the parsing of the data, you’ll need to split the import file and import less records at a time.

2) Can you please replicate this issue at https://www.wpallimport.com/debug/ and open a support ticket at https://www.wpallimport.com/support/ referencing this ticket so that we can dig into this and see what’s going on?

1) If your browser is crashing during the parsing of the data, you’ll need to split the import file and import less records at a time.

That’s really weird thing to say. It seems there’s some “memory leak” with your import page. I guess you have running text there, it’s emptied from the screen, but maybe it never emptied from memory. Or some service JS variables not getting emptied ever. This would be the reason for browser used ram to rise this high.

This is on your side to fix, not mine. In all other cases, industry standard browser (chrome) is not crashing here.

Since you ask me to reproduce it, I guess this is something unusual for you, and continuing import from 70000 items should not eat 5gb ram. Ok.

Hi @dima-stefantsov,

Since you ask me to reproduce it, I guess this is something unusual for you, and continuing import from 70000 items should not eat 5gb ram.

That’s correct, so far you’re the only report we have of this happening. We’d like to take a closer look so that we can determine the root cause of the errors you’re encountering.

In order for us to take a closer look, we need you to reproduce the problem (just the problem, not your whole site) on a testing install and submit support request to us: https://www.wpallimport.com/support/

Thank you!

For other users viewing this thread, these error messages were coming from a different plugin or theme.

• This reply was modified 7 years, 7 months ago by WP All Import.