Problem with local restore

  • Resolved mirgcire

    (@mirgcire)


    11 years ago

    After following a tutorial for backing up (https://mbrsolution.com/tutorial/backup-restore-wordpress-using-backwpup-plugin.php) and then following one for local restore (https://mbrsolution.com/tutorial/test-your-wordpress-site-locally.php), I ran into a couple of issues.

    The first was HTTP 500 error

    So, I set define(‘WP_DEBUG’, true) in wp-config.
    Then I could see an error message: Warning: mysql_connect(): Access denied for user ‘lightnm0_wor1’@’localhost’ (using password: YES)

    That was weird because I don’t remember creating that user name.
    So (after researching a bit) I queried the DB for the mysql user name which turned out to be “root” w/o password. Then I changed wp-config to reflect this.

    This resolved the first issue, but then I found two things
    1) The site content was displayed, but it was unformatted, as if missing the CSS file
    2) unable to log in – apache seems to be in an infinite loop of port IDs.

    I am hoping, there is some simple fix – it seems so close, yet so far away.
    Thanks,
    -Eric

    https://www.ads-software.com/plugins/backwpup/

Viewing 7 replies - 1 through 7 (of 7 total)
  • Daniel Hüsken

    (@danielhuesken)

    1) Use the browser tools to check waht css file is missing (404). Than check if the file is realy missing local or if the path to file not correct.

    2) did you have made Changing The Site URL

    Thread Starter mirgcire

    (@mirgcire)

    Hi Daniel,

    Thanks for the response. SiteUrl and Home are set correctly.

    The chrome development environment indicates that 5 files are missing, However, they are definitely there. I wonder if it is the version that is the problem?

    The version of jquery.js matches, but the version of style.css does not match.

    GET https://localhost/wpdev/wp-includes/js/jquery/jquery.js?ver=1.10.2 404 (Not Found) localhost/:30
    GET https://localhost/wpdev/wp-content/themes/twentytwelve-child/style.css?ver=3.6 404 (Not Found) localhost/:26
    GET https://localhost/wpdev/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1 404 (Not Found) localhost/:31
    GET https://localhost/wpdev/wp-content/themes/twentytwelve/js/navigation.js?ver=1.0 404 (Not Found) (index):186
    GET https://localhost/wpdev/wp-content/themes/twentytwelve-child/ajax-login-script.js?ver=3.6 404 (Not Found)

    Daniel Hüsken

    (@danielhuesken)

    I think the fastest way to resolve this is download the same WP version von wp.org and overwrite the files.

    Have a look in the archive, if the files located there?

    Thread Starter mirgcire

    (@mirgcire)

    Maybe my previous post was not clear.

    Chrome development environment indicates there are 5 files missing (see previous post), BUT the files are actually there in the exact same path locations as displayed.

    There is just one inconsistency: the version number for one of the files does not match.

    I assume “?ver=3.6” is version number requirement however my “twentytwelve-child” has a version of 0.1.0 not 3.6. So I wonder if the 3.6 refers to the wordpress version. (BTW, the wordpress version on my site is 3.6 so that should actually match)

    Bottom line: there is a contradiction between the error message and reality.

    Thread Starter mirgcire

    (@mirgcire)

    My current status is as follows: Content is displayed correctly, CSS files are not found (even though they exist), and the admin panel can not be displayed. So far I have lost over 5 days trying to verify this plugin.

    Thread Starter mirgcire

    (@mirgcire)

    Good news!

    The problem turned out to be the result of setting the siteurl incorrectly in the DB. I re-installed my previous local site. When it was working correctly, I started checking everything to see if I could notice any difference from the backup. Then I observed this the siteurl set to “localhost” only.

    The WP documentation on setting this parameter is less than helpful:
    ‘The “Home” setting is the address you want people to type in their browser to reach your WordPress blog.
    The “Site URL” setting is the address where your WordPress core files reside.’

    I am still not clear on how exactly to set these, but my guess is that siteurl can be set to localhost because the XAMPP config file is pointing to folder where wp is stored.

    The problem (incorrectly set siteurl) is consistent with the symptoms: the content, pulled from the DB, was all intact, but the none of the other files could be found.

    Anyway, the good news is that I am back on track and it looks like the BackWPup backup has been verified.

    Daniel Hüsken

    (@danielhuesken)

    Nice to hear. I mark this as resolved.

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Problem with local restore’ is closed to new replies.

Tags