Updating to 2.6.5: I think I altered the file setup

  • I have a WordPress blog that I host on A2. I recently upgrade (attempted) to version 2.6.5.

    I first backed up all of the files according to WP’s directions, which created a file called frothy_wp232.sql.

    I then downloaded the ZIP file of 2.6.5. The directions for upgrading stated to “either download and extract it to your computer or download it directly to the server.” I didn’t notice in WinZip that each file’s intended directory was listed; I tried to do what the instructions literally said and put them all in the root directory. I then followed the next instruction, to “delete your old wp-includes and wp-admin directories.” This, obviously, was wrong.

    By this time I realized I had screwed things up, as the files weren’t in their correct directories, so I attempted to restore the database from the backup. I performed the following:

    1. Login to phpMyAdmin.
    2. Click databases, and select the database that you will be importing your data into.
    3. You will then see either a list of tables already inside that database or a screen that says no tables exist. This depends on your setup.
    4. Across the top of the screen will be a row of tabs. Click the Import tab.
    5. On the next screen will be a Location of Text File box, and next to that a button named Browse.
    6. Click Browse. Locate the backup file stored on your computer.
    7. Make sure the SQL radio button is checked.
    8. Click the Go button.

    The import apparently worked fine, as I got a “successful” message, but when I went to the site itself, I got this message:

    Warning: require(/home/frothy/public_html/wp-includes/compat.php) [function.require]: failed to open stream: No such file or directory in /home/frothy/public_html/wp-settings.php on line 117

    Fatal error: require() [function.require]: Failed opening required ‘/home/frothy/public_html/wp-includes/compat.php’ (include_path=’.:/usr/lib/php:/usr/local/lib/php’) in /home/frothy/public_html/wp-settings.php on line 117

    Then, when I attempted to reimport – thinking maybe it didn’t take – I saw this on the import screen:

    Premature end of script headers: php: Please check /usr/local/cpanel/logs/error_log for the exact error.

    I checked with my host and got this response: “Upload your folders again for WordPress. I looked into your account and did not find the /home/frothy/public_html/wp-includes directory and since that directory is not there it can not open the /home/frothy/public_html/wp-includes/compat.php file and read it. Make sure that all your directories are there for your WordPress.”

    I then recreated the two missing folders (wp-includes and wp-admin) and moved all of the folders from the 2.6.5 ZIP file to their correct folders, but when I reimported the database, I got this:

    “Warning: array_keys() [function.array-keys]: The first argument should be an array in /home/frothy/public_html/wp-includes/theme.php on line 315

    Warning: Cannot modify header information – headers already sent by (output started at /home/frothy/public_html/wp-includes/theme.php:315) in /home/frothy/public_html/wp-includes/pluggable.php on line 770″

    A2 said it looked like there was a problem with the theme WP was trying to use and asked if I had tried to change the theme via wp-admin. But I can’t log in to wp-admin. When I visit https://www.frothyruminations.com/wp-admin, I am redirected to a login screen, and when I log in, I am redirected to the same screen (with wp-admin reappended to the URL). So I cannot access wp-admin.

    I know this is long, sorry about that. Here’s my main question (A2 seems to be out of answers):

    Should the wp-admin and wp-includes folders exist only one time (under the main WordPress folder) or twice (under WordPress and public_html)? Right now, they each appear under both folder. I wonder if that’s the problem.

    If you visit the site, it’s completely blank, and I can’t import the backup.

    Any help appreciated. I’m very much a novice at this though, so if you have any advice please dumb it down..

Viewing 2 replies - 1 through 2 (of 2 total)

  • Next time, carefully follow the extended upgrade instructions (not the brief ones). Especially make sure that you follow the instructions about what not to delete.

    Missing or incorrectly installed files or directories do not require you to reimport the database. Adding a reimportation of the database to the problem really confused things.

    If your WordPress was installed in the root, then you should not keep the wordpress folder once you have emptied it.

    As for “Warning: Cannot modify header information – headers already sent”, see: Headers already sent

    You can deactivate a theme by using ftp to delete it from the themes folder. The default WordPress theme will then be used. Make sure that you have downloaded the theme to your computer first if you want to save it.

    Thread Starter frothy

    (@frothy)

    Sir or Madam, thanks. I thought maybe the three-step guide was sufficient. But I appreciate your mixture of helpfulness and sanctimony, hallmarks of www.remarpro.com. The extended instructions will certainly be useful, if there is another time. They can’t help me now, but maybe they will in the future.

    The WordPress is installed in the root and contains wp-admin, wp-content, and wp-includes. These three folders are also in the www folder and the public_html folder, both of which are also in the root. So I wonder if I should delete the WordPress folder (and its subfolders) and leave the ones that are in public_html and www.

    I’m not really sure how to proceed. I have replaced the faulty file that generated the headers error message with one from the latest upgrade, but I wouldn’t know if it’s really been fixed if I am not importing the backup, as you note that it “confused” things before. I’ll just have to look again at the extended instructions tomorrow and redoo what needs to be redone, step by step. Thanks.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Updating to 2.6.5: I think I altered the file setup’ is closed to new replies.