Last modified: 2013-12-27 13:54:51 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 T59332, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 57332 - Subsection headers in SF sections prevent correct content parsing
Subsection headers in SF sections prevent correct content parsing
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
SemanticForms (Other open bugs)
REL1_21-branch
All All
: Unprioritized normal (vote)
: ---
Assigned To: Yaron Koren
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-11-20 23:43 UTC by Ben
Modified: 2013-12-27 13:54 UTC (History)
1 user (show)

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


Attachments

Description Ben 2013-11-20 23:43:48 UTC
When a Semantic Form contains a {{{section}}} and the user includes a subsection header (=== Subsection ===) in the content for that section, the resulting page content will not be parsed correctly when the page is edited with form, probably because the first two == of the subection header are recognized as a section header.

From a developer mailing list conversation, the code in question is likely located at lines 1415-1450 of /includes/SF_FormPrinter.php.
Comment 1 Gerrit Notification Bot 2013-12-09 19:27:12 UTC
Change 100421 had a related patch set uploaded by Himeshi:
Modified seperation of existing page content with sections in SF_FormPrinter.php

https://gerrit.wikimedia.org/r/100421
Comment 2 Gerrit Notification Bot 2013-12-09 20:25:21 UTC
Change 100421 merged by jenkins-bot:
Modified seperation of existing page content with sections in SF_FormPrinter.php

https://gerrit.wikimedia.org/r/100421
Comment 3 Yaron Koren 2013-12-09 20:27:14 UTC
Ben - I believe Himeshi's recent change fixed this problem. If possible, could you upgrade to the latest SF code, and let us know if that worked?
Comment 4 Yaron Koren 2013-12-27 13:54:51 UTC
Marking this as fixed, since I believe the problem is now resolved.

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


Navigation
Links