WordPress.org

Ready to get started?Download WordPress

Forums

plugin-install.php unserialize error (5 posts)

  1. testcricket
    Member
    Posted 5 years ago #

    I've just updated several sites on the same server to Worpress 2.7

    I have used the new plugin browser to install a couple of plugins with no problem, until yesterday.

    Now suddenly all sites are experiencing the same error when trying to browse the "new", "updated" "popular" etc categories in the plugin browser.

    The error message is:
    ------------------
    Warning: unserialize() expects parameter 1 to be string, object given in /home/xxxx/public_html/wp-admin/includes/plugin-install.php on line 45

    An unknown error occured
    ------------------

    I've tried checking line 45 and I guess I'm not techy enough to work out what the problem is.

    Using my test site, I attempted to change a couple of things in line 41 where there were 4 brackets after the word "arg" - the last one with a space before it and a ; following. I removed the space but got the same error message. I removed the space and bracket and got a different warning that there was an "unexpected ; in line 41" which was clear enough. So that didn't help at all. Anyway, I was doing all that as an experiment having almost zero understanding of php. I've replaced the original php file for now and still getting the error message.

    I've searched extensively for any discussion of this and found nothing at all except references to the "unserialise bug" in Tarski and some similar errors in plugins that gave no explanation of the problem. My apologies if I've missed something.

    As I said, I'm not a techy, I'm a designer and this warning is worrying me as I've upgraded clients sites and I don't know where it's coming from.

    Any help would be appreciated.

  2. testcricket
    Member
    Posted 5 years ago #

    Hmmmmm. This is kind of urgent and I'm trying to be patient here but I do need help asap. I don't want to harass the forum though - so is there somewhere else I should post this problem?? Maybe somewhere that is set up for urgent help on these sorts of issues on new releases of WordPress specifically??? (especially when it's Christmas and probably most people are sensibly off having fun somewhere)

    Can anyone at least tell me if this is a bug or error related ONLY to using the plugin browser to upload plugins (and therefore nothing to worry about - I just lose that functionality) OR is it a more serious problem in the code or in my database that could cause other issues in other areas of my sites. In other words - does it indicate an isolated problem in just that one thing script - in which case maybe I can remove it - OR does it mean the entire site is broken OR at risk?

    I REALLY don't want to put my clients sites at risk and if it's serious I will need to revert all my sites back to the older version of WP using the older versions database backups. WHich will not make them or me very happy but at least there sites will end up secure.

    Anyway - thanks to anyone taking the time to read this. If you can give me anything - ANYTHING at all - to help me out that would be a bonus.

    Cheers

  3. ejabs
    Member
    Posted 5 years ago #

    I'm having the same problem.

    When I search for a plugin, it works fine and the plugins come up. However, if the search results return more than 2 pages, I always get this error on the 2nd to last search results page only:

    Warning: unserialize() expects parameter 1 to be string, object given in /path_to_my_blog/wp-admin/includes/plugin-install.php on line 45

    An unknown error occured

    Here is what line 45 of '/wp-admin/includes/plugin-install.php' contains:

    $res = unserialize($request['body']);

    Not sure what the problem is or what to do to fix it.

    Thanks,

    Matt

  4. ejabs
    Member
    Posted 5 years ago #

    Apparently it is a problem quite a few others are experiencing as well.

    See this thread.

    Matt

  5. testcricket
    Member
    Posted 5 years ago #

    hmmmmm. Okay. This is where I realise how limited my understanding of coding is LOL I remember staring at that line 45 for what seemed like hours, reading the error message, staring at line, reading message, scratching head, staring, reading, staring, scratching.... - you get the picture.... until I finally had to admit it meant nothing at all to me and staring at it with wrinkled brow and serious intent wouldn't change that LMAO

    Oh well, it seems to fix itself if you ignore it and keep trying so hopefully it will get resolved in a later update. Its good to know it's more annoying that harmful.

    Thanks for that Matt.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.