Restore failed: …line 249…check permissions

  • Resolved gamattox

    (@gamattox)


    5 years, 9 months ago

    I have successfully migrated from restoration files many times in order to move the website from development to production. Today the restoration/migration failed with the following error:

    Warning: copy(): The first argument to copy() function cannot be a directory in C:\wamp64\www\mywebsite\wp-admin\includes\class-wp-filesystem-direct.php on line 243
    Error message: Could not move old files out of the way. You should check the file ownerships and permissions in your WordPress installation (C:/wamp64/www/mywebsite/wp-content/languages)
    Restore failed…

    There is plenty of file space
    The plugin is up to date on both dev and prod machines
    I deleted cache files and turned off cache on the dev machine prior to backing up
    I deleted cache files and turned off cache on the server prior to restore/migration
    The “languages” folder in the error message is empty on both dev and prod
    The website appears to be 100% functional even though restoration says it failed

    I see others have hade the same problem but no definitive answer to how they cleared it up. The error simply mysteriously stops. Does anyone have an clear idea on how to clear up this failure to restore? Does anyone have any ideas on where to look next?

    Thanks

Viewing 1 replies (of 1 total)
  • Plugin Contributor DNutbourne

    (@dnutbourne)

    Hi,

    Please could you send us a copy of the restoration log?
    This can be found in the wp-content/updraft directory of the site, via FTP or your hosting filemanger.

    The contents will be too long to post here directly, but you can use an online service such as Pastebin, and post the link here

    Please could you (or your hosts/server admin) check the file permissions and ownership for the wp-content folder? This error can be caused if WordPress does not have permission to read/write to a directory.

Viewing 1 replies (of 1 total)
  • The topic ‘Restore failed: …line 249…check permissions’ is closed to new replies.