restoring WP, reports stack-cache error

  • Resolved nakup36

    (@nakup36)


    1 year ago

    Hi,

    When I restore WP from backup, the backup does not complete and stops at 85%. A critical error is reported when the page is restored:
    Warning: require(/usr/share/php/wp-stack-cache.php): failed to open stream: no such file or directory in /www/konferencesvm.cz/wp-content/mu-plugins/wp-stack-cache.php on line 31.

    Fatal error:(include_path=’.:/usr/share/pear:/usr/share/php:/www/konferencesvm.cz:/www/konferencesvm.cz-tmpdir’) in /www/konferencesvm.cz/konferencesvm. cz/wp-content/mu-plugins/wp-stack-cache.php:31 Stack trace: #0 /www/konferencesvm.cz/konferencesvm.cz/wp-settings.php(456): include_once() #1 /www/konferencesvm. cz/konferencesvm.cz/wp-config.php(26): require_once(‘…’) #2 /www/konferencesvm.cz/konferencesvm.cz/wp-load. php(50): require_once(‘…’) #3 /www/konferencesvm. cz/konferencesvm.cz/wp-admin/admin.php(35): require_once(‘…’) #4 {main} thrown in /www/konferencesvm.cz/konferencesvm.cz/wp-content/mu-plugins/wp-stack-cache.php on line 31

    Only deleting the wo-stack-cache file in mu-cache will help.

    Thank you in advance for your help.

    Translated with DeepL.com (free version)

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

Viewing 1 replies (of 1 total)
  • Plugin Author Yani

    (@yaniiliev)

    1 year ago

    Thanks for the report. The issue was caused by a mu-plugin (wp-stack-cache.php) that references a server-specific path. These kinds of plugins are often installed by hosting providers and aren’t portable, which is why the restore failed at 85%.

    You’re correct that deleting that file resolves the issue.

    If you’re using the Unlimited Extension, you can exclude mu-plugins or specific problematic plugins during export to avoid this kind of issue in the future. Let us know if you’d like help setting that up.

    Let us know if everything’s working now or if you need further assistance.

Viewing 1 replies (of 1 total)

The topic ‘restoring WP, reports stack-cache error’ is closed to new replies.

  • 1 reply
  • 2 participants
  • Last reply from: Yani
  • Last activity: 1 year ago
  • Status: resolved