Last modified: 2013-01-18 17:32:06 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 T32255, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 30255 - #ask result maps with template giving UNIQ/QINU tags
#ask result maps with template giving UNIQ/QINU tags
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticMaps (Other open bugs)
unspecified
PC Windows Server 2003
: Unprioritized major (vote)
: ---
Assigned To: Jeroen De Dauw
:
Depends on:
Blocks: UNIQ
  Show dependency treegraph
 
Reported: 2011-08-05 22:58 UTC by Brandon Plewe
Modified: 2013-01-18 17:32 UTC (History)
2 users (show)

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


Attachments

Description Brandon Plewe 2011-08-05 22:58:09 UTC
Trying to upgrade to MW 1.17/SMW 1.6/SM 1.0, but a new problem emerged:
When I have an ask query with map results that use a template, many of the formatted elements (headers and links at least) that appear above the map have the UNIQ...QINU in them, with source code like:
<h3> <span class="mw-headline" id=".7FUNIQ527bb8725a0682a4-h-0--QINU.7FSettlements">UNIQ527bb8725a0682a4-h-0--QINUSettlements</span></h3>

I have some form links which are replaced completely by the UNIQ tag:
{{#formlink:form=TextBlock|link text=Add quote...|query string=super_page={{PAGENAME}}&Attribute_t[Place]={{PAGENAME}}&Attribute_t[AttType]=quote}}
becomes
UNIQ352fb3c1cbec798-item-1--QINU

formatted elements appearing *below* the map are fine.  Other templates work fine, and if I remove the template= from the ask query, it works fine.

This wasn't a problem in MW 1.16.1/SMW 1.5.6/SM 0.7.7.  I think I followed all the upgrading instructions.  Might I have missed something?
Comment 1 Jeroen De Dauw 2011-08-05 23:11:25 UTC
This is a bug occurring when combining MediaWiki 1.17.x with SM 1.0 and using the template parameter. I have looked at it but could not find any working solution. (Well, this sort of is, originally you'd simply get a fatal error when trying to use the template parameter)

The issue does not occur for MediaWiki 1.18 and later.

This is quite unfortunate of course. You can always try getting a core dev that knows the MediaWiki parser well have a look at it.
Comment 2 Brandon Plewe 2011-08-05 23:43:43 UTC
Ouch!  This is no the answer I'd like, but I understand that it is not worth fixing if it will go away soon.

I suppose I can make do until 1.18 is released.
Comment 3 Leonard Wallentin 2012-11-28 21:27:59 UTC
This old friend suddenly resurfaced again. It seems to me like it happened here: https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/SemanticMaps.git;a=commitdiff;h=969389786dcfffdeb12f5758d82279d0c509e995

See example output here http://xn--ssongsmat-v2a.nu/ssm/Test
Comment 4 Leonard Wallentin 2012-11-28 21:30:09 UTC
MediaWiki 1.21alpha (c86351c)
Semantic MediaWiki 1.8rc1
Semantic Maps 2.1 alpha (30c1b77)
Maps 2.1 alpha (818f8f4)
Comment 5 Leonard Wallentin 2013-01-17 11:00:24 UTC
Investigating further, this seems to happen when a template included at the same page as the map contains one or more <nowiki />-codes. It also happens when calling parser functions that use Parser::recursiveTagParse somewhere in the code.
Comment 6 Leonard Wallentin 2013-01-17 11:01:58 UTC
...but only if the parser (or tag) function is placed BEFORE the map ...
Comment 7 Leonard Wallentin 2013-01-17 11:13:19 UTC
And finally a live example: http://semantic-mediawiki.org/wiki/Semantic_Maps_examples/Using_templates_(queries)
Comment 8 Jeroen De Dauw 2013-01-18 13:03:56 UTC
Could you try https://gerrit.wikimedia.org/r/#/c/44608/ and see if that fixes it?

It's putting back in the old dirty fix, no time to look for something better ATM.
Comment 9 Leonard Wallentin 2013-01-18 13:39:47 UTC
Yes, that fixes it!

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


Navigation
Links