vipul.wikis wrote:

The bug also appears to be present at Semantic Web:

http://www.semanticweb.org

For instance, from the People page:

http://semanticweb.org/wiki/People

clicking "Show more people" takes us to this page:

http://semanticweb.org/wiki/Special:Ask/-5B-5BCategory:Person-5D-5D-20-5B-5B:%2B-7C-7CUser:%2B-5D-5D/-3F-23/-3FAffiliation/mainlabel%3D

where the first column is duplicated.

Looks like these queries are simply requesting the extra column.

This will get you the main column, but without the subject being linked: ?#-

If you only want this non-linked column, also add mianlabel=-

vipul.wikis wrote:

(In reply to comment #2)

Looks like these queries are simply requesting the extra column.

This will get you the main column, but without the subject being linked: ?#-

If you only want this non-linked column, also add mianlabel=-

I don't understand this. Yes, the clicked-on queries are requesting the extra column. But the original #ask query is not requesting the extra column. So it seems that the code that's being used to convert the #ask query is buggy. The code was working okay until Semantic MediaWiki version 1.5.6.

If this is not a bug but an intentional feature, I don't understand what the purpose of that feature is. Why would a person want to see the same information in two columns when clicking on a link, when the person hasn't explicitly specified this?

The mainlabel=- doesn't work, it removes both the columns.

Oh, I was a bit to quick there :)

You are right, there was an issue with the link to special:ask created by inline queries. Issue was introduced after 1.6.1.

Fix in r107850

Thanks for reporting :)

See also bug 37214