Last modified: 2013-07-30 13:52:44 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 T53910, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 51910 - No <references/> warning not intuitive
No <references/> warning not intuitive
Status: RESOLVED DUPLICATE of bug 45132
Product: VisualEditor
Classification: Unclassified
Editing Tools (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Rob Moen
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-07-23 20:32 UTC by John Mark Vandenberg
Modified: 2013-07-30 13:52 UTC (History)
5 users (show)

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


Attachments

Description John Mark Vandenberg 2013-07-23 20:32:21 UTC
After adding a reference, this new user couldnt work out what to do.
https://es.wikipedia.org/w/index.php?title=Caballete&diff=next&oldid=68554884 
(ignore the first diff block; that is another bug)
Comment 1 Amir E. Aharoni 2013-07-26 07:18:36 UTC
Is this a duplicate of Bug 51873 [reported by yourself ;-) ]?
Comment 2 John Mark Vandenberg 2013-07-26 08:24:34 UTC
Hehe; no.
bug 51873 is references with no ref.
this bug is ref with no references, which gives no warning at all in VE, and then after saving says "Cite error: <ref> tags exist, but no <references/> tag was found"

The title of this bug could be: inserting a ref should _automatically_ insert a references block if there is none, and warn the user on save if they have a ref in a group which doesnt have a corresponding references tag.
Comment 3 Chris McKenna 2013-07-30 10:13:09 UTC
Is this the same as Bug 45132?
Comment 4 James Forrester 2013-07-30 13:52:44 UTC
(In reply to comment #3)
> Is this the same as Bug 45132?

Yes.

*** This bug has been marked as a duplicate of bug 45132 ***

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


Navigation
Links