Last modified: 2014-02-12 23:38:32 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 T46105, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 44105 - SF info page name parameter truncates values with apostrophes
SF info page name parameter truncates values with apostrophes
Status: NEW
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-01-18 14:35 UTC by Neill Mitchell
Modified: 2014-02-12 23:38 UTC (History)
0 users

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


Attachments

Description Neill Mitchell 2013-01-18 14:35:18 UTC
Hi.

I'm running SMW bundle 1.18, SF 2.5.1 on MW 1.19.3.

Continuing with the apostrophe testing. I'm using the SF one step process to create pages. The info page name parameter truncates values with apostrophes.

I have:

{{{info|add title=Add a Subsection|edit title=Editing Subsection|page name=<Subsection Admin[Parent]> - <Subsection Template[Subsection ID] }}}

If the Parent value contains an apostrophe, the page name is truncated and the - <Subsection Template[Subsection ID] part of the page name is missed off entirely.

Example. If the Parent is "What's New" and the Subsection ID is "Education". The resulting page is created as "What" instead of "What's New - Education.

Again, I'm sure this was fixed and working in an older version.

Any help appreciated. Apostrophes are very common, so not handling them is a real pain.

Thanks
Neill.
Comment 1 Neill Mitchell 2013-01-18 14:39:51 UTC
SMW is version 1.8 of course.
Comment 2 Neill Mitchell 2013-01-18 15:02:28 UTC
Fix to this of course would be to urlencode the value when passing it and then urldecoding it.

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


Navigation
Links