Jump to content


FTP Upload does not use Folder path settings correctly


3 replies to this topic

#1 Wessel

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 27 November 2011 - 11:52 PM

Hi,

In the Wizard -> FTP Settings
Using Select directory Displays my directory structure correctly and i can browse throiugh all the folders, and I can select my instalation directory.

In the log it displays the usages of the CWD and the selected path correctly.
CWD /var/www/vhosts/www.foo.bar.eu/HTML/LiveZilla

CURRENT BEHAVIOR
Now when I try to upload or update the instalations since the 3.2 version it has a bug:
The Client incorrectly first tries to acces the / folder Which will not be accesable on systems that are on secure rules.

CWD /
550 /: No such file or directory
/: No such file or directory (550).

EXPECTED BEHAVIOR
The Update/Install Wizard uses the path given inside the Folder: settings as it was selected or given by the user.
Old versions of LiveZilla did this correctly, the newer versions have this bug that first CWD's to / instead of the path given by the user.

PROPOSED FIX
Remove the code that initiates with a CWD / and replace it with an immediate CWD /foo/bar/folder/user/has/set
As it is in the RFC directly use of directories is allowed and recommended.

Hope you can fix soon as it blocks updating on several shared hosting

Wessel

#2 Derek Punzova

    Support Team Member

  • Moderators
  • 6057 posts

Posted 28 November 2011 - 07:15 AM

Thanks for reporting.

POSSIBLE WORKAROUND
Upload the files manually instead of using the in-build FTP upload.
- If you like to suggest a new feature, please click here.
Kind Regards,
Derek

#3 Wessel

    Newbie

  • Members
  • Pip
  • 9 posts

Posted 30 November 2011 - 09:20 AM

Thanks,
That's where I ended up with doing to get it installed.

When is this fix scheduled ?

Wessel

#4 Derek Punzova

    Support Team Member

  • Moderators
  • 6057 posts

Posted 30 November 2011 - 10:26 AM

Quote

When is this fix scheduled ?
This issue has not been confirmed yet, we will investigate in the next week. It's not prioritized as we don't have any other reports for this problem.

The next update will be 4.1.x.x. I don't have a release date yet but I expect it to be released in january.

Hope this helps.
- If you like to suggest a new feature, please click here.
Kind Regards,
Derek





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users