WordPress.org

Ready to get started?Download WordPress

Forums

FATAL ERROR after install wordpress 2.5, help! (14 posts)

  1. minimalnet
    Member
    Posted 6 years ago #

    Hi!, I am trying update to wordpress 2.5 now and when I go to upgrade, and in the blog in general, i read this error on the top:

    Warning: array_keys() [function.array-keys]: The first argument should be an array in /home/minimal/public_html/wp-includes/widgets.php on line 654
    
    Warning: Invalid argument supplied for foreach() in /home/minimal/public_html/wp-includes/widgets.php on line 654

    And when I access to a page i read:

    Warning: array_keys() [function.array-keys]: The first argument should be an array in /home/minimal/public_html/wp-includes/widgets.php on line 654
    
    Warning: Invalid argument supplied for foreach() in /home/minimal/public_html/wp-includes/widgets.php on line 654
    
    Warning: Cannot modify header information - headers already sent by (output started at /home/minimal/public_html/wp-includes/widgets.php:654) in /home/minimal/public_html/wp-includes/pluggable.php on line 689

    All that before clic upgrade, wiewing that i do not go to upgrade still. what can be the problem?

    Notes:
    I have all the plugins deactived.
    I still not upgrade wiewing that.
    I have the default theme selected befor upgrade.

  2. genevaeagles
    Member
    Posted 6 years ago #

    Think I had a same error message (check here).

  3. minimalnet
    Member
    Posted 6 years ago #

    But how you solved finally?, I do it 2 times with the same result.

  4. genevaeagles
    Member
    Posted 6 years ago #

    I really just started from my last running 2.3.3 back-up and did the whole update process again. I did it locally first tough to make sure it's working. Do you have a local install of your WP?

    2nd time I really just made the change in the config file (did you do that?...you need to add a line -> copy and paste)

    and then didn't even delete the files just override with copy and paste...going on with .../wp-admin/upgrade.php to get the DB changes done and voilĂ ...good to go!

  5. genevaeagles
    Member
    Posted 6 years ago #

    Oh..by the way...when I was doing it on my server...I didn't deactivate any plugins at all. Just run the Maintenance Mode plugin and uploaded my local files to the server.

  6. minimalnet
    Member
    Posted 6 years ago #

    No, I do it all that before but the problem is not solve for me. I go ty try aply the xml backup.

  7. genevaeagles
    Member
    Posted 6 years ago #

    Well...hopefully someone is going to be able to help you out here. Good luck!

  8. minimalnet
    Member
    Posted 6 years ago #

    I create a new database and I imported all the post to there, anyway I hope somebody can explain me why this error because I would like continue using my old database with normality.

  9. 87insight
    Member
    Posted 6 years ago #

    same problem here
    my poor blog is all messed up.

  10. minimalnet
    Member
    Posted 6 years ago #

    If more people have this problem and cannot solve it, I recommend use my option, new database and import the xml with the post information.

    The bad is the work, configurate the plugins again, and lost the registered users and the links, but... I did not have other option.

    Now with the new database and the post imported my blog is working in 2.5 of correctly way.

  11. 87insight
    Member
    Posted 6 years ago #

    Me too. Did exactly the same.

  12. kastam
    Member
    Posted 6 years ago #

    wow, i think for you all, it's possible any file is broken like : wp-includes/widgets.php

    So, Download new wp 2.5 again, extract and upload except wp content.
    make sure during upload, your system working properly, all file uploaded smootly and finish.

    Now you can see the result

  13. 87insight
    Member
    Posted 6 years ago #

    I downloaded several copies and uploaded several times.

    Now my blog is brand new with a new database

  14. urich
    Member
    Posted 6 years ago #

    I believe i have found a solution. it invovles deleting one line from the wp-config.php file. here's a link.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags