Maniphest T196447

monolingual text and input type textarea with autocomplete
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	infinite-dao
	Jun 5 2018, 11:14 AM

Description

I use PF 4.3.1 and have set the form field “keywords” to autocomplete by a monolingual text property “Has keyword”. The form field definition looks like:

{{{field|keywords|input type=textarea with autocomplete|list|delimiter=,|values from property=Has keyword|rows=2|placeholder=Comma separated list of key words|remote autocompletion|autogrow}}}

… but in the form I only get the page to be selectable. If I use a property with normal data type text, then it works as expected.

Can one use monolingual text and have it selectable in the form?

Event Timeline

infinite-dao created this task.Jun 5 2018, 11:14 AM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJun 5 2018, 11:14 AM

@infinite-dao - what is "monolingual text"?

In T196447#4256879, @Yaron_Koren wrote:

@infinite-dao - what is "monolingual text"?

The data type text but with language specific values:
https://www.semantic-mediawiki.org/wiki/Help:Type_Monolingual_text

Oh - I don't think I had heard of that type, and I'm guessing that Page Forms doesn't support it - so unfortunately, I think the answer is no, for now.

Then it would be my feature request to get it working: form field autocompletion on a property that has data type monolingual Text. Right now it is not working.

A work around can be—for now—to create for each language a separate property or a Property that has a language code suffix in the page name to map it to different translated languages. I’m not sure how to best handle multiple languages within forms, extension translate can be used of course

Do I need to submit a feature request on this matter of multiple languages within page forms? If so, how?

• Vvjjkkii renamed this task from monolingual text and input type textarea with autocomplete to gmbaaaaaaa.Jul 1 2018, 1:05 AM

• Vvjjkkii triaged this task as High priority.

• Vvjjkkii added projects: CheckUser, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), Tamil-Sites, Gamepress, Hashtags, Jade, KartoEditor, Language-2018-Apr-June, New-Editor-Experiences, Mail, TCB-Team (now WMDE-TechWish).

• Vvjjkkii updated the task description. (Show Details)

• Vvjjkkii removed a subscriber: Aklapper.

Oetterer renamed this task from gmbaaaaaaa to monolingual text and input type textarea with autocomplete.Jul 1 2018, 6:10 AM

Oetterer raised the priority of this task from High to Needs Triage.

Oetterer removed projects: TCB-Team (now WMDE-TechWish), Mail, New-Editor-Experiences, Language-2018-Apr-June, KartoEditor, Jade, Hashtags, Gamepress, Tamil-Sites, Connected-Open-Heritage-Batch-uploads (RAÄ-KMB_1_2017-02), CheckUser.

Oetterer updated the task description. (Show Details)

Oetterer added a subscriber: Aklapper.

Yaron_Koren moved this task from Backlog to Semantic MediaWiki on the MediaWiki-extensions-Page_Forms board.Feb 4 2021, 2:48 AM

Does anyone know if there's still a problem autocompleting on "monolingual text"? Not with "textarea with autocomplete", presumably, since that input type no longer really exists, but with other input types.

monolingual text and input type textarea with autocompleteOpen, Needs TriagePublicActions

Description

Event Timeline

monolingual text and input type textarea with autocomplete
Open, Needs TriagePublic
Actions