WordPress.org

Ready to get started?Download WordPress

Forums

[closed] Warning: Invalid argument supplied for foreach() in /home/ft/public_html/wp-incl (17 posts)

  1. St.Dusty
    Member
    Posted 1 year ago #

    Hi,
    I just upgraded to 3.5.
    I get this error on my website which needs to be eradicated asap!

    Warning: Invalid argument supplied for foreach() in /home/ft/public_html/wp-includes/post.php on line 3588

    What could this issue be? Any assistance?

    Your help is very much appreciated,
    Dusty.

  2. St.Dusty
    Member
    Posted 1 year ago #

  3. dsonson23
    Member
    Posted 1 year ago #

    Same thing happened to my website

  4. capotea
    Member
    Posted 1 year ago #

    I have exact the same error

  5. capotea
    Member
    Posted 1 year ago #

    What could be the common thing on our websites?
    Something with jquery or a caching plugin or a security plugin?
    Any idea?

  6. capotea
    Member
    Posted 1 year ago #

    I'm sorry to say St.Dusty but your Forum section has a problem too.
    Mingle is only compatible up to WordPress 3.2.1

  7. eworldlinx
    Member
    Posted 1 year ago #

    similar error... upgraded from 3.4.2

  8. capotea
    Member
    Posted 1 year ago #

    I think it will be fixed in an update, see http://core.trac.wordpress.org/ticket/22883
    Hopefully patience is enough here ;-)

  9. esmi
    Forum Moderator
    Posted 1 year ago #

    @St.Dusty: Have you tried:

    - deactivating all plugins to see if this resolves the problem. If this works, re-activate the plugins one by one until you find the problematic plugin(s).

    - switching to the Twenty Eleven theme to rule out any theme-specific problems.

    - resetting the plugins folder by FTP or PhpMyAdmin. Sometimes, an apparently inactive plugin can still cause problems.

    - re-uploading all files & folders - except the wp-content folder - from a fresh download of WordPress. Make sure that you delete the old copies of files & folder before uploading the new ones.

    @Everyone else: As per the Forum Welcome, please post your own topic. Your problem - despite any similarity in symptoms - is likely to be completely different.

  10. St.Dusty
    Member
    Posted 1 year ago #

    Hi guys i've tried all those things to no avail.
    This is really not good.

  11. DaveyWavey
    Member
    Posted 1 year ago #

    I went through all my plugins and I found that activating WordPress Shortcodes and Sharebar caused WordPress to have the exact error cited by @St.Dusty - hope that helps!

  12. St.Dusty
    Member
    Posted 1 year ago #

    wordpress shortcodes fixed it!

  13. capotea
    Member
    Posted 1 year ago #

  14. ArtFl
    Member
    Posted 1 year ago #

    Hi all!

    I've faced a new problem after update.

    I've updated wp on my two sites (in different languages) with the same Genesis themes and plugins: one update on http://www.riseday.net went okay, other on ru.riseday.net produced the warning.

    I used every recommendation on this and parallel thread to fight it: disabled plugins, switched themes, and put the word "(array)" in the code as someone proposed.

    Finally, the warning disappeared but a worse problem arose.
    Now every post and page on my site shows only the homepage (the url remains the url of the post/page).
    The archives are shown okay.

    That shocked me because I didn't touch any wp files except for minor changes in post.php as proposed here http://core.trac.wordpress.org/ticket/22883

    After that I reinstalled not only this file but I also several times reinstalled wp in my dashboard updates section but nothing changes.

    I need your help. Please someone advise.

  15. markdj57
    Member
    Posted 1 year ago #

    I got my problem sorted.

    I downloaded wordpress 3.4, extracted it, deleted the existing wordpress folders apart from my content and then uploaded all of 3.4 to my wordpress install, overwriting all the 3.5 wordpress stuff.

    Basically, using the manual install instructions to downgrade to 3.4.2 again.

    https://plus.google.com/112927249389096933840/posts/aGwEGRzfghs

  16. ArtFl
    Member
    Posted 1 year ago #

    YES!!! Thank you very much markdj57 for your wise advice! Now the site rocks again on wp 3.4.2.
    Next time I'll think of update only when it becomes less risky.

  17. esmi
    Forum Moderator
    Posted 1 year ago #

    Do not downgrade to WordPress 3.4.2 unless you can first restore a pre-upgrade database backup. The database was changed for 3.5 and should not be used with 3.4.2 core files.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags