4.6 File Uploader

[oryk]

Kirk,

I fill out <destination path>. Then I close the window or send file(s). If I reopen the window the field <destination path> is empty. This not happens in PM 4.5.4 .


-Oryk

[Kirk Baker]

Oryk,

I fill out <destination path>. Then I close the window or send file(s). If I reopen the window the field <destination path> is empty. This not happens in PM 4.5.4 .

With which template?

-Kirk

[oryk]

Oryk,

I fill out <destination path>. Then I close the window or send file(s). If I reopen the window the field <destination path> is empty. This not happens in PM 4.5.4 .

With which template?

-Kirk

<Selected uploader>: FTP

-Oryk

[oryk]

Kirk,

now I use PM 4.6 (not beta). Nothing changed. Is that issue on purpose ?

[Kirk Baker]

Oryk,

now I use PM 4.6 (not beta). Nothing changed. Is that issue on purpose ?

The engineer responsible for the Uploaders stated that this is by design.  The connection setting's destination path takes precedence.

-Kirk

[oryk]

Oryk,

now I use PM 4.6 (not beta). Nothing changed. Is that issue on purpose ?

The engineer responsible for the Uploaders stated that this is by design.  The connection setting's destination path takes precedence.

-Kirk

Kirk,

that's ok. But I do have to fill out the optional <destination path> in <File Uploader> template again and aigain.

[Kevin M. Cox]

Oryk, I think the solution would be to use "Edit Connections" button at the bottom of the window and add your "Destination Path:" information into the blank labeled "Destination Folder on Server."  This way it will always be filled out when you open the File Uploader.

[oryk]

Oryk, I think the solution would be to use "Edit Connections" button at the bottom of the window and add your "Destination Path:" information into the blank labeled "Destination Folder on Server."  This way it will always be filled out when you open the File Uploader.

Kirk, Kevin,

that's not practicable. The folder's name will change for several clients and will change for every event and. PM 4.5. was perfect.

[Kevin M. Cox]

Couldn't you just edit the connection before every event? This will still keep you from having to retype it while in the middle of editing and transmitting I would think.

[oryk]

Kevin,

I don't want to change to many things before every event. I want to simplify my workflow.

[Kirk Baker]

Oryk,

I don't want to change to many things before every event. I want to simplify my workflow.

I think you've made your point quite clear.  We'll see what we can do to return the old functionality back again.

-Kirk