Last modified: 2014-04-21 21:09:02 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 T20103, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 18103 - removal of principal named reference silently breaks others
removal of principal named reference silently breaks others
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
Cite (Other open bugs)
unspecified
All All
: Low enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 57364 (view as bug list)
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-03-22 12:03 UTC by reisio
Modified: 2014-04-21 21:09 UTC (History)
2 users (show)

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


Attachments

Description reisio 2009-03-22 12:03:11 UTC
Unwary editors occasionally remove a principal named reference (<ref name="foo">bar</ref>) in an article where it is still being used elsewhere in the form <ref name="foo" />, thus silenting breaking references & often leading to another (or the same :p) editor simply removing all instances of the reference, presumably under the assumption that the initial inclusion was improper.

A check — & subsequent warning, if prudent — for remaining references with a name matching a non-empty reference being removed in the current edit would likely prevent most such happenings.
Comment 1 Gadget850 2010-05-22 13:47:20 UTC
This error check has been in place for some time. The base Cite.php message is Cite error references no text. On en.wiki, this shows as "Cite error: Invalid <ref> tag; no text was provided for refs named $1; see Help:Cite error."
Comment 2 reisio 2010-05-22 21:06:45 UTC
That's after the damage is done.  There should be a check before the edit is allowed to be committed.
Comment 3 Gadget850 2010-05-23 13:44:07 UTC
(In reply to comment #2)
> That's after the damage is done.  There should be a check before the edit is
> allowed to be committed.

I can see a check if you edit the whole article, but I don't see how it can be done if you edit a section. That will take someone with some programming smarts.
Comment 4 reisio 2010-05-24 14:23:20 UTC
Yes... fixing bugs in software requires programming knowledge...
Comment 5 James Forrester 2014-04-21 21:09:02 UTC
*** Bug 57364 has been marked as a duplicate of this bug. ***

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


Navigation
Links