Closed Bug 233524 Opened 21 years ago Closed 20 years ago

Publishing settings dialog should not preselect a publishing site

Categories

(SeaMonkey :: Composer, defect)

defect
Not set
minor

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: glazou, Assigned: glazou)

Details

Attachments

(1 file)

I have received A LOT of feedback about the Publishing Settings dialog. When it
is opened, it preselects the default publishing site and people have to click
on "new site" to create one. That's confusing enough so many people modified
by mistake their default publishing site instead of creating a new one.
It is proposed to change the current behavior and stop preselecting the default
site.
Comment on attachment 140961 [details] [diff] [review]
fix #1

brade/dbaron, could you r/sr please ?
Attachment #140961 - Flags: superreview?(dbaron)
Attachment #140961 - Flags: review?(brade)
One concern I would have is that someone is trying to publish but they don't
quite get the settings right.  If they come back to the dialog, wouldn't it be
better if their settings were already there?  (I'm coming from the perspective
that many users will only publish to one location.)

I would prefer to reorganize the dialog so that the "New Site" button is more
prominent or use other techniques to avoid the problem where people are changing
their default setting when they want a new setting.  One option would be to ask
the user if they really want to replace the settings if they change the host (or
some similar check).

Before we proceed with any patch, I'd like to know the rationale for whatever we
agree to.  :-)
Comment on attachment 140961 [details] [diff] [review]
fix #1

sr=dbaron assuming you get peer review
Attachment #140961 - Flags: superreview?(dbaron) → superreview+
brade: you propose to revamp the dialog, that's another bug. I am just dealing
here with the fact some people forget ftp:// because nobody told them about it,
and publishing does not work...
Comment on attachment 140961 [details] [diff] [review]
fix #1

Looks safe enough to me.
Attachment #140961 - Flags: review?(brade) → review+
Comment on attachment 140961 [details] [diff] [review]
fix #1

Requesting approval for 1.7 checkin: this bug is a long-standing problem, with
user feedback, the fix for the bug is trivial and harmless, and it is already
implemented and used in Nvu 0.20.
Attachment #140961 - Flags: approval1.7?
Comment on attachment 140961 [details] [diff] [review]
fix #1

a=chofmann for 1.7
Attachment #140961 - Flags: approval1.7? → approval1.7+
checked in (trunk)
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: