WordPress.org

Forums

[resolved] Moving and older site to a test - blank dashboard (13 posts)

  1. SoCalCreations
    Member
    Posted 10 months ago #

    PURPOSE: to make a complete copy of the site on the test server. Then upgrade from v3.3 to v.3.9.1. I expect the theme WILL BREAK during the upgrade according to the research. Therefore the plan is to revert to TwentyEleven, update WP and then see if the client theme will work with v3.9.1.

    Current WordPress site
    - http://blog.picturebakery.com
    - WP v3.3
    All files backuped
    Database exported using phpMyAdmin

    Moving to Test Server
    - Created Database (same name, except for mandatory prefix)
    - Created DBUser (same name, except for mandatory prefix)
    - imported database
    - edit DataBase "wp_options" table changed "siteurl" to new test server url [option id 1]
    FROMhttp://blog.picturebakery.com
    TO http://picturebakery.socalcreations.net
    - edit DataBase "wp_options" table changed 'home' to new test server [option id 37]
    FROMhttp://blog.picturebakery.com
    TO http://picturebakery.socalcreations.net

    UPDATED "WP-CONFIG.PHP" FILE
    Changed two lines
    define('DB_NAME', 'NEWPREFIX_SAMEDBNAME');
    define('DB_USER', 'NEWPREFIX_SAMEUSERNAME');
    no need to change the DB_PASSWORD as it was set the same.

    RESULTS
    Transferred site looks and acts just like original from visitor perspective
    Original: http://blog.picturebakery.com
    Transferred: http://picturebakery.socalcreations.net
    So Far So Good.

    PROBLEM
    Login screen looks fine for both admin and user login, however after logging in only the menu appears on the left of the dashboard and nothing of a dashboard or any response to any menu click (see image http://screencast.com/t/zV46GBz8pWZw)

    ATTEMPTS Tried
    NOTE: EVERY ATTEMPT BELOW STARTED WITH THE ABOVE STEPS REPEATED SO AS TO TRULY ISOLATE.

    - Change Theme in SQL via http://www.inmotionhosting.com/support/edu/wordpress/change-theme-in-db FAILED

    - Removed ALL Plugins not part of original v3.3 FAILED

    - Got WP v3.3 from archive on WP.org & uploaded those FAILED

    - Did a WordSearch in the SQL Backup file for
    "blog.picturebakery.com"
    and changed all 700+ instances to "picturebakery.socalcreations.net"
    Then Imported FAILED

    ALL FAILS RESULT IN THE SAME (see image http://screencast.com/t/zV46GBz8pWZw)

    I am sort of out of ideas and research, so any one here with a couple of years of transferring site under them have any ideas?

    Thanks

  2. linux4me2
    Member
    Posted 10 months ago #

    Did you change both the "siteurl" and "home" records in the wp_options table to your new, test domain, or did I miss that in your list? It looks like you only change the "home" record.

    The next thing to do is to check your error log for the PHP error that is occurring on your Admin side, accounting for the mostly blank page. Depending on how your server is set up, you may have error_log files in the folders were the error(s) occurred. The PHP error may point you to the cause.

    The next thing I'd look at is your .htaccess file to make sure nothing in there is causing a problem.

  3. SoCalCreations
    Member
    Posted 10 months ago #

    Hi Linux,

    Yes you missed it in the list. Both the Siteurl and home were changed in the wp_options.

    No error_log was generated in the subdomain or the main account one level up.

    .htaccess file is stock WordPress.

    Keep them coming ;)

  4. SoCalCreations
    Member
    Posted 10 months ago #

    I take that back I did find some error logs from the hosting server, which are not written in the directories. Here they are, a bit sanitized

    /myhostingacct/public_html/picturebakery/wp-admin/error_log:

    [03-Jul-2014 07:29:28 UTC] PHP Fatal error: Access to undeclared static property: WP_Screen::$this in /myhostingacct/public_html/picturebakery/wp-admin/includes/screen.php on line 706

    [03-Jul-2014 16:50:45 UTC] PHP Fatal error: Access to undeclared static property: WP_Screen::$this in /myhostingacct/public_html/picturebakery/wp-admin/includes/screen.php on line 706

    /myhostingacct/public_html/picturebakery/wp-includes/error_log:

    [16-Jul-2013 14:52:13] PHP Fatal error: Call to undefined function _deprecated_file() in /home/sherym/public_html/picturebakery.com/blog/wp-includes/registration-functions.php on line 7
    The above references the moved from server where it is running live

    /myhostingacct/public_html/picturebakery/wp-content/plugins/error_log:

    [18-Apr-2014 19:41:04] PHP Fatal error: Call to undefined function add_action() in /home/sherym/public_html/picturebakery.com/blog/wp-content/plugins/hello.php on line 60
    Here again the above references are from the server where it is running live

    /myhostingacct/public_html/picturebakery/wp-content/themes/prophoto2/error_log:

    [13-Mar-2013 04:16:37] PHP Fatal error: Call to undefined function get_header() in /home/medgush/public_html/picturebakery.com/blog/wp-content/themes/prophoto2/index.php on line 1
    Here again the above references are from the server where it is running live

    I can think of a few different things here, but I am open to some experienced peoples opinions.

  5. SoCalCreations
    Member
    Posted 10 months ago #

    Looking at it with Firebug I see something interesting, but don't fully understand it.... anyone?

    http://screencast.com/t/RgzK0Q4eRD

  6. linux4me2
    Member
    Posted 10 months ago #

    The relevant errors, going by the dates, are these:

    [03-Jul-2014 07:29:28 UTC] PHP Fatal error: Access to undeclared static property: WP_Screen::$this in /myhostingacct/public_html/picturebakery/wp-admin/includes/screen.php on line 706
    
    [03-Jul-2014 16:50:45 UTC] PHP Fatal error: Access to undeclared static property: WP_Screen::$this in /myhostingacct/public_html/picturebakery/wp-admin/includes/screen.php on line 706

    At this point, you have the site moved to the test server, but what version of WP are you using and what theme is active?

  7. SoCalCreations
    Member
    Posted 10 months ago #

    Linux4me, please re-read initial post.

    As for the theme it is a purchased theme, very out of date, just like the wordpress.

    The purpose is to recreate it on the test server then process any upgrades.

    In the file mentioned in the error log, there isn't a clear indication of what the error is. I had to back track it through multiple files, but it's beyond my current knowledge of php.

    I did do a file comparison of all backed up files from my method and the hosting cpanel method.... they are exact.

  8. linux4me2
    Member
    Posted 10 months ago #

    So you're working with a supposedly identical install of WP 3.3 and an old theme. It wasn't clear to me from reading through your initial post.

    Here's the answer to where that error is coming from and the solution is to upgrade WP.

    Since you're working on a test server, if it were me, I'd take the plunge and upgrade WP first after reverting to Twenty Eleven as you planned, then see what kind of errors your old theme is causing and either fix them or switch themes to something 3.9.1-compatible.

  9. SoCalCreations
    Member
    Posted 10 months ago #

    linux

    I truly appreciate the journey you are taking with me, but reverting to another theme is part of the problem, since I can't see the dashboard. See an example http://screencast.com/t/RgzK0Q4eRD

    As I mentioned in my initial post I attempted to Change Theme in SQL via http://www.inmotionhosting.com/support/edu/wordpress/change-theme-in-db

    However that FAILED

    Do you know of another way?

  10. linux4me2
    Member
    Posted 10 months ago #

    I usually just delete the broken theme's folder from /wp-content/themes, but you need to have one of the default themes there first. If you don't have one already, you can upload it from the package of WP you downloaded previously.

  11. kiev707
    Member
    Posted 10 months ago #

    change php version.. that probably will help

  12. linux4me2
    Member
    Posted 10 months ago #

    If renaming/deleting the broken theme folder doesn't get you back your Dashboard so you can do a one-click update of WP, then the next thing I would try would be a manual update of WP.

  13. SoCalCreations
    Member
    Posted 10 months ago #

    Kiev - I didn't mention that, but that was tried as well. I have a great hosting company that allows for quite flexible configurations.

    Linux - okay I decided, what the hell, it's only a test site....even though I was trying to learn, I simply gave up and decided to try the manual upgrade.

    The Theme Company said the current theme would NOT work with WP v3.9.1 upgrading from v3.3. I am guessing that was 'marketing scare tactics' i.e. 'we want more money for our latest theme and we will toss in support'

    uh-huh, right.

    Dropped in all the new WP v3.9.1 files, just over wrote everything. Did the \wp-admin\upgrade and it told me the DB needed updating, so OK, then the DASHBOARD appeared. COOL, Did NOT expect that.

    Bounced to the public view and What do you Know, the site remained alive and well as it was, which was poor in my opinion, but that's why I got the job.

    Anyway aside from 2 plugins and base WP themes asking to be upgraded, so far so good after 30minutes of poking and prodding.

    I truly wanted to know the reason why this issue took place and have an interesting learning experience, however, the outcome is the outcome.

    Thanks for the Journey Linux, I appreciate your input. I hope this thread helps others in the future.

    -Will

Reply

You must log in to post.

About this Topic