Better debug logging?

  • Resolved BertPC

    (@bertpc)


    5 years, 5 months ago

    Hi there. I have the premium version and am running some test migrations before we do the final one. I find I need to re-start the import over and over again, at least several times. The first time (with the free version) it did finish eventually, and I am seeing the same thing with the Premium version.

    With debug logging turned on, I am seeing this error – anything bad about it?

    [16-Sep-2019 02:47:42 UTC] PHP Notice: Undefined index: description in /home/bertpcco/public_html/tms/wp-content/plugins/fg-magento-to-woocommerce-premium/admin/class-fg-magento-to-woocommerce-admin.php on line 2169

    I would like to see more debug logging, like especially a line for perhaps each product it is importing, or even better a line for each aspect of a product, so I can tell that it is proceeding. The % completion goes up by about 6-7% each time I start it, but then stays there for hours and hours — so it seems to just be stopping, but there is no indication of why in the debug log.

    We are definitely going to use this, but am hoping to make the final import process a cleaner and quicker one. Thank you!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Thread Starter BertPC

    (@bertpc)

    Keeping an eye on /wp-content/uploads/fgm2wcp-progress.json, I can see that the total is 5883 and the “current” value increments in small amounts (anywhere from 10-30) every several seconds to few minutes, then eventually just stops updating. I’ve run the process four times so far, and it’s only up to 1351.

    I’m just hoping to figure out what’s stalling the process so much.

    Thread Starter BertPC

    (@bertpc)

    Ran two more times, and it’s up to 1656. At this rate I’ll have to run it as many as 35 more times. ugh… I’m gonna try and put some log statements in the code and see where it’s bombing.

    Anyone else seeing this behavior?

    Plugin Author Kerfred

    (@kerfred)

    This issue is generally due to a timeout or from a memory full on your server.
    You should increase the max_execution_time, max_input_time and memory_limit in the server’s php.ini file.

    If you are on a shared host, you can’t modify the php.ini file. Another solution is to install WordPress on your local computer and run the import in local. In this case, you won’t have the limitations of the shared host. Here is the procedure:
    on Windows: https://www.fredericgilles.net/migrate-wordpress-local-windows-server/
    or on Mac: https://www.fredericgilles.net/how-to-migrate-to-wordpress-from-various-cms-on-a-mac-local-server/

    In any case, if you click again on the import button, it will resume the import where it left off.

    Hi – I’m experiencing the same thing, and my settings are quite liberal already. max_execution_time = 5 hours, max_input_time = -1 (5 hours), memory_limit = 512M.

    Plugin Author Kerfred

    (@kerfred)

    The max_execution_time and the max_input_time should be enough. Try to increase the memory_limit to 1G or 2G. You can come back to lower values after the migration.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Better debug logging?’ is closed to new replies.