Last modified: 2006-11-03 01:38:04 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7788 - Force edit summaries does not work when adding a new section
Force edit summaries does not work when adding a new section
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-11-02 11:58 UTC by Paolo Liberatore
Modified: 2006-11-03 01:38 UTC (History)
0 users

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Description Paolo Liberatore 2006-11-02 11:58:09 UTC
When creating a new section, the headline field works both as a new section
title and as an edit summary. As such, the user should be prompted when trying
to insert an empty headline, if "force edit summaries" is enabled. A way to fix
it is to add a "force new section headline" option to the user's preferences.
Comment 1 Andrew Garrett 2006-11-02 13:36:08 UTC
Fixed in r17364
Comment 2 Rob Church 2006-11-02 18:57:30 UTC
Use a different interface message to indicate that it's the heading that's
missing - in this mode, users can't enter a summary, so reusing the existing
message is misleading.

If this isn't done, then the bogus fix should be reverted. Please also see the
history of the feature in question; this isn't the first time this issue has
come up.
Comment 3 Andrew Garrett 2006-11-03 01:37:49 UTC
I've changed this in r17365 to have the behaviour described by Rob.

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