Last modified: 2013-02-18 03:57:59 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 T44856, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 42856 - subobject property names inconsistency
subobject property names inconsistency
Status: RESOLVED INVALID
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-12-08 06:14 UTC by John McClure
Modified: 2013-02-18 03:57 UTC (History)
4 users (show)

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


Attachments

Description John McClure 2012-12-08 06:14:17 UTC
SMW accepts property names beginning with a "period", which I use conventionally to identify all text/string properties. However, when used with subobjects, SMW fails to process the {{#subobject}} function successfully. When I remove the "period" before property names, then it operates fine.
Comment 1 John McClure 2012-12-08 06:17:09 UTC
MediaWiki 	1.17.0
PHP 	5.2.17 (cgi)
MySQL 	5.1.65-rel14.0-log
Semantic MediaWiki (Version 1.7.1)
Comment 2 MWJames 2012-12-09 13:39:07 UTC
Based on the above description and with the understanding of using "period" as a prefix such as ".has text::test" to specify a property/value relationship.

I can't confirm this bug because 
* Using [[.has text::test]] will result in a property ".has text" with value "test"
* Using {{#subobject:|.has text=test2}} will result in a subobject with a property ".has text" and value "test2"

The above was tested against SMW 1.9[1]

[1] https://gerrit.wikimedia.org/r/#/c/37020/

It is highly recommended that you update at least to SMW 1.8 to verify of this bug 
is still valid otherwise this bug will be rendered invalid due to an insufficient release (SMW 1.7.1).
Comment 3 MWJames 2013-02-18 03:57:59 UTC
SMW 1.7.1 is no longer in active development. The described behaviour has not been verified against the current SMW 1.9 release.

Please feel free to re-open this issue if it relates to SMW 1.8 or SMW 1.9.

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


Navigation
Links