Last modified: 2013-01-01 19:38:58 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T10065, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 8065 - New page automatic summaries override prompt for blank summary
New page automatic summaries override prompt for blank summary
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page editing (Other open bugs)
unspecified
All All
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-11-28 13:34 UTC by Danny B.
Modified: 2013-01-01 19:38 UTC (History)
2 users (show)

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


Attachments

Description Danny B. 2006-11-28 13:34:14 UTC
Tested on new page summary, new redirect summary and blanking page summary. I
was unable to trigger the "content rewritten with" summary, so I guess this one
does not override the blank summary prompt.

I'd suggest either forcing of prompt in every occasion or another checkbox
"Prompt for blank summary even when automatic summary available" in
Special:Preferences.

Thanks
Comment 1 Rotem Liss 2006-11-28 13:39:03 UTC
New pages and redirects (new and existing) don't require a manual summary, by
purpose. However, a blanking summary and replacing summary (which is created by
removing more than 90% from a page; the new page should be below 500 characters)
should require it. Checking them.
Comment 2 Andrew Garrett 2006-11-28 13:39:45 UTC
Seems to be a regression from r17804.
Comment 3 Rotem Liss 2006-11-28 13:45:04 UTC
I can't reproduce this bug on my MediaWiki installation (latest trunk, English,
preference is on). Probably worksframe. Where did you check it? If it's a local
installation, try to do "svn update".
Comment 4 Danny B. 2006-11-28 13:49:26 UTC
(In reply to comment #1)
> New pages and redirects (new and existing) don't require a manual summary, by
> purpose.

I can understand this, that's why I proposed the checkbox in preferences as the
alternative to force prompt.

On the other hand I know, there are people who like to fill it but sometimes
they just forget and that's why they have the prompt set on.

Prompt has also one nice side-effect: while creating new page you can
accidentaly press Submit instead of Preview and prompt blocks it from submitting
of half-done version.

(In reply to comment #3)
> I can't reproduce this bug on my MediaWiki installation (latest trunk, English,
> preference is on). Probably worksframe. Where did you check it? If it's a local
> installation, try to do "svn update".

Tested on cs.wikipedia -
http://cs.wikipedia.org/w/index.php?title=Wikipedista:Danny_B./test_shrnut%C3%AD&curid=150135&action=history
Comment 5 Rob Church 2006-12-01 17:31:48 UTC
When the preference is on, automatic summaries should be avoided wherever
possible in favour of screaming at the user to provide one.
Comment 6 Aaron Schulz 2008-09-16 16:56:42 UTC
Looking at the code, this is no longer the case.
Comment 7 Danny B. 2008-09-21 11:31:12 UTC
It is.

I do have "Prompt me when entering a blank edit summary" checked and it does not prompt when saving new page.

http://test.wikipedia.org/w/index.php?title=Autosummary&action=history
Comment 8 Aaron Schulz 2009-01-17 17:49:39 UTC
Gah, thought this was about section summaries. Fixed in r45843.
Comment 9 Aaron Schulz 2009-01-17 17:51:08 UTC
(In reply to comment #8)
> Gah, thought this was about section summaries. Fixed in r45843.
> 

Redirects left the same though.
Comment 10 Mark Hurd 2012-12-30 15:02:04 UTC
Just confirming, I see new pages being added without edit summaries, even though I have "Prompt me when entering a blank edit summary" checked, on Wikipedia and Wikiquote now (1.21wmf6 (9e7e0d1)).
Comment 11 Danny B. 2013-01-01 16:27:51 UTC
REOPEN per comment #10
Comment 12 Andre Klapper 2013-01-01 16:41:59 UTC
Mark / Danny: Please file new bug reports instead of reopening issues that were fixed three years ago. The problem likely is something different in the codebase, even if it has the same outcome.
Comment 13 Mark Hurd 2013-01-01 17:13:32 UTC
I didn't attempt to reopen (or add a new bug) because the commentary above for this bug did not make it (completely) clear that this scenario was addressed. I will start a new bug.
Comment 15 Danny B. 2013-01-01 19:38:58 UTC
(In reply to comment #12)
> Mark / Danny: Please file new bug reports instead of reopening issues that
> were
> fixed three years ago. The problem likely is something different in the
> codebase, even if it has the same outcome.

This is still the same *issue*. And *this issue* has not been solved, not even three years ago (I just simply forgot about this bug because made myself a gadget to fix that). Bugs are about issues not about particular line in code. If the issue is triggered by several places in code, then still one bug is supposed to be opened, not a single bug per any relevant place which triggers the issue.

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


Navigation
Links