Wordpress error HELP.

Discussion in 'Blogging' started by nirose, Jun 18, 2010.

  1. nirose

    nirose Senior Member

    Joined:
    Oct 24, 2008
    Messages:
    1,057
    Likes Received:
    450
    Location:
    theyre.onto.us
    i recently upgraded to WP 3 and this problem appeared.

    I'm now getting this error on my post pages.
    Code:
    Warning: Parameter 1 to pstl_the_content() expected to be a reference, value given in /wp-includes/plugin.php  on line 166
    Anyone know how to fix this

    I'm using wp-clear theme and common wp plugins like tweetmeme, AIO SEO pack, Super Cache, etc.

    HELP
     
  2. imperial109

    imperial109 Regular Member

    Joined:
    Jan 19, 2009
    Messages:
    499
    Likes Received:
    362
    That's why I'm waiting a few days before upgrading mine :p

    However it's your one or more of your plugins. Here's what you do. Deactivate each plugin one by one. Once you find the one that isn't working look for a replacement. Keep the broken one in your plugins list so you know if there's going to be an update for it.

    I know a bit of PHP but not enough to completely understand WP. I'd say that there was a default parameter that WP use to have and with this new update is more strict on value definitions. It's most likely due to an expansion of a parameter having more applicable values.
     
  3. nirose

    nirose Senior Member

    Joined:
    Oct 24, 2008
    Messages:
    1,057
    Likes Received:
    450
    Location:
    theyre.onto.us
    I know i should have waited. I always do but this time i didn't and it got me. I'm checking with the plugins hope to get it working again. but help appreciated.

    EDIT:
    Got it working
     
    Last edited: Jun 18, 2010
  4. topsytips

    topsytips Regular Member

    Joined:
    Aug 11, 2008
    Messages:
    334
    Likes Received:
    234
    Occupation:
    Self Employed
    Location:
    UK
    I've upgraded with (almost) no probs.

    Deactivate all of your plugins then re-activate them one by one to see which (if any) is causing problems. This upgrade will break some plugins and you may have to wait a while for those to be upgraded.
     
  5. bradk

    bradk Newbie

    Joined:
    Aug 15, 2010
    Messages:
    1
    Likes Received:
    0
    hi, i signed up because I ran into sort-of the same issue and ended up getting it resolved so figured I'd share what I found.

    it might be WP 3.0, since I haven't upgraded to it yet, but i started getting that same error after I rebuilt Apache on my server. after doing some debugging, I determined it was the post layout plug-in which I couldn't live without so I did more digging and eventually found out it was related to the fact that when I updated Apache, I went with PHP 5.3.x and there is an apparent incompatibility between that plug-in and PHP 5.3.x

    I notified the author who told me he submitted an updated version today, so hopefully that will be available soon, but in the meantime, I just downgraded PHP to 5.2.14 and all is right with the world.