Problem with 2.7

  • Resolved barnyoka

    (@barnyoka)


    16 years, 3 months ago

    In a previous post, titled Another Problem with 2.7, I reported that my blog was not working after upgrade. Nearly 24 hours later, this problem is still not resolved.

    Suspecting outdated StuffIt Expander as the source of the problem, I downloaded the most recent version. Then, I downloaded StuffIt Cleaner. I used the latter to remove all StuffIt files. Everything, including the copies of WP I had downloaded earlier and all aborted attempts at opening it, went into the Trash, which I then emptied.

    I restarted the computer. I repaired disk permissions and restarted the computer again. I downloaded StuffIt Expander again, installed it, and it seems to be working just fine. I also downloaded the WP.zip file again. StuffIt continues to tell me there’s something wrong with the WP zip file. One of the suggested causes from the Support page for StuffIt indicates the cause might lie in the compression software used to zip the files.

    Now, something I did not notice yesterday, is the icon on the WP.zip file – a Gzip icon. I searched for Gzip, found the homepage and downloaded the software. It also will not open the WP.zip file, claiming that Classic is no longer available.

    Once again, I am working on a MacBook Pro with Mac OS X 10.5.4.

    What can I do to acquire a full copy of WordPress 2.7 that WILL open on command?

    Thanks in advance for any more guidance anyone can offer.

    Getting desperate – –

    Dena

Viewing 3 replies - 16 through 18 (of 18 total)
  • Thread Starter barnyoka

    (@barnyoka)

    The message I get with the Archive Utility is

    “Unable to unarchive “wordpress-2.7.zip into “Desktop’.
    (Error 1 – Operation not permitted.)”

    Then I tried downloading it in a way that would expand it as it came in and selected the Mac OS to expand it. That did not work either. Error message:

    “Download Error

    /Users/Home/Desktop/wordpress-2.7.tar.gz could not be opened, beacuse an unknown error occurred.

    Try saving to disk first and then opening the file.”

    That brings me back full circle.

    Again – could there be something malicious on my computer that is preventing me from updating my blog?

    Now – here’s something interesting!

    The attempted expansion on delivery resulted in two files –

    VYaDOqXG.gz.part
    VYaDOqXG.gz.1.part

    The first one opened just fine. It seems to have all the files I need, as I see wp-load.php among others I have not previously seen. I’m going to try uploading those files now and see what happens. I’ll get back to you soon.

    Anyway, what this tells us is that a) my Archive Utility works, b) there IS something wrong with the download file, and c) the error lies in VYaDOqXG.gz.1.part.

    Back soon . . .

    Thread Starter barnyoka

    (@barnyoka)

    OK – problem solved – I’m back in business!

    Interesting – I tried to open VYaDOqXG.gz.1.part with StuffIt. It seemed to be taking a very long time to open, so I stopped StuffIt. VYaDOqXG.gz.1.part disappeared from my desktop!

    I don’t know what all this means, other than that anyone using a Mac should download to open, not to save, and should have Mac OS do the opening.

    Many thanks to all of you who tried to help. This one has been a struggle, but I think it’s been worth it. The new interface looks positively brilliant, and I can’t wait to learn my way around it. Well done, everyone!!!

    Dena

    I am not sure if this will help anyone using a mac but it was very quick and easy for me when I did the following:

    In your web browser input https://www.yourdomainname.com/cpanel
    This will take you to your hosting account where you host your blog (you will need the username and password from them)

    In the cpanel/back office of your blog scroll down the page and click the icon which installed your blog initially (my host is HostGator.com and my icon is Fantastico DeLux)

    It is here where the option to upgrade to 2.7 was 30 seconds maximum and no glitches whatsoever.

    I sure do hope this helped.

Viewing 3 replies - 16 through 18 (of 18 total)
  • The topic ‘Problem with 2.7’ is closed to new replies.