Topic on Project:Support desk

MediaWiki 1.34.2 with Extension:ContactPage

My principally all default contact form as an automatically-formed "Subject" field; this field defaultly appears above additional fields (of the AdditionalFields array) but I want it to defaultly appear under them.

How to put "Subject" under additional fields (instead of above them)?

I need a backend solution (if I change it frontendly with JavaScript than the order of the fields in the form's input will mismatch the order of the fields in the form's output).

as = has*

I think that the only solution would be to make ContactPage contact forms totally modular but I don't think this solution would be available in the coming 10 years (I am not a PHP programmer and doesn't have even 7% of the knowledge required to do so), yet if I am wrong and there is another focal solution I would gladly try to implement it, I guess.

not sure its applicable but maybe the section field would help.

Also, the order of a form should not affect its output. Output is bassd on field name not order.

@Bawolff

Please kindly elaborate a bit more about the section field, what did you mean to suggest?

There's a field named 'section' that takes a value of 'section/subsection'. I've never used it and don't know how it works, but I know it exists

Output is bassd on field name not order

Given that current release ContactPage doesn't allow fully modular forms, I don't understand how this is relevant in that particular case - in great plea, elaborate more.

Respectfully (!!!),

I don't know what a modular form is.

You made the statement: "if I change it frontendly with JavaScript than the order of the fields in the form's input will mismatch the order of the fields in the form's output)" which doesn't make sense, because forms aren't ordered (Or at least not in the way you are implying).

@Bawolff

By modular form I mean to a form which doesn't come with any preexisting subset of fields; the user can thus toggle and untoggle (let along sort) which fields should be, or not, in the form; thus, no prexisting email and/or subject fields will be in the form unless the user puts these there (for the good and for the bad).

About the statement; I think it makes sense because for example, if you change say the first form field to be the last with JavaScript and a user comes and submits that form -- the "last" field will still be first in the output ---- as the backend behavior wasn't changed.

you can make such a form but you would have to write your own extension.

The backend doesn't look at the order of the fields in the output, it looks at the field names. As far as i know.