https://bugzilla.wikimedia.org/show_bug.cgi?id=32102

       Web browser: ---
             Bug #: 32102
           Summary: #formlink: Works incorrectly if form name contains a
                    slash.
           Product: MediaWiki extensions
           Version: any
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: SemanticForms
        AssignedTo: [email protected]
        ReportedBy: [email protected]
                CC: [email protected]
    Classification: Unclassified


I created a form which name includes a slash, for example, `Region/Attributes'.
(I also have form `Region', and some other forms `Region/xxx'). Then I used
`#formlink' function to create a link:

{{ #formlink: form=Region/Attributes | link type = text | link text = Edit
attributes | target = Country }}

`#formlink' creates a link with target
`http://localhost.localdomain/wiki/Special:FormEdit/Region/Attributes/Country'.
When I click on the link, page `Country' is opened for editing with `Region'
form. That's incorrect, because the specified form is `Region/Attributes', not
just `Region'.

Some background. I developed an approach, when a page can be edited either as
whole, or each section separately (by clicking `[edit]' links at the top of
every section). The approach based on multiple forms and templates (to avoid
code duplication). I found it is convenient to move sub-forms to subpages of
base form. This is the reason for slash in the form name. Slash can be avoided
by using another form name, like "Region (Attributes)", but subpages are
convenient, because can be renamed with parent form, listed with SubPageList
extension, etc.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to