WordPress.org

Ready to get started?Download WordPress

Forums

[resolved] Error on upgrading to 3.5 (8 posts)

  1. fredriley
    Blocked
    Posted 1 year ago #

    This has to be a FAQ, as a search for this error gets quite a few threads for older versions of WP. Trying to upgrade WP 3.4.x on two different hosts, as advised by WP itself, I get the error:

    The package could not be installed.: PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature

    This was reported as a bug for 2.8 but that was ages ago. Is this a common error for 3.5? How can it be resolved? No, I really, really do not want to manually upgrade by laborious page editing and ftp-ing 00s of files. Life just isn't long enough...

    Fred

  2. Samuel Wood (Otto)
    Tech Ninja
    Posted 1 year ago #

    If your hosting systems cannot download the ZIP file properly, then there is no other option than manually upgrading.

    But it's not that bad. A manual upgrade only takes about 5 minutes. Download the file, unzip it, upload the files to the host. Not that big a deal.

  3. fredriley
    Blocked
    Posted 1 year ago #

    The hosting accounts were fine for previous upgrades. This is a large hosting company (Titan Internet) with zillions of accounts. The accounts support FTP ok, can download zips ok (see previous WP upgrades), and are generally the bee's knees. This is a WP bug, no question. I just need to know how to fix it without going through a full manual upgrade, which would involve downloading to local disk, unzipping, editing config files (else existing files would be overwritten and all my config would go walkies), then uploading 00s of files via ADSL.

    More importantly, manual updating is not a sustainable option for my main site as the clients are naive users who wouldn't know FTP from TCP.

    Fred

  4. Samuel Wood (Otto)
    Tech Ninja
    Posted 1 year ago #

    This is a WP bug, no question.

    Except that it's not. A bad download of the ZIP file is an issue on the host. Our ZIP files are fine (I checked). We can't ensure that the host downloads them correctly.

    editing config files (else existing files would be overwritten and all my config would go walkies)

    WordPress's files don't contain the wp-config.php file, so doing a manual upgrade won't overwrite it. There's no config files to edit in a manual upgrade process.

  5. fredriley
    Blocked
    Posted 1 year ago #

    Funny, then, how previous upgrades worked fine on the same host, all the plugin updates worked fine (I've just done a few now), and that a search for PCLZIP_ERR_BAD_FORMAT in the forum brings up many threads which indicate that, for previous versions, this was a WP bug. Some hint that it might be a quota problem, but AFAIK there's plenty of quota on both the accounts I'm hosting WordPress on, and it would be a coincidence for both of them to give the same error at the same time. Plus the zipfile is only 5Mb and unzipped around 12Mb so that's hardly disk-busting.

    However, as you insist that it's not a WP problem but a host problem, I'll just have to experiment on other hosts. I've tried upgrading a localhost WP install but it just stalls on unpacking, but then I'm using a crappy Windoze machine with XAMPP. I'll install an old version of WP on a different host then try to upgrade and see what happens. A few hours later and I might be able to report back. Or not, if I get fed up.

    Manual upgrades are asking for trouble - overwitings, deletions, permissions problems, transfer outages when uploading 00s of files via ADSL, etc - and are definitely not sustainable on a client site where the client should just be able to click 'upgrade' and it does it.

    Sorry to implicitly impugn your packing skills. No such insult was intended.

  6. Samuel Wood (Otto)
    Tech Ninja
    Posted 1 year ago #

    brings up many threads which indicate that, for previous versions, this was a WP bug

    It is not now, and has never been, a "bug" in WordPress. The error has been misleading and confusing in the past, and the message can be caused by many possible circumstances, but it's not a "bug".

    PCLZIP_ERR_BAD_FORMAT is a generic error that means, basically, the ZIP file that was downloaded is somehow broken. Many things can cause this. If WordPress.org was just down at the time, for example, then the download will timeout and the resulting file will be zero bytes long. Obviously, this is not a valid file and you get that error. Anything that causes the download to fail and an invalid file to be downloaded will cause it, basically.

    So the question isn't whether it's a bug in the WordPress software or not, because it is definitely not. The question is why is your download of the ZIP file failing. I have no idea, frankly. Perhaps the host is unable to talk to WordPress.org properly. Maybe a guy in Idaho dug up the wrong fiber optic line. Who knows?

    There have been times when WordPress.org was down, or times when it was heavily overloaded, and yes, at those times you might see this error. Currently, the site doesn't appear to be undergoing any extreme load, so I'd rule that out for now.

    The error is a generic one, essentially, and doesn't lend towards explaining what the problem is, other than the website can't download the ZIP file properly.

  7. Samuel Wood (Otto)
    Tech Ninja
    Posted 1 year ago #

    I've tried upgrading a localhost WP install but it just stalls on unpacking, but then I'm using a crappy Windoze machine with XAMPP.

    The upgrade works fine on XAMPP, but if the machine is particularly slow, then I'd suggest editing your PHP.INI file to increase the process timeout limit beyond the default of 30 seconds. That usually fixes it.

  8. fredriley
    Blocked
    Posted 1 year ago #

    Ok, thanks, that seems clear enough. I've bugged the hosting company with a support call to see if they've had any problems along those lines of late. The localhost upgrade did eventually work, after a couple more tries, so that could indicate a transfer problem, maybe low bandwidth or timing out. As long as this is just a temporary, rather than a chronic, problem then I'll not worry about it.

    Maybe it is rats nibbling on the cables after all...

Topic Closed

This topic has been closed to new replies.

About this Topic