Open Bug 1067874 Opened 10 years ago Updated 3 years ago

Composer forgets FTP "publish" settings

Categories

(SeaMonkey :: Composer, defect)

SeaMonkey 2.29 Branch
x86_64
Linux
defect
Not set
normal

Tracking

(Not tracked)

UNCONFIRMED

People

(Reporter: rabbe, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:32.0) Gecko/20100101 Firefox/32.0 SeaMonkey/2.29
Build ID: 20140904220144

Steps to reproduce:

Browse to a webpage.
Do File->EditPage; a composer window appears.
Edit the page (does not matter how).
Do File->PublishAs; the "Publish Page" dialog appears.
In the dialog, click the "Publish" tab.
Use the "New Site" button to configure an FTP server, OR use the drop-down list to pick a previously configured FTP server.
Fill in remaining dialog items as appropriate.
Click "Publish". Successful publishing by FTP takes place. The "Publish" button on the composer toolbar goes grey.

Now perform another minor edit of the page content. The "Publish" button is un-greyed.

Click the "Publish" button.


Actual results:

Publishing fails, because publish by HTTP was attempted instead of publishing by FTP.
In order to get successful publishing one has to redo the "Publish As" routine.


Expected results:

Publish by FTP takes place again, and the "Publish" button is greyed.
This was the behaviour in 2.26 if I remember correctly. IMHO that is the way it should be: The composer window "remembers" the FTP publishing configuration for the rest of the editing session.
This wound has healed it seems! Right now I am running Seamonkey built from source on a Gentoo amd64 system "unstable" (that is ACCEPT_KEYWORDS="~amd64" is set). The version reported in Help->AboutSeamonkey is 2.42.

When I do "Publish As" in an editing session I have to specify that an FTP server should be targeted, and the directory on that server. Later on I can just push "Publish" and another FTP upload takes place to the exact same place. Just as it should be IMO.

FTP support has been removed (bug 1574475). Consider closing this bug.

You need to log in before you can comment on or make changes to this bug.