Support » Plugin: WooCommerce PDF Invoices & Packing Slips » Memory exhaust (512M) after server migration

  • Resolved jorugar

    (@jorugar)


    Hi team, we are trying to migrate the page from our current hosting provider to a owned server. The migration is working fine if accessing the frontpage, but when we login into the backend we get a memory size exhaust error.

    We has incresed the memory up to 2GB for trying but get the same error. We has disabled all plugins and enabling one by one until we get yours is the responsible of the memory crash.

    I tried delete and reinstall the plugin, but whe we enable de plugin, we have the memory problem another time.

    Can you provide some information???? Thanks in advance.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Ewout

    (@pomegranate)

    Hi! I’m sorry to hear that! We’re not aware of any issues like the one you’re describing.
    Can you post the exact error you’re getting? That will help us narrow down the issue to a specific PHP process.

    Thanks!
    Ewout

    jorugar

    (@jorugar)

    Hi again team,
    After some tests, disable and re-enable the plugin, delete it and reinstall nothing works; we did a deeper investigation and discover something is working wrong with your plugin:
    – Delete action from the plugins section, do not clean the database and any configuration is refreshed installing the plugin again.
    – Origin of the error is not managed or reported on the logs.
    – Error is on some static paths saved in DB configuration of the plugin. Those paths are not relative to the wordpress installation path and after migrating the website to other hosting server are pointing to non existing paths.

    We fixed the error replacing the paths on the dump file before import it to the new databese. You may correct that to make the paths relatives or to clean or refresh the config if delete and reinstall the plugin.

    Plugin Author Ewout

    (@pomegranate)

    Hello Jorugar,
    Thanks for the report!
    Since version 1.4.4 (and some improvements for alternative folder stuctures like Bedrock in 2.0.8), paths to the template files are stored relatively to the site base. However, if you have been using the plugin for a long time, it’s possible the paths were indeed still absolute. I have done many migrations myself without any issues.

    Here’s an example of the settings as stored on one of my staging sites (table: wp_options, option_name: wpo_wcpdf_settings_general):

    
    array (
      'download_display' => 'display',
      'template_path' => 'wp-content/plugins/woocommerce-pdf-invoices-packing-slips/templates/Simple',
      'paper_size' => 'a4',
      'currency_font' => '1',
      'header_logo' => '',
      'shop_name' => 
      array (
        'default' => '',
      ),
      'shop_address' => 
      array (
        'default' => '',
      ),
      'footer' => 
      array (
        'default' => '',
      ),
      'extra_1' => 
      array (
        'default' => 'Extra 1',
      ),
      'extra_2' => 
      array (
        'default' => 'Extra 2',
      ),
      'extra_3' => 
      array (
        'default' => 'Extra 3',
      ),
    )
    

    As you can see, the path is relative, starting with wp-content.

    So I’m not sure why this was not working for you, but I’d like to fix this if possible.
    Could you try the following?

    • Go to WooCommerce > PDF Invoices > General
    • Save the settings (to make sure it’s not stored as an absolute path if that’s how you have set that up now)
    • Check the option wpo_wcpdf_settings_general in the wp_options table in your database

    If that is still the absolute path, could you send us an email at support@wpovernight.com so we can investigate the issue?

    We don’t delete the settings when the plugin is deleted because sometimes people need to temporarily delete the plugin and don’t want to lose their settings. This shouldn’t be an issue when the paths are relative, but if that’s not working on some configurations obviously we need to fix that.
    I hope you’re willing to cooperate for that, thanks in advance!

    Ewout

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Memory exhaust (512M) after server migration’ is closed to new replies.