Not working with WP All Import?

  • Resolved Willem-Siebe

    (@siebje)


    10 years ago

    Hi,

    I just did a test run on my staging site with WP All Import, importing different products with images into the website. However, already very quick the server terminated this process. I found the below in my error log file. Is your plugin having trouble with the import process from WP All Import. Since I saw your plugin name in below error log I disabled your plugin temporarely and that solved it. But I prefer to leave your plugin enabled all the time.

    1-Mar-2015 08:15:33 UTC] WordPress database error Duplicate entry '326-32' for key 'PRIMARY' for query INSERT INTOwp_term_relationships(object_id,term_taxonomy_id`) VALUES (326,32) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:33 UTC] WordPress database error Duplicate entry ‘326-56’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (326,56) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:41 UTC] WordPress database error Duplicate entry ‘329-32’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (329,32) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:41 UTC] WordPress database error Duplicate entry ‘329-57’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (329,57) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:51 UTC] WordPress database error Duplicate entry ‘330-32’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (330,32) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:51 UTC] WordPress database error Duplicate entry ‘330-57’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (330,57) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:57 UTC] WordPress database error Duplicate entry ‘4872-32’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (4872,32) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query
    [11-Mar-2015 08:15:57 UTC] WordPress database error Duplicate entry ‘4872-56’ for key ‘PRIMARY’ for query INSERT INTO wp_term_relationships (object_id,term_taxonomy_id) VALUES (4872,56) made by do_action(‘admin_init’), call_user_func_array, PMXI_Plugin->__adminInit, PMXI_Admin_Import->process, PMXI_Import_Record->process, PMXI_Import_Record->associate_terms, QueryMonitorDB->query`

    https://www.ads-software.com/plugins/query-monitor/

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author John Blackbourn

    (@johnbillion)

    WordPress Core Developer

    Thanks for the report!

    Query Monitor isn’t actually causing the “Duplicate entry” database errors you’re seeing here (they must be caused by something else), but I suspect that QM is contributing to the exhaustion of memory on your server when performing a long-running import, which *is* causing the server to terminate the process.

    Can you take a look at your error log after running the import with QM disabled and see if those “Duplicate entry” errors still appear? I suspect that they will.

    The most likely reason the server is terminating the script is because QM can use a high amount of memory on a script which performs a high number of database queries (ie. hundreds or thousands). This is because QM logs a back trace with every query, and they can get quite large.

    This is something that I’m working on continually.

    Thread Starter Willem-Siebe

    (@siebje)

    Hi, next time I do it again, I will test it with and without QM activated and post the logs. I now know where to find these logs myself, but in the meanwhile I accidently removed the staging site, so for now I have put this issue to resolved!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Not working with WP All Import?’ is closed to new replies.