Opened 12 years ago

Closed 12 years ago

Last modified 7 years ago

#4182 closed Bug report (fixed)

Default Remote Directory not working in v3.2.0 for MVS server type

Reported by: Steve Mann Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: XP SP3

Description

The Default Remote Directory for a MVS server type worked in v3.1.6 but not in v3.2.0. In v3.1.6 a directory of the form 'test' was accepted and was used correctly. In v3.2.0, the same value returns message "Default remote path cannot be parsed. Make sure it is valid and is supported by the slected server type.". v3.2.0 will accept values of the form /'test' or \'test' but neither value is used or saved.

Attachments (2)

attachment1.png (1.2 KB ) - added by wesleydevrient 12 years ago.
attachment2.png (7.0 KB ) - added by wesleydevrient 12 years ago.

Download all attachments as: .zip

Change History (8)

by wesleydevrient, 12 years ago

Attachment: attachment1.png added

by wesleydevrient, 12 years ago

Attachment: attachment2.png added

comment:1 by wesleydevrient, 12 years ago

I also came across this problem while connect to a MVS server. You can browse a folder by typing '\u' in the Remote site box after connecting (see attachment1.png). But if I want to set that as the Default remote directory I get the following error:
"Default remote path cannot be parsed. Make sure it is valid and is supported by the slected server type." (see attachment2.png)
I am also using FileZilla v3.2.0

comment:2 by Tim Kosse, 12 years ago

Status: newmoreinfo

Since when are slashes part of the MVS path syntax?

It's afaik all uppercase ASCII separated by dots and at the end maybe parenthesis for PDS members. All enclosed on single quotes.

'FOO.'
'FOO.BAR.'
'FOO.BAR(SOMETHING)'

comment:3 by Steve Mann, 12 years ago

The Default Remote Directory for a MVS server type is still not working as of the nightly build for 02/18/2009.

comment:4 by Tim Kosse, 12 years ago

See my previous reply.

comment:5 by Steve Mann, 12 years ago

After a connection is made, the Remote Site path field will accept entries of the form

'FOO.'
'FOO.BAR.'
'FOO.BAR(SOMETHING)'

But these are not accepted in the Default Remote Directory field in Site Manager under the Advanced tab.

comment:6 by Tim Kosse, 12 years ago

Resolution: fixed
Status: moreinfoclosed

Ah, that is what you mean. The replies to this ticket made by wesleydevrient were more than confusing.

Will be fixed in 3.2.2

Note: See TracTickets for help on using tickets.