Last modified: 2013-01-23 10:19:23 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 T46239, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44239 - "Caller ID" Reserved word bug in SMW 1.8?
"Caller ID" Reserved word bug in SMW 1.8?
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
Semantic MediaWiki (Other open bugs)
master
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-22 13:52 UTC by Neill Mitchell
Modified: 2013-01-23 10:19 UTC (History)
5 users (show)

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


Attachments

Description Neill Mitchell 2013-01-22 13:52:05 UTC
Hi.

I'm running SMW 1.8 bundle on MW 1.19.3.

I'm seeing very weird behaviour on a form and template. If I have in my 
form:

! Caller ID
|{{{field|Caller ID}}}

In my template:

! Caller ID
| [[Caller ID::{{{Caller ID|}}}]]

When the form is saved you see this on the page:

[[Caller ID::Mitchell_Neill,1]]

and the Caller ID page property is not set.

If I change to:

! Caller ID
|{{{field|Caller}}}

! Caller ID
| [[Caller::{{{Caller|}}}]]

Then it works fine. You just see the field content Mitchell_Neill,1 and 
the property gets set.

Have I stumbled across a reserved word i.e. "Caller ID" in SMW/SF?
Comment 1 Jeroen De Dauw 2013-01-22 18:40:42 UTC
It not reserved
Comment 2 Gary Rodgers 2013-01-23 09:58:43 UTC
Okay, so we need to work out why this is not working. I can see nothing wrong with the syntax. 

If it is broken for my basic example, it is very likely it is broken for others.
Comment 3 Neill Mitchell 2013-01-23 10:06:28 UTC
I think this is related to bug 44104. The Caller ID is passed in via a formlink query string parameter. 

If the query string parameter is enclosed in a {{#urlencode: }} then it works.

So I think that if #44104 is fixed then this will go away.

I will close for now as I believe it is what is being passed by the formlink to the field that is at fault, not the field itself.
Comment 4 Gary Rodgers 2013-01-23 10:19:23 UTC
I think you are right. My example is (sorry, forgot to post it in this bug! Noob)

{{#formlink:form=Book Entry|link text=Add a Book|link
type=button|query string=Book[Title]={{PAGENAME}}}}

with this in the form

! Book Title
|{{{field|Title}}}

and I was seeing the same problem - this was showing in the saved field [[Title::Hydrogen Sonata, Iain M. Banks]]

I tried the suggested urlencode trick (after being advised to install the string functions extension first!)

{{#formlink:form=Book Entry|link text=Add a Book|link
type=button|query string={{#urlencode:Book[Title]={{PAGENAME}}}}}}

and it now works. So I concur, if bug 44104 is fixed then this problem would not occur.

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


Navigation
Links