266811 - After publishing, composer forgets the "site name" to which page was published

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Nelson Bolyard (seldom reads bugmail)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8a4) Gecko/20040927

I have several web sites to which I publish pages.  They have separate 
logins, passwords, etc.  

After composing a page, I save it, and then publish it.  Then, I often
choose to make additional edits to the page, and then save it again,
and then publish it again.  

The first time I publish the page, when the "publish page" dialog appears, 
I must select the proper site name from the list.  That's as expected.

The problem is that after I have published the page, composer forgets 
the site name to which I just published the page.  So, after publishing
the page, and then editing it some more, and saving it, Composer has once
again reverted to the first "site name" in the list.  

Composer remembers the previous settings of some of the properties of the
"Publish Page" dialog from one use to the next.  For example, it remembers
whether I have checked the "Include images and other files" box, and the 
radio button that says "Use the same location as page" or "use this site
subdirectory".  But it doesn't remember the site name from one publish to
the next, in the same composer window, in the same session of composer.

On several occasions, I have had the unfortunate experience of publishing
the site's home page to the wrong site, putting "index.html" on the wrong
site.  Whatta PAIN.  

Reproducible: Always
Steps to Reproduce:
1. Compose page,
2, save it.
3. publish it
4. edit it some more in the same composer window as step 1 above,
5. press Save again
6. Publish again
Actual Results:  
"Publish Page" dialog comes up with the first "site name" selected.

Expected Results:  
"Publish Page" dialog should come up with the same "site name" selected
that I used just seconds before when I previously published this page from
this same composer window.

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

1.8 is trunk, right?  I wish bugzilla was smarter about choosing the bug
"version" based on the submittor's user agent string.

Comment 2

[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 3

[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