136970 - adding filename with Publish URL should not do bad things

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[sujay]

using 4/11 build

some users are adding the filename at the end of the Publish
URL even though they have declared it in the other tab.

This is causing some problems in poublishing files.

Am working on a reducted test case..filing this bug as a placeholder
because there is definitely something going wrong here doing this.

Comment 1

[Charles Manske]

The only thing I can think of doing is adding some text to dialog or in a tooltip
to tell user not to include filename.
We should still force them to enter the filename in the "Filename" input field in
 the "Publish panel". We could then strip that off of publish url if it is a 
duplicate.

Comment 2

[TucsonTester1]

1.Install/Launch NS 6.2.1+
2.Launch new/blank Composer window.
3.Add some content to the page.
4.Click file|publish as...
5.Enter info to publish to valid ftp site (include filename at end of publishing
URL).
6.Click publish.

Error message (Alert) states that there is no directory. 
This is what I would expect to happen.  If the publishing URL is incorrect, the
page won't publish.
There are no crashes and page will properly publish if URL is corrected.  
I agree with cmanske, guide user to enter correct info or "strip" duplicate
filename.

Comment 3

[Charles Manske]

We currently do say "...(don't include filename)" in the tooltip for the 
"Publishing address"
Should we try to do anything else?

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420