• I tried to upgrade from 1.2 to 1.5. When I did, my blog page was completely blank! (Thank goodness, I didn’t delete all those files, just renamed the folder and so I was able to get everything back.)

    In the Admin area, everything looked fine. My last post was there and it looked like everything else was there, too. But if I clicked View Site or browsed directly to the page, the page was blank.

    I also had these error messages in the Presentation page:
    WordPress database error: [Unknown column ‘autoload’ in ‘field list’]
    INSERT INTO wp_options (option_name, option_value, option_description, autoload) VALUES (‘template’, ”, ”, ‘yes’)
    WordPress database error: [Unknown column ‘autoload’ in ‘field list’]
    INSERT INTO wp_options (option_name, option_value, option_description, autoload) VALUES (‘stylesheet’, ”, ”, ‘yes’)

    The active theme is broken. Reverting to the default theme.

    I have no idea what this means.

    By the way, I found the instructions not completely clear. For example, it said “Run wp-admin/upgrade.php.” How does a newbie know what “run” means? In your FTP program? In your browser? Finally, I figured out to browse to that.

    So, any idea what I might have done wrong? I’m looking forward to being able to customize a theme.

    Thanks,
    Ellen

Viewing 11 replies - 1 through 11 (of 11 total)
  • I just updated a 1.2.1 version to 1.5.1.1. yesterday – it was painless. When it is about the upgrade forget the customizing. Just make it work with the 2 themes that come with the package. AFTER that there is plenty of time to do it (and good tutorials, too).

    Thread Starter ellenfinkl

    (@ellenfinkl)

    But you missed the point. Before I started any customizing, it made my blog page blank! I need the main thing to work before I can go on. I thought that maybe those messages would explain why I had a blank page.

    Probably the upgrade did not happen. Did you proceed as it is in the guide? It seems not, since you said “just renamed the folder” instead of deleting the old WP files from the server. Of course, after saving/downloading them to your computer (a.k.a. backup). Since you left it there both scripts try to access your DB, the old and new config file, for example.
    Always follow the tutorials…

    Moderator James Huff

    (@macmanx)

    The best guide for upgrading from WP v1.2.x to v1.5.x: https://www.tamba2.org.uk/wordpress/upgrade/

    The “official” guide for upgrading from WP v1.2.x to v1.5.x: https://codex.www.ads-software.com/Upgrade_1.2_to_1.5

    Thread Starter ellenfinkl

    (@ellenfinkl)

    Thread Starter ellenfinkl

    (@ellenfinkl)

    The update definitely did happen, because my menus were different. I followed the tutorial exactly, except for deleting my files. You misunderstood. I put my old files in a renamed folder and then did the upgrade exactly as described. But I’ll try that Tamba set of instructions, although it looks daunting.

    Like ellenfinkl my blog page was completely blank also when I upgraded. Unfortunately I’m not 100% sure that I upgraded from v1.2x or v.1.5x – cardinal sin of doing it when I was tired.
    I deleted all files apart from wp-config.php beforehand (but my ftp software may not have initially deleted the folders properly). I deleted and uploaded again and this time I was presented with the folders tree. I was able to login clicking on wp-login.php with normal password, and everything was fine in the control panel, everything there, version 1.5.1.1. I’ve now deleted everything again as it looked like a security risk. Any pointers would be appreciated.

    Moderator James Huff

    (@macmanx)

    If you deleted /wp-content/, then you deleted your active theme as well. That’s why your blog looked blank. What looked like a security risk to you?

    Many thanks for the quick reply and likely solution. All the folders and files were visible on arrival at the url – it seemed very open.

    Moderator James Huff

    (@macmanx)

    That means that you’re missing an index.php file in the WordPress root, or you have you .htaccess file or Apache configuration setup to ignore index.php as a possible index file.

    macmanx, your tip about the deleted /wp-content/ was the solution.
    All is now well at Slimming for the Beach. Many thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • The topic ‘upgrade didn’t work’ is closed to new replies.