Support » Plugin: Prime Mover » “invalid site footprint” while exporting

  • Resolved mhurwicz

    (@mhurwicz)


    I have exported several WordPress blogs from this same hosting account with no problem. I notice in the Prime Mover migration log says Blog ID 1, whereas I am entering blog ID 18. Perhaps this is the problem?

    latest version of Prime Mover (1.0.3)

    export to multisite
    blog ID 18
    shows “Dumping database”
    shows “Copying media files”
    Then “Invalid system footprint” in red

    link to phpinfo output: http://prime-mover.s3-website-us-west-2.amazonaws.com/phpinfo.html

    Health Check: result is “good”, no critical issues, recommended changes are:
    You should remove inactive plugins (Security)
    Your PHP version should be updated (Performance)
    One or more recommended modules are missing (Performance)
    Your site does not use HTTPS (Security)
    Your site is not using localized timezones (Performance)

    enabled WP_DEBUG and WP_DEBUG_LOG

    Deactivated all plugins except Prime Mover

    When going to export function:

    Warning: include(/home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-settings.php on line 95

    Warning: include(): Failed opening ‘/home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-content/advanced-cache.php’ for inclusion (include_path=’.:/opt/alt/php71/usr/share/pear’) in /home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-settings.php on line 95

    Download WP_DEBUG log and see screenshot of the error here:
    http://prime-mover.s3-website-us-west-2.amazonaws.com

    add to wp-config.php:
    define(‘PRIME_MOVER_LOG_PATH’, ‘/home/myaccount/public_html/mydomain.com/leonidhurwicz/poiyroiewquy15253.log’);

    log pasted into: https://pastebin.com/VrN7PyfM

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

Viewing 11 replies - 1 through 11 (of 11 total)
  • Plugin Author Codexonics

    (@codexonics)

    Thanks for reporting this issue and for all the logs. Usually this occurs when exporting a site that is already having configuration problems (by itself). For example, exporting a site without an active theme activated in dB but deleted, invalid site url, etc. Based on the log provided, it shows it indeed fails on footprint validation.

    The current version 1.0.3 does not yet include a detailed logging to see the footprint data in details. We will add it on the future version. To understand the issue, we want to know what part of the footprint is missing or invalid. Can you please do the steps below:

    1. Download this Prime Mover footprint logging plugin.
    2. Log-in as administrator go to Plugins -> Add New and upload that plugin zip: prime-mover-footprint-log.zip.
    3. Activate the plugin named as: Prime Mover Footprint Log
    4. Enable all logs as what you have done first time when you report this issue
    5. Now the footprint log is enabled, re-generate the export (to reproduce the error) so it will re-generate another set of logs (now including footprint which we need to analyze).
    6. Update the log in your pastebin with the latest log containing footprint data: https://pastebin.com/VrN7PyfM
    7. You will know that the footprint data is logged when it contains “Custom log for site footprint data” in the log. Let me know if this is added so I’ll re-check the log for analysis. Thank you !

    Plugin Author Codexonics

    (@codexonics)

    Also it seems this error:

    Warning: include(/home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-content/advanced-cache.php): failed to open stream: No such file or directory in /home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-settings.php on line 95
    
    Warning: include(): Failed opening ‘/home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-content/advanced-cache.php’ for inclusion (include_path=’.:/opt/alt/php71/usr/share/pear’) in /home/myaccount/public_html/mydomain.com/leonidhurwicz/wp-settings.php on line 95

    is not related to Prime Mover. But that is usually caused by having a caching plugin incorrectly deactivated. It’s deleted directly in the plugins directory while the caching files or caching are still enabled. This can probably affect the export process.

    Try commenting or removing this in your wp-config.php if you have this line:
    define('WP_CACHE', true);

    And then delete these file or folder inside your /wp-content/ if you still have this:

    • cache folder
    • w3tc-config folder
    • advanced-cache.php’

    In my test that removes the error in your debug.log (caching related error) but I’m not sure if this will resolve the Invalid system footprint erro. I’ll wait for your site footprint data to see it.

    Thank you! The new log is at https://pastebin.com/ap4UCQ0Y

    • This reply was modified 9 months, 2 weeks ago by mhurwicz.
    Plugin Author Codexonics

    (@codexonics)

    Thanks but it seems it still showing the old log, did you activate the foot print logging plugin? Or did you save it to pastebin again?

    The new log should contain the phrase Footprint keys for validation. Please review.

    Sorry, I guess I haven’t figured out how to edit the pastebin. Here’s a new one instead: https://pastebin.com/ap4UCQ0Y

    Plugin Author Codexonics

    (@codexonics)

    That’s the correct log. Give me time to analyze and I will get back to you. Thanks.

    Plugin Author Codexonics

    (@codexonics)

    OK I found the issue after checking the updated logs. Prime Mover checks the theme version used when exporting so it can be compared during restoration process to check for theme differences. It’s included as required footprint of the source site. It is why without this, it returns invalid system footprint error.

    The exporting site is using a child theme Divi-child that does not include a theme version.

    To fix the error, can you please add a version to your child (Divi-child)? This is done in the child theme style.css file.

    For example from: (before)

    
    /*
    Theme Name:   Divi Child Theme
    Theme URI:    http://xxx.com
    Description:  Child theme, based on Divi
    Author:       xxx xxx
    Author URI:   http://xxx.xxx
    Template:     Divi
    */
    
    @import url("../Divi/style.css");
    

    TO: (after -this is the right way – including theme version)

    
    /*
    Theme Name:   Divi Child Theme
    Theme URI:    http://xxx.com
    Description:  Child theme, based on Divi
    Version:      1.0.0
    Author:       xxx xxx
    Author URI:   http://xxx.xxx
    Template:     Divi
    */
    
    @import url("../Divi/style.css");
    

    Reference: https://developer.wordpress.org/themes/advanced-topics/child-themes/#2-create-a-stylesheet-style-css

    Try this one and the export error should be resolved. Let me know how it goes 🙂

    Prime Mover has exported a file!

    Inserting the version number in styles.css did make the process run beyond where it had before, to exporting themes. However, it stalled there and did not complete even after around five hours.

    So I aborted that process (just x’d out of the page), activated the main Divi theme (instead of the child theme) and deleted both the child theme and the standard WordPress 2019 theme. (I had not really done anything with the child theme, just created it since it’s considered a “best practice”.)

    The process then ran to completion.

    I have not imported it yet.

    Thanks very much for all your help!

    • This reply was modified 9 months, 2 weeks ago by mhurwicz.
    Plugin Author Codexonics

    (@codexonics)

    Thank you for confirming the fix works. The stalling on export and import is a known issue with version 1.0.3 that is caused by web server timeouts. We are on the process of adding an improvement to this one and will be included in the next release version 1.0.4.

    If you are affected again with this issue, please create a separate ticket. And we will provide you with a beta version to test. Cheers.

    Tried to import the file using 1.0.3, but had problems:

    https://community.bitnami.com/t/redirects-from-main-domain-to-static-ip-sign-up-then-says-registration-is-disabled/70572

    Perhaps I should start a new ticket here, too?

    We already have an ongoing ticket here: https://wordpress.org/support/topic/requesting-beta-of-1-0-4-to-cure-import-stall/

    So let’s continue the discussion there. I’ll post an update there right now.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘“invalid site footprint” while exporting’ is closed to new replies.