Results 1 to 5 of 5

Thread: Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

  1. #1
    siros is offline Sugar Community Member
    Join Date
    Jan 2006
    Posts
    20

    Default Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

    Hi,

    I am trying to upgrade Sugar from 4.01e to 4.2 on a shared server- which means I don't have the option of becoming root nor to easily change all files into chmod 0777. Up to now all upgrades ran very smoothly, but with this upgrade I get the following error:

    Could not copy file $sugar/cache/upload/upgrades/temp/W0oRul/./SugarSuite-Patch-4.2.0/themes/RipCurl/layout_utils.php to $sugar/./SugarSuite-Patch-4.2.0/themes/RipCurl/layout_utils.php
    I had similar problems with the White (?) theme before. Sometimes manually deleting a file like header.php in that new themes directory helped but then the next file reports the same error. The strange thing is that these errors are caused by files that have just been created by the upgrade script itself (nothing there before and nothing changed to permissions)

    The host reports the following OS etc:
    Linux 2.4.21-37.ELsmp
    Sugar Suite 4.01e => 4.2 upgrade patch
    Webserver 1.3.34 (Unix)
    PHP 4.4.1
    MySQL 4.0.25-standard

    Anybody have an idea which does NOT involve manually changing the permissions of every single file created by the installation script one by one?

    Thanks
    Siros

  2. #2
    joomlales is offline Sugar Community Member
    Join Date
    Apr 2006
    Posts
    45

    Thumbs down Re: Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

    Quote Originally Posted by siros
    Hi,

    I am trying to upgrade Sugar from 4.01e to 4.2 on a shared server- which means I don't have the option of becoming root nor to easily change all files into chmod 0777. Up to now all upgrades ran very smoothly, but with this upgrade I get the following error:



    I had similar problems with the White (?) theme before. Sometimes manually deleting a file like header.php in that new themes directory helped but then the next file reports the same error. The strange thing is that these errors are caused by files that have just been created by the upgrade script itself (nothing there before and nothing changed to permissions)

    The host reports the following OS etc:
    Linux 2.4.21-37.ELsmp
    Sugar Suite 4.01e => 4.2 upgrade patch
    Webserver 1.3.34 (Unix)
    PHP 4.4.1
    MySQL 4.0.25-standard

    Anybody have an idea which does NOT involve manually changing the permissions of every single file created by the installation script one by one?

    Thanks
    Siros

    I get exactly the same problem. And as yourself, CHMODIng a zillion files manually does not make sense. There must be a better way!


  3. #3
    jscherber is offline Sugar Community Member
    Join Date
    Oct 2004
    Posts
    77

    Default Re: Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

    Hi Guys,

    What type of FTP client are you using? It actually isn't as difficult a process as you make it out.


    1. Backup your Sugar Directory and MySQL files (IMPORTANT! DON"T SKIP)

    2.CHMOD 777 all the files in your root directory,

    3. CHMOD 777 each directory under your Sugar Directory.

    The FTP client I use (WSFTP) will prompt you whether you want to include all subdirectories and files as well. Check yes.

    4. Once all the files are 777 execute the upgrade process

    5. After the upgrade leave cache, data and custom directories at 777, and config.php at 777, everything else 755.

    Entire process should take less than 15 minutes.

    Hope this helps.

  4. #4
    joomlales is offline Sugar Community Member
    Join Date
    Apr 2006
    Posts
    45

    Default Re: Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

    Quote Originally Posted by jscherber
    Hi Guys,

    What type of FTP client are you using? It actually isn't as difficult a process as you make it out.


    1. Backup your Sugar Directory and MySQL files (IMPORTANT! DON"T SKIP)

    2.CHMOD 777 all the files in your root directory,

    3. CHMOD 777 each directory under your Sugar Directory.

    The FTP client I use (WSFTP) will prompt you whether you want to include all subdirectories and files as well. Check yes.

    4. Once all the files are 777 execute the upgrade process

    5. After the upgrade leave cache, data and custom directories at 777, and config.php at 777, everything else 755.

    Entire process should take less than 15 minutes.

    Hope this helps.
    Hey there 'jsherber" - Yes it is a simple process. Unfortunately nobody bothers to tell you this when you download the patches. I have looked high and low --- and knew that that something had to be CHMODED - but was wary of doing a mass change. A small suggestion to the SugarCRM Team - Build comprehensive readmes in the downloads so people will know what to do, not waste time, and keep this Forum a little less busy.

    I use FTP Commander - which does not allow for recursive changes. I'll download WSTP and give it a go.

    Thanks for the great advice and for taking the time to give it!




  5. #5
    siros is offline Sugar Community Member
    Join Date
    Jan 2006
    Posts
    20

    Default Re: Upgrade to 4.2: multiple 'Could not copy file' bugs on shared server

    Quote Originally Posted by joomlales
    I use FTP Commander - which does not allow for recursive changes. I'll download WSTP and give it a go.

    My FTP clients (Transmit and Fetch on the Mac) don't allow recursive CHMODs either. If you don't have that functionality in an FTP client, the process is basically blocked... Any tip on which FTP client for the Mac or Unix does support recursive CHMOD?

    Siros

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •