Update using ZIP of "update" folder instead sending files with FTP?

Discussion in 'General discussions' started by Benjamin A, Oct 10, 2019.

  1. Benjamin A

    Benjamin A New Member

    Joined:
    Jul 4, 2019
    Messages:
    28
    Likes Received:
    1
    S.E:
    2020-01-02 08:12:45
    L.T:
    Regular
    L.C:
    1
    Hello guys,

    I find the update procedure (uploading the content of the "update" folder with an FTP client) to be less than optimal to say the least... especially since this weird "overwriting(don’t replace, but overwrite)" is FTP client-dependent...

    Why not instead just upload a zip file of the update folder, and then run some command line to extract the content of this folder and do the same "overwriting" that the FTP client does (if properly configured lol)?

    maybe through some "mv" or "cp" command?

    Anyone has found the proper command lines to run?

    Thanks a lot,

    Cheers,
     
  2. Benjamin A

    Benjamin A New Member

    Joined:
    Jul 4, 2019
    Messages:
    28
    Likes Received:
    1
    S.E:
    2020-01-02 08:12:45
    L.T:
    Regular
    L.C:
    1
    lmao, 25K files to send through FTP in the latest update, this does NOT make any sense...

    We need proper instruction on how to do this by just uploading 1 zip file and then extracting it and moving or cp'ing the content.
     
  3. twisted1919

    twisted1919 Administrator Staff Member

    Joined:
    Dec 27, 2014
    Messages:
    10,477
    Likes Received:
    2,440
    You can enable auto-update from backend > settings > common.
    Other than this, the update procedure is standard for web based apps, upload files, overwrite existing ones, etc.
     
  4. piusodiahi

    piusodiahi New Member

    Joined:
    Oct 9, 2017
    Messages:
    21
    Likes Received:
    10
    S.E:
    Expired
    L.T:
    Regular
    L.C:
    1
    Hello twisted1919,

    Noticed that the Common link under Settings just show a white page with text :"Common settings". What could be the props here.

    Regards,

    Pius
     
  5. twisted1919

    twisted1919 Administrator Staff Member

    Joined:
    Dec 27, 2014
    Messages:
    10,477
    Likes Received:
    2,440
  6. piusodiahi

    piusodiahi New Member

    Joined:
    Oct 9, 2017
    Messages:
    21
    Likes Received:
    10
    S.E:
    Expired
    L.T:
    Regular
    L.C:
    1
    Follow the advice above and this was the result

    Error 500!


    require(/home/home_folder/application_directory/apps/common/vendors/SwiftMailer-5x/lib/mime_types.php): failed to open stream: Permission denied

    scrolled down and got this error section with
    require(/home/home_folder/application_directory/apps/common/vendors/SwiftMailer-5x/lib/mime_types.php):
    failed to open stream: Permission denied
    (/home/home_folder/application_directory/apps/common/vendors/SwiftMailer-5x/lib/dependency_maps/mime_deps.php:3)
    Stack trace:
    #0 /home/home_folder/application_directory/apps/common/framework/YiiBase.php(328):
    require()
    #1
    /home/home_folder/application_directory/apps/common/components/mailer/MailerSwiftMailer.php(38):
    import()
    #2
    /home/home_folder/application_directory/apps/common/components/mailer/Mailer.php(198):
    MailerSwiftMailer->init()
    #3
    /home/home_folder/application_directory/apps/common/components/mailer/Mailer.php(162):
    Mailer->instance()
    #4
    .............

    /home/home_folder/application_directory/apps/common/vendors/SwiftMailer-5x/lib/swift_init.php
    (23)
     
  7. twisted1919

    twisted1919 Administrator Staff Member

    Joined:
    Dec 27, 2014
    Messages:
    10,477
    Likes Received:
    2,440
    This seems like a user/group permission issue for the files, basically your web server runs under a user and tries to access files which apparently are owned by another user, this generally happens when you upload files as root for example in a user account and that user account does not have enough permissions to access those files.
    So my advice is to see under which the user and group run (most likely the home folder name is the name of the user and group) and change the permissions accordingly:
    Code:
    chown -R home_folder:home_folder /home/home_folder/
    
     

Share This Page