CSP Wiki - User contributions [en]

Property:Doc synopsis

2025-08-27T10:13:47Z

944f869b-8467-464e-95c7-903362952755: Created page with "{{#set: Has type=Text }}"

DevOps:Doc/FlexForm/2.0/create

2025-08-25T12:02:59Z

944f869b-8467-464e-95c7-903362952755: mwwrite: add two further options

===Name===
_create
===Type===
_create
===Synopsis===
Using a form to create new pages or overwrite existing pages
===Description===
_create can be defined as part of a form to have new page(s) created on form submit or overwrite (an) existing page(s).
===Parameters===
'''_create'''

'''mwtemplate''' = Name of a template to use as content for the new page. If you have a form with only one input element you can also use mwtemplate="wsnone". This will take the content of the form input element and make it the source content of the new page (without putting it inside a template).

'''mwwrite''' = Full name of the target page; or when used with 'mwoption', part of the page name; or a formula in the format "::id::< ... >" referencing the value of 'mwwrite' from another <code>_create</code> (see example 4 below).

'''mwfollow''' = Will send the user to the newly create page after form submission

'''mwoption''' can hold three different values:

* "'''add_random'''" = Create random numbers
* "'''next_available'''" = Get the next available number. If mwwrite is : "orders/", this option will find the highest orders number (e.g. orders/192) and will create a page with one number higher (e.g. orders/193)
* "'''range:'''" = Get the next available free slot in a range of numbers. If mwwrite is : "orders/", this option will find the first free spot in a range of numbers. If mwoption="range:2019000-2019999" and mwwrite="orders/" then FlexForm will start looking for a page called orders/2019000. If exists it will look for orders/2019001 etc.. till the first free page is found.

'''mwleadingzero''' can be used in combination with range. When a range is set like 1-99999 using mwleadingzero will use the length of the end range and use it to fill the start range with leading zeros, making the range from 00001-99999.

'''mwfields''' = comma separated names of form elements that need to be included. Only works when using multiple _create.

If you are creating multiple pages and want to re-assign form fields to template variables, you still add the form field name to mwfields, but add "'''::'''" and then the name of the template variable. So if you want to tell mwfields to use formfield "'''name2'''", but add it to the template as "'''Name'''", add : "'''name2::Name'''" to mwfields.

'''mwslot''' = name of a specific content slot to use.

'''nooverwrite''' = when this is set, no create will be done for a page that already exists. Even if you are creating a new slot for a page that already exist.

'''noseo''' = when this is set, even if the setting '''create-seo-titles''' in your local settings is set to '''true''' to always create SEO friendly page titles, it will not make the title of a new page SEO friendly, but use the title given.

'''mwformat''' = defaults to wiki. Currently only supports wiki or json. When set to json, the page content of the page will become a json. When used with mwtemplate, then the template name will be the key for the json. All form values will be stored as strings. Every new array with key names will automatically get a ffID value that will always be unique. This is done for easy editing later.

There are several ways for creating a page with FlexForm.

# Easiest Use mwtemplate and mwwrite as described above (and optionally wsfollow, wsoption, etc) This will use the values of mwtemplate and mwwrite and any form elements the current for has and create a new page with template "mwtemplate" and title of "mwwrite". See example 1.
# More advanced and possibilities Use mwtemplate and mwwrite with more options than described above (and optionally wsfollow, wsoption, etc) mwwrite can use can use other elements in the form and use those values to create a title for a new page. Field names can be added using square brackets. So if a form also has a text input field of "title" mwwrite could be "[title]". [mwrandom] can also be used e.g. mwwrite="[title]/[mwrandom]". See example 2.
# Create multiple pages with one form and control what form elements are used. This is where mwfields comes in. This is a comma separated list of form elements that will be used to create the new page. If a form has 15 text input fields, then using _create will include all 15 (filled-in by user) elements in the new page. Using mwfields you can tell _create specifically what form element to use to create a new page. So, when creating multiple new pages with one form, mwfields should be used with any and all _create. See example 3.
# Create a new page and fill different content slots for that page. You have to give the definition of the first _create an id. The other _create elements reference the first _create with a mwwrite like mwwrite="::id::<idOfWSCreateWithID>". See example 4.

===Example===
Example 1 : Create a new page with the next available number
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="next_available" />
</syntaxhighlight>
Create a new page with the next available number in a range and always start from the beginning
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="range:2019000-2019999" />
</syntaxhighlight>
Random number
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:" mwoption="add_random" mwtemplate="Solution" />
</syntaxhighlight>

Example 2 : Create from text, mwrandom and fieldvalues
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/[mwrandom]" mwtemplate="Solution" />
</syntaxhighlight>

Example 3 : Create from text and field values and only include specific form element names in the new template
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/Personal" mwtemplate="Personal" mwfields="naam, adres, straat, plaats" />
<_create mwwrite="Proj-solution:[namefield]/Business" mwtemplate="Business" mwfields="Company, cadres, cstraat, cplaats" />
</syntaxhighlight>

Example 4 : Create a page with title : Test/[title]. With no main content and a template of Structured data with an argument of Hello in slot:mds-metadataslot". At the same time content slot "mds-metadataslot2" get the same template with argument Hello2.
<syntaxhighlight lang="html">
<_create id="testingSlot" mwwrite="Test/[title]" mwtemplate="Structured data" mwfollow mwfields="Hello" mwslot="mds-metadataslot" />
<_create mwwrite="::id::testingSlot" mwtemplate="wsnone" mwfields="Hello2" mwslot="mds-metadataslot2" />
</syntaxhighlight>

Example 5 : Use '''wsnone''' and '''[https://www.mediawiki.org/wiki/Help:Substitution substitution] ''' to copy content of an existing page onto a new page. This example copies the content of "Main Page" when creating a new page named "Test new page".
<syntaxhighlight lang="html">
<form>
<_create mwwrite="Test new page" mwtemplate="wsnone" mwfields="Content" />
<textarea name="Content">{{subst::Main Page}}</textarea>
<input type="submit" />
</form>
</syntaxhighlight>

===Note===
If you create a page from text, mwrandom and field values and also add mwoption="add_random", another random number will be added to the end of the page title.

You can have multiple instances of _create in a form, as long as mwfields is a non empty argument with every _create.
If you have multiple _create and they all have a mwfollow, the last _create in the list will be followed.
===Links===
https://www.mediawiki.org/wiki/Multi-Content_Revisions

{{FlexForm/Create and edit comparison}}

DevOps:Doc/FlexForm/2.0/input/select

2025-07-12T07:56:22Z

944f869b-8467-464e-95c7-903362952755: /* Example */ demonstrate use of 'selected'

===Name===
select (dropdown)
===Type===
select
===Synopsis===
How to use select with option fields to create a dropdown input
===Description===
The <code>select</code> element is used to create a drop-down list.

The <code>name</code> attribute is needed to reference the form data after the form is submitted (if you omit the <code>name</code> attribute, no data from the drop-down list will be submitted).

The <code>id</code> attribute is needed to associate the drop-down list with a label.

The <code><nowiki><option></option></nowiki></code>tags inside the <code><nowiki><select></nowiki></code> element define the available options in the drop-down list.

Instead of option inputs, it's also possible to use <code>selected</code> and <code>options</code> as attributes of the select element. In this case <code>options</code> should contain a comma-separated list of options and <code>selected</code> can be used to specify which option should be selected.

===Parameters===
<code><nowiki><select><option></option></select></nowiki></code>

You can also use placeholder to have an extra, non-selectable item with a suggestion. This also allows for not sending any data from a select, when the placeholder is still selected. Making a select field also an optional field in a form. See example 1.

Select values have by default comma separated values when adding to a Template. You can specify a different separator using the argument '''separator'''. e.g. separator=";".

All other valid HTML5 attributes are allowed
===Example===
<syntaxhighlight lang="html">
<p>Select a car:</p>
<div>
<select name="car" placeholder="Choose a car">
<option value="volvo">Volvo</option>
<option value="saab" selected="selected">Saab</option>
</select>
</div>
</syntaxhighlight>
<div>
<select name="car" placeholder="Choose a car">
<option value="volvo">Volvo</option>
<option value="saab" selected="selected">Saab</option>
</select>
</div>

<syntaxhighlight lang="html">
<label for="dino-select">Choose a dinosaur:</label>
<select id="dino-select">
<optgroup label="Theropods">
<option value="Tyrannosaurus">Tyrannosaurus</option>
<option value="Velociraptor">Velociraptor</option>
<option value="Deinonychus">Deinonychus</option>
</optgroup>
<optgroup label="Sauropods">
<option value="Diplodocus">Diplodocus</option>
<option value="Saltasaurus">Saltasaurus</option>
<option value="Apatosaurus">Apatosaurus</option>
</optgroup>
</select>
</syntaxhighlight>
<label for="dino-select">Choose a dinosaur:</label>
<select id="dino-select">
<optgroup label="Theropods">
<option value="Tyrannosaurus">Tyrannosaurus</option>
<option value="Velociraptor">Velociraptor</option>
<option value="Deinonychus">Deinonychus</option>
</optgroup>
<optgroup label="Sauropods">
<option value="Diplodocus">Diplodocus</option>
<option value="Saltasaurus">Saltasaurus</option>
<option value="Apatosaurus">Apatosaurus</option>
</optgroup>
</select>

<syntaxhighlight lang="html">
<select name="Test" selected="C" options="A,B,C,D,E" />
</syntaxhighlight>

<select name="Test" selected="C" options="A,B,C,D,E" />

DevOps:Doc/FlexForm/2.0/Installation of FlexForm

2025-07-10T07:07:33Z

944f869b-8467-464e-95c7-903362952755: /* Notification/Messages */

FlexForm is installed using [https://www.mediawiki.org/wiki/Composer/For_extensions Composer]:

<syntaxhighlight lang="php">
composer require open-csp/flex-form
</syntaxhighlight>

You can install FlexForm from [https://github.com/Open-CSP/FlexForm github] by installing it in extensions/FlexForm. You do have to run composer --update inside that folder after installation to get all dependencies.

==== Setup ====
You can tweak '''FlexForm''' to an extent in your <code>LocalSettings.php</code> file:

<syntaxhighlight lang="php">
// Will render form that makes no sense when inspected in the browser.
$wgFlexFormConfig['secure'] = true;

// A salt key for encryption. Used together with "secure" option. Must be set when using multiple instances of a wiki.
$wgFlexFormConfig['sec_key'] = "";

// Interval time in ms, defaults to 3 minutes (180000 ms). Form is submitted on each interval regardless of changes.
$wgFlexFormConfig['auto_save_interval'] = 30000;

// Time in ms, defaults to 3 seconds (3000 ms). Form is submitted after the specified time, timer starts when there is a change in the form. Timer resets if there is another change before the time has passed.
$wgFlexFormConfig['auto_save_after_change'] = 3000;

// Text on the autosave button to toggle on.
$wgFlexFormConfig['auto_save_btn_on'] = 'Autosave on';

// Text on the autosave button to toggle off.
$wgFlexFormConfig['auto_save_btn_off'] = 'Autosave off';

// Currently the only form.
$wgFlexFormConfig['FlexFormDefaultTheme'] = "plain";

// reCaptcha site key.
$wgFlexFormConfig['rc_site_key'] = "";

// reCaptcha secret key.
$wgFlexFormConfig['rc_secret_key'] = "";

// Where to store images temporarily that need to be format converted.
$wgFlexFormConfig['file_temp_path'] = "";

// Defaults to false. Set to yes if FlexForm is allowed to create new users.
$wgFlexFormConfig['can_create_user'] = "";

// Defaults to false. Will filter all parser arguments to plain text, except value parameters. Will also disallow onClick and onFocus parameter. This feature will most likely be removed in future updates.
$wgFlexFormConfig['filter_input_tags'] = false;

// Defaults to what is described by the loadscript form argument. When you change it do a different folder, then loadScript argument will be looking in this folder for its JavaScript file to load with the Form.
$wgFlexFormConfig['loadScriptPath'] = "";

// Defaults to sysop. Only a user in the allowedGroups is able to edit pages with a FlexForm in the source.
$wgFlexFormConfig['allowedGroups'] = ["sysop","moderator"];

// Defaults to true. When a user in the allowedGroups creates a form it will become valid and will be rendered. Someone not in the allowedGroups can create a form and save it, but it will never be rendered until a user from the allowedGroups will edit and re-save the page. Only then will a form become valid. The message "FORM CANNOT BE RENDERED, NOT VALIDATED" will be shown instead of the form when it is invalid or depending on the next setting an image stating it cannot be rendered.
$wgFlexFormConfig['renderonlyapprovedforms'] = true;

// When a form is invalid, an invalid image will be rendered instead of the form. Set to true to render i18n invalid message.
$wgFlexFormConfig['renderi18nErrorInsteadofImageForApprovedForms'] = false;

// Defaults to false. This differs from FlexForm before 2.0. FlexForm will now honor the UserCan functions in MediaWiki. If a form edits or creates a page a user has no rights to, the form will fail.
$wgFlexFormConfig['userscaneditallpages'] = false;

// Defaults to true. If a user is not in the allowedGroups then hide edit and editsource menu items for any page containing a FlexForm form.
$wgFlexFormConfig['hideEdit'] = true;

// Defaults to false. Will turn titles given to wscreate into url friendly slugs. Creating only latin character and converting spaces and special characters.
$wgFlexFormConfig['create-seo-titles'] = true;

// If you have a custom/different version of Pandoc than the one set by your hosting provider, you can add its local path here and FlexForm will use it, instead of the one set by environment variables
$wgFlexFormConfig['pandoc-install-path'] = $IP . '/bin/pandoc'; // This will look for Pandoc executable in the root/bin of your MediaWiki instalment

// FlexForm will by default always do an extra null edit on a save or an edit. This is mainly due to SMW. Not always this is necessary, so with this option you can turn it off. ( resulting in less handling time )
$wgFlexFormConfig['forceNullEdit'] = true; // Default to true for backwards compatibility

// When sending email, should we use separate smtp?
$wgFlexFormConfig['use_smtp'] = false;

$wgFlexFormConfig['smtp_host'] = "";

$wgFlexFormConfig['smtp_authentication'] = true;

$wgFlexFormConfig['smtp_username'] = "";

$wgFlexFormConfig['smtp_password'] = "";

$wgFlexFormConfig['smtp_secure'] = "TLS";

$wgFlexFormConfig['smtp_port'] = "587";

</syntaxhighlight>

==== Installation ====
* Add the following line at the end of your <code>LocalSettings.php</code> to enable the extension:

<syntaxhighlight lang="php">
wfLoadExtension( 'FlexForm' );
</syntaxhighlight>

* It is also recommended to turn off the parser cache when using FlexForm:

<syntaxhighlight lang="php">
$wgParserCacheType = CACHE_NONE;
</syntaxhighlight>

* Run the [https://www.mediawiki.org/wiki/Manual:Update.php update script] which will automatically create the necessary database tables that this extension needs.
* Navigate to Special:Version on your wiki to verify that the extension is successfully installed.

==== Migrate from version 1.x to 2.0 ====
* Please notice the changes in the config settings.
* Do not forget to run update.php.
* Also, by default, the setting '''renderonlyapprovedforms''' will be '''true'''. Meaning that once you install FlexForm v2.0 all your existing FlexForm forms in your wiki will be shown as unvalidated. Visit [[DevOps:Doc/FlexForm/2.0/Validated Forms|Validated Forms]] to read how to solve this easily.

==== Notification/Messages ====
FlexForm has a notification system built in. This is used to show possible errors or success/custom messages.

'''As of version 2.2.2 this is a default feature''' and <nowiki><form showmessage /></nowiki> is deprecated.

DevOps:Doc/FlexForm/1.0/Error-messages

2025-07-10T07:04:50Z

944f869b-8467-464e-95c7-903362952755: clearer

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|-
| /Special:FlexForm Error: Class "JsonPath\JsonObject" not found
| forms
| shown when JsonPath is missing
| This, and similar errors about missing classes, may happen when you forgot to run 'composer update' or 'composer update' somehow failed to install the required package (in this case, [https://github.com/Galbar/JsonPath-PHP JsonPath]). Make sure FlexForm's composer.json is included in the merge-plugin section of your composer.local.json.
|}

=== Error messages in the browser's console ===

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|-
| <code>SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line [...] column [...] of the JSON data</code> (FlexForm.general.js)
| This may happen if you have set your config options for debugging in such a way that any PHP warnings are printed, in turn mangling the JSON output expected by FlexForm. It is generally not a good idea to permanently use settings like <code>ini_set( 'display_errors', 1 ) </code> or <code>error_reporting( E_ALL )</code> in a live environment.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/1.0/Error-messages

2025-07-04T13:00:22Z

944f869b-8467-464e-95c7-903362952755:

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|-
| /Special:FlexForm Error: Class "JsonPath\JsonObject" not found
| forms
| shown when JsonPath is missing
| You must first download and install [https://github.com/Galbar/JsonPath-PHP JsonPath]
|}

=== Error messages in the browser's console ===

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|-
| <code>SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line [...] column [...] of the JSON data</code> (FlexForm.general.js)
| This may happen if you have set your config options for debugging in such a way that any PHP warnings are printed, in turn mangling the JSON output expected by FlexForm. It is generally not a good idea to permanently use settings like <code>ini_set( 'display_errors', 1 ) </code> or <code>error_reporting( E_ALL )</code> in a live environment.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/1.0/Error-messages

2025-07-04T12:59:04Z

944f869b-8467-464e-95c7-903362952755: +JsonPath error - not yet sure how to install it

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|-
| /Special:FlexForm Error: Class "JsonPath\JsonObject" not found
| You must first download and install [https://github.com/Galbar/JsonPath-PHP JsonPath]
|}

=== Error messages in the browser's console ===

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|-
| <code>SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line [...] column [...] of the JSON data</code> (FlexForm.general.js)
| This may happen if you have set your config options for debugging in such a way that any PHP warnings are printed, in turn mangling the JSON output expected by FlexForm. It is generally not a good idea to permanently use settings like <code>ini_set( 'display_errors', 1 ) </code> or <code>error_reporting( E_ALL )</code> in a live environment.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/2.0/create

2025-07-03T07:48:00Z

944f869b-8467-464e-95c7-903362952755: update input to textarea

===Name===
_create
===Type===
_create
===Synopsis===
Using a form to create new pages or overwrite existing pages
===Description===
_create can be defined as part of a form to have new page(s) created on form submit or overwrite (an) existing page(s).
===Parameters===
'''_create'''

'''mwtemplate''' = Name of a template to use as content for the new page. If you have a form with only one input element you can also use mwtemplate="wsnone". This will take the content of the form input element and make it the source content of the new page (without putting it inside a template).

'''mwwrite''' = Full name of the target page

'''mwfollow''' = Will send the user to the newly create page after form submission

'''mwoption''' can hold three different values:

* "'''add_random'''" = Create random numbers
* "'''next_available'''" = Get the next available number. If mwwrite is : "orders/", this option will find the highest orders number (e.g. orders/192) and will create a page with one number higher (e.g. orders/193)
* "'''range:'''" = Get the next available free slot in a range of numbers. If mwwrite is : "orders/", this option will find the first free spot in a range of numbers. If mwoption="range:2019000-2019999" and mwwrite="orders/" then FlexForm will start looking for a page called orders/2019000. If exists it will look for orders/2019001 etc.. till the first free page is found.

'''mwleadingzero''' can be used in combination with range. When a range is set like 1-99999 using mwleadingzero will use the length of the end range and use it to fill the start range with leading zeros, making the range from 00001-99999.

'''mwfields''' = comma separated names of form elements that need to be included. Only works when using multiple _create.

If you are creating multiple pages and want to re-assign form fields to template variables, you still add the form field name to mwfields, but add "'''::'''" and then the name of the template variable. So if you want to tell mwfields to use formfield "'''name2'''", but add it to the template as "'''Name'''", add : "'''name2::Name'''" to mwfields.

'''mwslot''' = name of a specific content slot to use.

'''nooverwrite''' = when this is set, no create will be done for a page that already exists. Even if you are creating a new slot for a page that already exist.

'''noseo''' = when this is set, even if the setting '''create-seo-titles''' in your local settings is set to '''true''' to always create SEO friendly page titles, it will not make the title of a new page SEO friendly, but use the title given.

'''mwformat''' = defaults to wiki. Currently only supports wiki or json. When set to json, the page content of the page will become a json. When used with mwtemplate, then the template name will be the key for the json. All form values will be stored as strings. Every new array with key names will automatically get a ffID value that will always be unique. This is done for easy editing later.

There are several ways for creating a page with FlexForm.

# Easiest Use mwtemplate and mwwrite as described above (and optionally wsfollow, wsoption, etc) This will use the values of mwtemplate and mwwrite and any form elements the current for has and create a new page with template "mwtemplate" and title of "mwwrite". See example 1.
# More advanced and possibilities Use mwtemplate and mwwrite with more options than described above (and optionally wsfollow, wsoption, etc) mwwrite can use can use other elements in the form and use those values to create a title for a new page. Field names can be added using square brackets. So if a form also has a text input field of "title" mwwrite could be "[title]". [mwrandom] can also be used e.g. mwwrite="[title]/[mwrandom]". See example 2.
# Create multiple pages with one form and control what form elements are used. This is where mwfields comes in. This is a comma separated list of form elements that will be used to create the new page. If a form has 15 text input fields, then using _create will include all 15 (filled-in by user) elements in the new page. Using mwfields you can tell _create specifically what form element to use to create a new page. So, when creating multiple new pages with one form, mwfields should be used with any and all _create. See example 3.
# Create a new page and fill different content slots for that page. You have to give the definition of the first _create an id. The other _create elements reference the first _create with a mwwrite like mwwrite="::id::<idOfWSCreateWithID>". See example 4.

===Example===
Example 1 : Create a new page with the next available number
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="next_available" />
</syntaxhighlight>
Create a new page with the next available number in a range and always start from the beginning
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="range:2019000-2019999" />
</syntaxhighlight>
Random number
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:" mwoption="add_random" mwtemplate="Solution" />
</syntaxhighlight>

Example 2 : Create from text, mwrandom and fieldvalues
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/[mwrandom]" mwtemplate="Solution" />
</syntaxhighlight>

Example 3 : Create from text and field values and only include specific form element names in the new template
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/Personal" mwtemplate="Personal" mwfields="naam, adres, straat, plaats" />
<_create mwwrite="Proj-solution:[namefield]/Business" mwtemplate="Business" mwfields="Company, cadres, cstraat, cplaats" />
</syntaxhighlight>

Example 4 : Create a page with title : Test/[title]. With no main content and a template of Structured data with an argument of Hello in slot:mds-metadataslot". At the same time content slot "mds-metadataslot2" get the same template with argument Hello2.
<syntaxhighlight lang="html">
<_create id="testingSlot" mwwrite="Test/[title]" mwtemplate="Structured data" mwfollow mwfields="Hello" mwslot="mds-metadataslot" />
<_create mwwrite="::id::testingSlot" mwtemplate="wsnone" mwfields="Hello2" mwslot="mds-metadataslot2" />
</syntaxhighlight>

Example 5 : Use '''wsnone''' and '''[https://www.mediawiki.org/wiki/Help:Substitution substitution] ''' to copy content of an existing page onto a new page. This example copies the content of "Main Page" when creating a new page named "Test new page".
<syntaxhighlight lang="html">
<form>
<_create mwwrite="Test new page" mwtemplate="wsnone" mwfields="Content" />
<textarea name="Content">{{subst::Main Page}}</textarea>
<input type="submit" />
</form>
</syntaxhighlight>

===Note===
If you create a page from text, mwrandom and field values and also add mwoption="add_random", another random number will be added to the end of the page title.

You can have multiple instances of _create in a form, as long as mwfields is a non empty argument with every _create.
If you have multiple _create and they all have a mwfollow, the last _create in the list will be followed.
===Links===
https://www.mediawiki.org/wiki/Multi-Content_Revisions

{{FlexForm/Create and edit comparison}}

DevOps:Doc/FlexForm/1.1/token

2025-01-21T14:35:03Z

944f869b-8467-464e-95c7-903362952755:

===Name===
_token
===Type===
_token
===Synopsis===
Token input field
===Description===
Use of select2 tokens
===Parameters===
'''_token'''

'''name''' = e.g. tokenfield[]

'''separator''' = token values have by default comma separated values when adding to a Template. You can specify a different separator using this argument . e.g. separator=";".

'''allowtags''' = allow user to add custom values that are not suggested through autocompletion or otherwise. As of version 2.2.19, use a value of 'allowtags'; prior to that, just give the attribute name, without any value.

'''allowsort''' = (no value or (as of version 2.2.19 ->) value of 'allowsort') Allow user to sort values (drag and drop selected token). '''Does not work with query source.'''

'''allowclear''' = (no value or (as of version 2.2.19 ->) value of 'allowclear') allow user to clear his selection. Will only work when you have set a placeholder.

'''input-length-trigger''' = integer number of characters before lookup actually happens, defaults to 3

'''id''' = '''''mandatory'''''

'''query''' = If you have [https://www.semantic-mediawiki.org Semantic MediaWiki] installed, you can do a SMW Ask query here to fill the options list.
* '''returntext''' lets you set a property for the visible label of the token
* '''returnid''' (optional) lets you set a property for the value to be stored. This defaults to the page name.
* '''limit''' (optional) lets you sets the maximum number of pages to be returned by the query
* '''fquery''' (optional) lets you set a SMW Filter query that will be added to the query. Additional you can use [fffield='<name of a form field>'] inside the fquery to dynamically add a value of a form field in the filter query.

'''callback''' = templateCallBack

'''multiple''' = multiple

===Example===
Example 1 : Search for pages in the Doc page types.
<syntaxhighlight lang="html">
<form>
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear="allowclear">
</_token>
</form>
</syntaxhighlight>

<_form restrictions="lifted" action="get">
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear="allowclear">
</_token>
</_form>

Example 2 : Select one or more cars or create a new one
<syntaxhighlight lang="html">
<form>
<_token name="car[]" id="test-tokens-multiple" multiple="multiple" allowtags="allowtags">
<option value="volvo">Volvo</option>
<option value="saab" selected="selected">Saab</option>
<option value="tesla" selected="selected">Tesla</option>
</_token>
</form>
</syntaxhighlight>
<form restrictions="lifted" >
<_token name="car[]" id="test-tokens-multiple" multiple="multiple" allowtags="allowtags">
<option value="volvo">Volvo</option>
<option value="saab" selected="selected">Saab</option>
<option value="tesla" selected="selected">Tesla</option>
</_token>
</form>

Example 3 : using the '''selected''' and '''options''' attributes
<syntaxhighlight lang="html">
<form>
<_token name="TestSelected[]" id="test-tokens-selected" selected="C" options="A,B,C,D,E" />
</form>
</syntaxhighlight>
<form restrictions="lifted">
<_token name="TestSelected[]" id="test-tokens-selected" selected="C" options="A,B,C,D,E" />
</form>

Example 4 : using fquery
<pre>
<form>
<select name="Version" >
<option value="+">Any version</option>
<option value="1.0">1.0</option>
<option value="1.1">1.1</option>
<option value="2.0">2.0</option>
<option value="2.1">2.1</option>
</select>
<_token name="Doc page" id="tokens-with-fquery" query="[[Class::Doc]][[Doc subject::DevOps:Doc/FlexForm]][[Title::!!!]](limit=99999)(returntext=Title)(fquery=[[Subject version::[fffield=Version] ]])" input-length-trigger="1" placeholder="Search for Documentation Titles" multiple="multiple" allowclear="allowclear">
</_token>
</form>
</pre>
<form restrictions="lifted">
<select name="Version" >
<option value="+">Any version</option>
<option value="1.0">1.0</option>
<option value="1.1">1.1</option>
<option value="2.0">2.0</option>
<option value="2.1">2.1</option>
</select>
<_token name="Doc page" id="tokens-with-fquery" query="[[Class::Doc]][[Doc subject::DevOps:Doc/FlexForm]][[Title::!!!]](limit=99999)(returntext=Title)(fquery=[[Subject version::[fffield=Version] ]])" input-length-trigger="1" placeholder="Search for Documentation Titles" multiple="multiple" allowclear="allowclear">
</_token>
</form>

===Note===
In an SMW query, the '''!!!''' will be replaced with whatever the user types.

===Links===

Template:FlexForm/Create and edit comparison

2025-01-05T11:28:33Z

944f869b-8467-464e-95c7-903362952755:

<div class="card" style="background-color:#eaedf1;"><div class="card-body">The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slightly. By presenting these attributes side by side, the following table may help you on your way more quickly.

{| class="table"
|-
! _create
! _edit
! comments
|-
| Can be used to create new pages<br>Can be used to edit existing pages<br>Cannot be used to edit a selection of fields on a page
| Cannot be used to create new pages<br>Can be used to edit existing pages,<br>including select fields
|
|-
| <code>mwwrite</code><br>page title, optionally a formula in conjunction with <code>mwoption</code> or <code>mwleadingzero</code>
| <code>target</code><br>page id or page title
|-
| specific to page creation:
* <code>mwleadingzero</code>
* <code>mwoption</code>
* <code>noseo</code>
* <code>nooverwrite</code>
| <span style="color:red;">x</span>
|
|-
| <code>mwfollow</code>
| <span style="color:red;">x</span>
| If you know the name of the target page in advance, you can always set <code>mwreturn</code> in the <code>form</code> tag instead. <code>mwfollow</code> was specifically created for use cases where the title of the page to be created cannot be predicted.
|-
| <code>mwfields</code><br>allows for multiple fields (comma-separated)
| <code>formfield</code><br>allows for single fields only
|
|-
| <span style="color:red;">x</span>
| <code>usefield</code>
|
|-
| <code>mwslot</code>
| <code>mwslot</code>
|-
| <code>mwformat</code>
| <code>format</code>
| wiki or json
|-
| <code>mwtemplate</code>
| <code>template</code>
| template name or JSON configuration
|-
| <span style="color:red;">x</span>
| <code>value</code>
| can be used to set the value explicitly, without reading it from a form field.
|}
</div></div>

DevOps:Doc/FlexForm/1.0/edit

2025-01-05T11:24:52Z

944f869b-8467-464e-95c7-903362952755: add a table of comparison

===Name===
_edit
===Type===
_edit
===Synopsis===
Using a form to edit pages that have content with templates.
===Description===
How to edit pages in the wiki with FlexForm
===Parameters===
'''_edit'''

'''target''' = Target page ( title or page id ) that needs to be edited

'''template ''' = Name of the template on the target page that needs to be edited. If there are multiple instances of the same template, you can specify what instance FlexForm should use if you have a unique key and value in the specific instance. You define it by '''template="<name of template>|<name of argument>=<value of argument>"'''. E.g. '''template="Edit user|User id=55"'''

'''formfield''' = Name of the field in the template. Field in the form should have the same name

'''usefield''' = [optional] If the field in the form differs from the template variable name, you can use "usefield" to let _edit know what other field from the form it should use

'''value''' = [optional] Don't read the value from the form field, but use this value explicitly

'''mwslot''' = [optional] Name of content slot to use

===Example===
<syntaxhighlight lang="html">
<_edit target="pageid" template="template" formfield="formfield" />
</syntaxhighlight>

Simple test with a complete form you can use to see if editing works: Copy the following code snippet to the source code of a page and save. You will see a text field that will edit the "Content" parameter within the "Test" template call. Note that Template:Test does not need to exist for this example to work.
<syntaxhighlight lang="html">
{{Test
|Content=abc
}}

<form>
<_edit target="{{PAGEID}}" template="Test" formfield="Content" />
<input type="text" name="Content" />
<input type="submit"/>
</form>
</syntaxhighlight>

===Note===

* You can have multiple _edit's in a form all doing different tasks.
* If you have more than 5 edits to one single page in the wiki, consider [[DevOps:Doc/FlexForm/1.0/create]] to speed-up the process.
* If you omit value, then the value of the form will be used (so what a user has filled in).
===Links===
https://www.mediawiki.org/wiki/Multi-Content_Revisions

{{FlexForm/Create and edit comparison}}

DevOps:Doc/FlexForm/2.0/create

2025-01-05T11:24:02Z

944f869b-8467-464e-95c7-903362952755: add a table of comparison

===Name===
_create
===Type===
_create
===Synopsis===
Using a form to create new pages or overwrite existing pages
===Description===
_create can be defined as part of a form to have new page(s) created on form submit or overwrite (an) existing page(s).
===Parameters===
'''_create'''

'''mwtemplate''' = Name of a template to use as content for the new page. If you have a form with only one input element you can also use mwtemplate="wsnone". This will take the content of the form input element and make it the source content of the new page (without putting it inside a template).

'''mwwrite''' = Full name of the target page

'''mwfollow''' = Will send the user to the newly create page after form submission

'''mwoption''' can hold three different values:

* "'''add_random'''" = Create random numbers
* "'''next_available'''" = Get the next available number. If mwwrite is : "orders/", this option will find the highest orders number (e.g. orders/192) and will create a page with one number higher (e.g. orders/193)
* "'''range:'''" = Get the next available free slot in a range of numbers. If mwwrite is : "orders/", this option will find the first free spot in a range of numbers. If mwoption="range:2019000-2019999" and mwwrite="orders/" then FlexForm will start looking for a page called orders/2019000. If exists it will look for orders/2019001 etc.. till the first free page is found.

'''mwleadingzero''' can be used in combination with range. When a range is set like 1-99999 using mwleadingzero will use the length of the end range and use it to fill the start range with leading zeros, making the range from 00001-99999.

'''mwfields''' = comma separated names of form elements that need to be included. Only works when using multiple _create.

If you are creating multiple pages and want to re-assign form fields to template variables, you still add the form field name to mwfields, but add "'''::'''" and then the name of the template variable. So if you want to tell mwfields to use formfield "'''name2'''", but add it to the template as "'''Name'''", add : "'''name2::Name'''" to mwfields.

'''mwslot''' = name of a specific content slot to use.

'''nooverwrite''' = when this is set, no create will be done for a page that already exists. Even if you are creating a new slot for a page that already exist.

'''noseo''' = when this is set, even if the setting '''create-seo-titles''' in your local settings is set to '''true''' to always create SEO friendly page titles, it will not make the title of a new page SEO friendly, but use the title given.

'''mwformat''' = defaults to wiki. Currently only supports wiki or json. When set to json, the page content of the page will become a json. When used with mwtemplate, then the template name will be the key for the json. All form values will be stored as strings. Every new array with key names will automatically get a ffID value that will always be unique. This is done for easy editing later.

There are several ways for creating a page with FlexForm.

# Easiest Use mwtemplate and mwwrite as described above (and optionally wsfollow, wsoption, etc) This will use the values of mwtemplate and mwwrite and any form elements the current for has and create a new page with template "mwtemplate" and title of "mwwrite". See example 1.
# More advanced and possibilities Use mwtemplate and mwwrite with more options than described above (and optionally wsfollow, wsoption, etc) mwwrite can use can use other elements in the form and use those values to create a title for a new page. Field names can be added using square brackets. So if a form also has a text input field of "title" mwwrite could be "[title]". [mwrandom] can also be used e.g. mwwrite="[title]/[mwrandom]". See example 2.
# Create multiple pages with one form and control what form elements are used. This is where mwfields comes in. This is a comma separated list of form elements that will be used to create the new page. If a form has 15 text input fields, then using _create will include all 15 (filled-in by user) elements in the new page. Using mwfields you can tell _create specifically what form element to use to create a new page. So, when creating multiple new pages with one form, mwfields should be used with any and all _create. See example 3.
# Create a new page and fill different content slots for that page. You have to give the definition of the first _create an id. The other _create elements reference the first _create with a mwwrite like mwwrite="::id::<idOfWSCreateWithID>". See example 4.

===Example===
Example 1 : Create a new page with the next available number
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="next_available" />
</syntaxhighlight>
Create a new page with the next available number in a range and always start from the beginning
<syntaxhighlight lang="html">
<_create mwwrite="orders/" mwtemplate="Order" mwoption="range:2019000-2019999" />
</syntaxhighlight>
Random number
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:" mwoption="add_random" mwtemplate="Solution" />
</syntaxhighlight>

Example 2 : Create from text, mwrandom and fieldvalues
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/[mwrandom]" mwtemplate="Solution" />
</syntaxhighlight>

Example 3 : Create from text and field values and only include specific form element names in the new template
<syntaxhighlight lang="html">
<_create mwwrite="Proj-solution:[namefield]/Personal" mwtemplate="Personal" mwfields="naam, adres, straat, plaats" />
<_create mwwrite="Proj-solution:[namefield]/Business" mwtemplate="Business" mwfields="Company, cadres, cstraat, cplaats" />
</syntaxhighlight>

Example 4 : Create a page with title : Test/[title]. With no main content and a template of Structured data with an argument of Hello in slot:mds-metadataslot". At the same time content slot "mds-metadataslot2" get the same template with argument Hello2.
<syntaxhighlight lang="html">
<_create id="testingSlot" mwwrite="Test/[title]" mwtemplate="Structured data" mwfollow mwfields="Hello" mwslot="mds-metadataslot" />
<_create mwwrite="::id::testingSlot" mwtemplate="wsnone" mwfields="Hello2" mwslot="mds-metadataslot2" />
</syntaxhighlight>

Example 5 : Use '''wsnone''' and '''[https://www.mediawiki.org/wiki/Help:Substitution substitution] ''' to copy content of an existing page onto a new page. This example copies the content of "Main Page" when creating a new page named "Test new page".
<syntaxhighlight lang="html">
<form>
<_create mwwrite="Test new page" mwtemplate="wsnone" mwfields="Content" />
<input type="textarea" name="Content">{{subst::Main Page}}</input>
<input type="submit" />
</form>
</syntaxhighlight>

===Note===
If you create a page from text, mwrandom and field values and also add mwoption="add_random", another random number will be added to the end of the page title.

You can have multiple instances of _create in a form, as long as mwfields is a non empty argument with every _create.
If you have multiple _create and they all have a mwfollow, the last _create in the list will be followed.
===Links===
https://www.mediawiki.org/wiki/Multi-Content_Revisions

{{FlexForm/Create and edit comparison}}

Template:FlexForm/Create and edit comparison

2025-01-05T11:21:30Z

944f869b-8467-464e-95c7-903362952755:

<div class="card" style="background-color:#eaedf1;"><div class="card-body">The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slightly. By presenting these attributes side by side, the following table may help you on your way more quickly.

{| class="table"
|-
! _create
! _edit
! comments
|-
| Can be used to create new pages<br>Can be used to edit existing pages<br>Cannot be used to edit a selection of fields on a page
| Cannot be used to create new pages<br>Can be used to edit existing pages,<br>including select fields
|
|-
| <code>mwwrite</code><br>page title, optionally in conjunction with <code>mwoption</code> or <code>mwleadingzero</code>
| <code>target</code><br>page id or page title
|-
| specific to page creation:
* <code>mwleadingzero</code>
* <code>mwoption</code>
* <code>noseo</code>
* <code>nooverwrite</code>
| <span style="color:red;">x</span>
|
|-
| <code>mwfollow</code>
| <span style="color:red;">x</span>
| If you know the name of the target page in advance, you can always set <code>mwreturn</code> in the <code>form</code> tag instead. <code>mwfollow</code> was specifically created for use cases where the title of the page to be created cannot be predicted.
|-
| <code>mwfields</code><br>allows for multiple fields (comma-separated)
| <code>formfield</code><br>allows for single fields only
|
|-
| <span style="color:red;">x</span>
| <code>usefield</code>
|
|-
| <code>mwslot</code>
| <code>mwslot</code>
|-
| <code>mwformat</code>
| <code>format</code>
| wiki or json
|-
| <code>mwtemplate</code>
| <code>template</code>
| template name or JSON configuration
|-
| <span style="color:red;">x</span>
| <code>value</code>
| can be used to set the value explicitly, without reading it from a form field.
|}
</div></div>

Template:FlexForm/Create and edit comparison

2025-01-05T11:18:46Z

944f869b-8467-464e-95c7-903362952755:

<div class="card" style="background-color:var(--light);"><div class="card-body">The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slightly. By presenting these attributes side by side, the following table may help you on your way more quickly.

{| class="table"
|-
! _create
! _edit
! comments
|-
| Can be used to create new pages<br>Can be used to edit existing pages<br>Cannot be used to edit a selection of fields on a page
| Cannot be used to create new pages<br>Can be used to edit existing pages,<br>including select fields
|
|-
| <code>mwwrite</code><br>page title, optionally in conjunction with <code>mwoption</code> or <code>mwleadingzero</code>
| <code>target</code><br>page id or page title
|-
| specific to page creation:
* <code>mwleadingzero</code>
* <code>mwoption</code>
* <code>noseo</code>
* <code>nooverwrite</code>
| <span style="color:red;">x</span>
|
|-
| <code>mwfollow</code>
| <span style="color:red;">x</span>
| If you know the name of the target page in advance, you can always set <code>mwreturn</code> in the <code>form</code> tag instead. <code>mwfollow</code> was specifically created for use cases where the title of the page to be created cannot be predicted.
|-
| <code>mwfields</code><br>allows for multiple fields (comma-separated)
| <code>formfield</code><br>allows for single fields only
|
|-
| <span style="color:red;">x</span>
| <code>usefield</code>
|
|-
| <code>mwslot</code>
| <code>mwslot</code>
|-
| <code>mwformat</code>
| <code>format</code>
| wiki or json
|-
| <code>mwtemplate</code>
| <code>template</code>
| template name or JSON configuration
|-
| <span style="color:red;">x</span>
| <code>value</code>
| can be used to set the value explicitly, without reading it from a form field.
|}
</div></div>

Template:FlexForm/Create and edit comparison

2025-01-05T11:15:59Z

944f869b-8467-464e-95c7-903362952755:

The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slightly. By presenting these attributes side by side, this table may help you on your way more quickly.

{| class="wikitable"
|-
! _create
! _edit
! comments
|-
| Can be used to create new pages<br>Can be used to edit existing pages<br>Cannot be used to edit a selection of fields on a page
| Cannot be used to create new pages<br>Can be used to edit existing pages,<br>including select fields
|
|-
| <code>mwwrite</code><br>page title, optionally in conjunction with <code>mwoption</code> or <code>mwleadingzero</code>
| <code>target</code><br>page id or page title
|-
| specific to page creation:
* <code>mwleadingzero</code>
* <code>mwoption</code>
* <code>noseo</code>
* <code>nooverwrite</code>
| <span style="color:red;">x</span>
|
|-
| <code>mwfollow</code>
| <span style="color:red;">x</span>
| If you know the name of the target page in advance, you can always set <code>mwreturn</code> in the <code>form</code> tag instead. <code>mwfollow</code> was specifically created for use cases where the title of the page to be created cannot be predicted.
|-
| <code>mwfields</code><br>allows for multiple fields (comma-separated)
| <code>formfield</code><br>allows for single fields only
|
|-
| <span style="color:red;">x</span>
| <code>usefield</code>
|
|-
| <code>mwslot</code>
| <code>mwslot</code>
|-
| <code>mwformat</code>
| <code>format</code>
| wiki or json
|-
| <code>mwtemplate</code>
| <code>template</code>
| template name or JSON configuration
|-
| <span style="color:red;">x</span>
| <code>value</code>
| can be used to set the value explicitly, without reading it from a form field.
|}

Template:FlexForm/Create and edit comparison

2025-01-05T11:08:33Z

944f869b-8467-464e-95c7-903362952755: Created page with "The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slig..."

The <code>_create</code> and <code>_edit</code> tags share a lot of functionality but they do not always share the same attribute names or their intended usage may differ slightly. By presenting these attributes side by side, this table may help you on your way more quickly.

{| class="wikitable"
|-
! _create
! _edit
! comments
|-
| Can be used to create new pages<br>Can be used to edit existing pages<br>Cannot be used to edit a selection of fields on a page
| Cannot be used to create new pages<br>Can be used to edit existing pages,<br>including select fields
|
|-
| <code>mwwrite</code><br>page title, optionally in conjunction with <code>mwoption</code> or <code>mwleadingzero</code>
| <code>target</code><br>page id or page title
|-
| specific to page creation:
* <code>mwleadingzero</code>
* <code>mwoption</code>
* <code>noseo</code>
* <code>nooverwrite</code>
| <span style="color:red;">x</span>
|
|-
| <code>mwfollow</code>
| <span style="color:red;">x</span>, but you can set <code>mwreturn</code> in the <code>form</code> tag
|
|-
| <code>mwfields</code><br>allows for multiple fields (comma-separated)
| <code>formfield</code><br>allows for single fields only
|
|-
| <span style="color:red;">x</span>
| <code>usefield</code>
|
|-
| <code>mwslot</code>
| <code>mwslot</code>
|-
| <code>mwformat</code>
| <code>format</code>
| wiki or json
|-
| <code>mwtemplate</code>
| <code>template</code>
| template name or JSON configuration
|-
| <span style="color:red;">x</span>
| <code>value</code>
| can be used to set the value explicitly, without reading it from a form field.
|}

DevOps:Doc/FlexForm/2.0/edit/json

2024-12-30T13:49:47Z

944f869b-8467-464e-95c7-903362952755: corrected mwformat --> format; made clear that template is mandatory

===Name===
_edit JSON content
===Type===
_edit
===Synopsis===
Using a form to edit pages that have content with JSON.
===Description===
How to edit JSON content pages in the wiki with FlexForm.

The edit function is very similar to editing template content, we will brake down the differences here.

===Parameters===
'''_edit'''

'''target''' = Target page ( title or page id ) that needs to be edited

'''format''' = "json". Tell an edit that we are working with JSON

'''template ''' = Mandatory if format=json. This argument has been kept to keep editing a template wiki page and editing a JSON page similar to each other.
Name of the template differs from editing template content and now has two options : json and jsonk.

*'''json''' : When you create a JSON page with _create, every new named array will also get a unique id, called '''ffID'''. The following example tells FlexForm to find a certain ffID and then find a named value ( so the key ) called Title. FlexForm will then check if the submitted form has an input with the same name the "Title" and use it's value to add to the JSON.

Example JSON:
<syntaxhighlight lang="php">
{
"Coats": {
"ffID": 1669192355,
"Title": "The Body protector",
"Type": "Bodywarmer",
"Color": [
"blue",
"pink"
]
}
}
</syntaxhighlight>
Example EDIT:
<syntaxhighlight lang="php">
<_edit target="Json_test_result" format="json" template="json|ffID=1669192355" formfield="Title" />
</syntaxhighlight>
If you do not have a ffID, but do have something else in the JSON that is always unique you can use those instead of a ffID. For example, if you know the '''Type:"Bodywamer"''' is unique in this JSON, you can edit the '''Title''' of the JSON this way :
<syntaxhighlight lang="php">
<_edit target="Json_test_result" format="json" template="json|Type=Bodywarmer" formfield="Title" />
</syntaxhighlight>

*'''jsonk''' : This option lets you traverse down a JSON manually using the JSONPath (xpath for JSON). You tell FlexForm exactly what part of the JSON you want to edit and what value of a form input field to use. You can use the full root path method ( $. ) or leave it out for convenience and FlexForm will add it automatically. The following example uses the same JSON example from above and we tell FlexForm to go to '''Coats->Title''', then take the form input of type '''Title''' and put that value in the JSON.
<syntaxhighlight lang="php">
<_edit target="Json_test_result" format="json" template="jsonk|Coats.Title" formfield="Title" />
</syntaxhighlight>
You can also use a different input in your form to use as the new value
<syntaxhighlight lang="php">
<_edit target="Json_test_result" format="json" template="jsonk|Coats.Title" formfield="Alternative title" />
</syntaxhighlight>
You can even traverse into unnamed values like so :
<syntaxhighlight lang="php">
<_edit target="Json_test_result" format="json" template="jsonk|Coats.Color[0]" formfield="Title" />
</syntaxhighlight>
This will change the first Color array value into the value of the form field Title.

'''formfield''' = Name of the key in the JSON. When using template type json, then the formfield in the form should have the same name

'''value''' = [optional] Don't read the value from the form field, but use this value explicitly

'''mwslot''' = [optional] Name of content slot to use. Defaults to main content slot

===Note===

* You can have multiple _edit's in a form all doing different tasks.
* If you omit value, then the value of the form will be used (so what a user has filled in).
===Links===
https://www.mediawiki.org/wiki/Multi-Content_Revisions

https://github.com/Galbar/JsonPath-PHP

DevOps:Doc/FlexForm/2.1/input/file

2024-11-20T12:28:26Z

944f869b-8467-464e-95c7-903362952755:

===Name===
file
===Type===
input
===Synopsis===
Using file uploads
===Description===
Use a form to upload one or multiple files.
===Parameters===
input type="file"

'''target'''* : Name of the File page to be created

'''id'''* : This must always be unique, that is, it can only occur once on a page. Do not include a hyphen ("-"), underscore ("_"), or any special characters (also no spaces).

'''action'''* : defaults to '''upload'''. Read more below on using this to convert docx documents to pages in the wiki.

'''name'''* : As with any input field, a name is mandatory

'''pagecontent''': Text content to be added on the File Page. If you are using '''convertfrom''' then any images uploading during the convert will get the pagecontent.

'''comment''': Text to show in recent changes or contributions list

'''force ''': Force images to a certain format (png, jpg or gif). When using this option, any file uploaded that is not supported will be uploaded as is.

'''error_id ''': Id of a DOM Element where error notices will be shown

'''verbose_id ''': Id of a DOM element where information about the file is shown

'''use_label ''': Doesn't require a value. When an input field has a label attached to it, then the label will become the upload button and the input field will be hidden

'''dropzone ''': Doesn't require a value. Will turn the verbose div into an additional file drop zone. If you also '''use_label''', then the label will become the dropzone.

'''parsecontent''': Will force FlexForm to insert values from other form fields inside the pagecontent field. Use square brackets, like [fieldname], where values should be inserted.

'''template''' : If you want to store a template call inside the content of the File page, you can '''template=<name of your template>''' in combination with '''parsecontent'''. [flexform-template] inside your content field will be replaced by '''{{<name of your template''' and '''[/flexform-template]''' will be replaced by '''}}'''. See example 3 on the examples page.

'''*'''= a required variable

The '''target''' is basically the name you want to use to store the file or files. It recognizes '''[mwrandom]''', '''[filename]''' and other form fields, by using their name with square brackets around them (see example). '''pagecontent''' can also hold form variables.

=== action="convertfrom:????" ===
====Pandoc====
The '''action''' argument defaults to ''upload''. If you use '''action="convertfrom:????"''' and you have Pandoc installed on your system, FlexForm will convert a document and create it as a page in the Wiki. '''target''' will then be used as a Page Title. Depending on your version of Pandoc, the results might differ. '''convertfrom''' allows all Pandoc to MediaWiki text conversions. '''docx''' would be a good example : action="convertfrom:docx". Any images uploaded during the convert can have their content of their filepages be filled using '''pagecontent'''. Since version 2.2.9 you can also add an argument '''slot="<name of slot>"''' to have the converted Document be save to a specific slot on the target page, instead of the main slot. Keep in mind, MediaWiki slots need to be defined in your LocalSettings.
====Excel ( since version 2.2.9 )====
You can also use '''action="convertfrom:xls"''' or '''action="convertfrom:xlsx"'''. This allows for converting an Excel xls or xlsx file to JSON. Images are not supported. The argument '''slot''' is supported. ''This conversion is not done using Pandoc and thus will work without having Pandoc installed''. (just make sure you run composer update after you update FlexForm).

An excel document like this :
{| class="wikitable"
|'''options'''
|'''description'''
|'''HitCounter'''
|'''WSStats'''
|'''More'''
|-
|$wgDisableCounters
|automatically show hitcounts on a page and Special page
|yes
|no
|WSStats allows for adding this to a page using parser function
|-
|$wgHitcounterUpdateFreq
|frequency of counters update
|yes
|no
|WSStats uses MW DB abstraction layer to update hitcount. The approach is different
|-
|skip_user_groups
|Skip certain user groups in counting
|no
|yes
|
|-
|count_all_usergroups
|Count pages independend of a user group
|no
|yes
|
|}
Will result in the following JSON:
<syntaxhighlight lang="json">
[
{
"options": "$wgDisableCounters",
"description": "automatically show hitcounts on a page and Special page",
"HitCounter": "yes",
"WSStats": "no",
"More": "WSStats allows for adding this to a page using parser function"
},
{
"options": "$wgHitcounterUpdateFreq",
"description": "frequency of counters update",
"HitCounter": "yes",
"WSStats": "no",
"More": "WSStats uses MW DB abstraction layer to update hitcount. The approach is different"
},
{
"options": "skip_user_groups",
"description": "Skip certain user groups in counting",
"HitCounter": "no",
"WSStats": "yes"
},
{
"options": "count_all_usergroups",
"description": "Count pages independend of a user group",
"HitCounter": "no",
"WSStats": "yes"
}
]
</syntaxhighlight>

===HTMLtoImage===
You can also use the field input to upload an image created from part of the page shown where the form is rendered.

Basically, you tell FlexForm you want to render a part of your screen as an image and upload it to the wiki.

The syntax is the same as above, but it only needs : target, name and pagecontent. The other arguments are ignored. Additionally it needs an argument called '''presentor="canvas"''' and it needs the ID of the element you want to convert to an image: '''canvas_source_id'''.

''By default the image will always be a .jpg file. We plan to support png if this is requested.''

For example you have a DIV element with id="content-to-convert". Within this DIV you have content you want to convert to an image an upload to the Wiki.

A FlexForm to utilize this would look something like this :
<syntaxhighlight lang="html">
<div id="content-to-convert" style="width:500px">
<h1>Test Screenshot</h1>
<p>Lots of other content here</p>
</div>

<form>
<input type="file" presentor="canvas" id="canvasUpload" target="testCanvasFile.jpg" pagecontent="testing" canvas_source_id="content-to-convert" />
<input type="submit" value="upload" />
</form>
</syntaxhighlight>

'''You cannot use both file uploads in one form.'''

===Note===
An '''input type="file"''' always needs a unique ID! ( do not use "-", "_", any special characters ( also no spaces ) ).

A form that needs to upload files needs this argument : '''enctype="multipart/form-data"'''. The argument needs to be added to the Form tag, not the input tag. See also : https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/enctype

As FlexForm first handles File Upload, it will add the files processed to use in an _edit or a _create.
Every file upload field needs a name attribute and once a file has been uploaded you can use them in an edit or create in the following format :

*'''FFUploadedFile-UploadName-'''''<name attribute of input field>'' : Will hold the original file name uploaded
*'''FFUploadedFile-UploadBase-'''''<name attribute of input field>'' : Will hold the original file name uploaded without the extension
*'''FFUploadedFile-NewName-'''''<name attribute of input field>'' : Will hold the name of the file as it is uploaded into the Wiki ( Without the File: prefix )

If you use a multiple file upload, then the above values will all be ''',''' separated.

===Links===
https://developer.mozilla.org/en-US/docs/Web/API/HTMLFormElement/enctype

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/file

https://pandoc.org/

DevOps:Doc/FlexForm/2.0/Installation of FlexForm

2024-11-08T10:32:45Z

944f869b-8467-464e-95c7-903362952755: /FlexForm not hyphenated /Flex-Form

FlexForm is installed using [https://www.mediawiki.org/wiki/Composer/For_extensions Composer]:

<syntaxhighlight lang="php">
composer require open-csp/flex-form
</syntaxhighlight>

You can install FlexForm from [https://github.com/Open-CSP/FlexForm github] by installing it in extensions/FlexForm. You do have to run composer --update inside that folder after installation to get all dependencies.

==== Setup ====
You can tweak '''FlexForm''' to an extent in your <code>LocalSettings.php</code> file:

<syntaxhighlight lang="php">
// Will render form that makes no sense when inspected in the browser.
$wgFlexFormConfig['secure'] = true;

// A salt key for encryption. Used together with "secure" option. Must be set when using multiple instances of a wiki.
$wgFlexFormConfig['sec_key'] = "";

// Interval time in ms, defaults to 3 minutes (180000 ms). Form is submitted on each interval regardless of changes.
$wgFlexFormConfig['auto_save_interval'] = 30000;

// Time in ms, defaults to 3 seconds (3000 ms). Form is submitted after the specified time, timer starts when there is a change in the form. Timer resets if there is another change before the time has passed.
$wgFlexFormConfig['auto_save_after_change'] = 3000;

// Text on the autosave button to toggle on.
$wgFlexFormConfig['auto_save_btn_on'] = 'Autosave on';

// Text on the autosave button to toggle off.
$wgFlexFormConfig['auto_save_btn_off'] = 'Autosave off';

// Currently the only form.
$wgFlexFormConfig['FlexFormDefaultTheme'] = "plain";

// reCaptcha site key.
$wgFlexFormConfig['rc_site_key'] = "";

// reCaptcha secret key.
$wgFlexFormConfig['rc_secret_key'] = "";

// Where to store images temporarily that need to be format converted.
$wgFlexFormConfig['file_temp_path'] = "";

// Defaults to false. Set to yes if FlexForm is allowed to create new users.
$wgFlexFormConfig['can_create_user'] = "";

// Defaults to false. Will filter all parser arguments to plain text, except value parameters. Will also disallow onClick and onFocus parameter. This feature will most likely be removed in future updates.
$wgFlexFormConfig['filter_input_tags'] = false;

// Defaults to what is described by the loadscript form argument. When you change it do a different folder, then loadScript argument will be looking in this folder for its JavaScript file to load with the Form.
$wgFlexFormConfig['loadScriptPath'] = "";

// Defaults to sysop. Only a user in the allowedGroups is able to edit pages with a FlexForm in the source.
$wgFlexFormConfig['allowedGroups'] = ["sysop","moderator"];

// Defaults to true. When a user in the allowedGroups creates a form it will become valid and will be rendered. Someone not in the allowedGroups can create a form and save it, but it will never be rendered until a user from the allowedGroups will edit and re-save the page. Only then will a form become valid. The message "FORM CANNOT BE RENDERED, NOT VALIDATED" will be shown instead of the form when it is invalid or depending on the next setting an image stating it cannot be rendered.
$wgFlexFormConfig['renderonlyapprovedforms'] = true;

// When a form is invalid, an invalid image will be rendered instead of the form. Set to true to render i18n invalid message.
$wgFlexFormConfig['renderi18nErrorInsteadofImageForApprovedForms'] = false;

// Defaults to false. This differs from FlexForm before 2.0. FlexForm will now honor the UserCan functions in MediaWiki. If a form edits or creates a page a user has no rights to, the form will fail.
$wgFlexFormConfig['userscaneditallpages'] = false;

// Defaults to true. If a user is not in the allowedGroups then hide edit and editsource menu items for any page containing a FlexForm form.
$wgFlexFormConfig['hideEdit'] = true;

// Defaults to false. Will turn titles given to wscreate into url friendly slugs. Creating only latin character and converting spaces and special characters.
$wgFlexFormConfig['create-seo-titles'] = true;

// If you have a custom/different version of Pandoc than the one set by your hosting provider, you can add its local path here and FlexForm will use it, instead of the one set by environment variables
$wgFlexFormConfig['pandoc-install-path'] = $IP . '/bin/pandoc'; // This will look for Pandoc executable in the root/bin of your MediaWiki instalment

// FlexForm will by default always do an extra null edit on a save or an edit. This is mainly due to SMW. Not always this is necessary, so with this option you can turn it off. ( resulting in less handling time )
$wgFlexFormConfig['forceNullEdit'] = true; // Default to true for backwards compatibility

// When sending email, should we use separate smtp?
$wgFlexFormConfig['use_smtp'] = false;

$wgFlexFormConfig['smtp_host'] = "";

$wgFlexFormConfig['smtp_authentication'] = true;

$wgFlexFormConfig['smtp_username'] = "";

$wgFlexFormConfig['smtp_password'] = "";

$wgFlexFormConfig['smtp_secure'] = "TLS";

$wgFlexFormConfig['smtp_port'] = "587";

</syntaxhighlight>

==== Installation ====
* Add the following line at the end of your <code>LocalSettings.php</code> to enable the extension:

<syntaxhighlight lang="php">
wfLoadExtension( 'FlexForm' );
</syntaxhighlight>

* It is also recommended to turn off the parser cache when using FlexForm:

<syntaxhighlight lang="php">
$wgParserCacheType = CACHE_NONE;
</syntaxhighlight>

* Run the [https://www.mediawiki.org/wiki/Manual:Update.php update script] which will automatically create the necessary database tables that this extension needs.
* Navigate to Special:Version on your wiki to verify that the extension is successfully installed.

==== Migrate from version 1.x to 2.0 ====
* Please notice the changes in the config settings.
* Do not forget to run update.php.
* Also, by default, the setting '''renderonlyapprovedforms''' will be '''true'''. Meaning that once you install FlexForm v2.0 all your existing FlexForm forms in your wiki will be shown as unvalidated. Visit [[DevOps:Doc/FlexForm/2.0/Validated Forms|Validated Forms]] to read how to solve this easily.

==== Notification/Messages ====
FlexForm has a notification system build in. This is used to show possible errors or success/custom messages.

'''As off version 2.2.2 this is now a default feature''' and <nowiki><form showmessage /></nowiki> is deprecated.

User:944f869b-8467-464e-95c7-903362952755/Test

2024-08-27T21:01:46Z

944f869b-8467-464e-95c7-903362952755:

Target: [[Json/RecipeTest]]

<form id="my-recipe-form--create" type="addToWiki" >
<_create id="create-page"
mwwrite="Json/RecipeTest"
mwtemplate="Base properties"
mwslot="ws-data"
mwfields="Class"
mwfollow="true" />

<_input type="hidden" name="Class" value="Test recipe" />

<_create id="sdfsdfsdfsdf"
mwwrite="::id::create-page"
mwformat="json"
mwtemplate="wsnone"
mwfields="title,ingredients"
/>

<div class="ff">
<label for="title">Title</label>
<input type="text" name="title" />
</div>

<_instance
name="ingredients"
format="json"
>
<div class="ff">
<label for="name">Name</label>
<input type="text" name="name" />
</div>
<div class="ff">
<label for="amount">Amount</label>
<input type="text" name="amount" />
</div>
<div class="ff">
<label for="unit">Unit</label>
<input type="text" name="unit" />
</div>
</_instance>

<input type="submit" value="Save" />

</form>

== Issue ==
;Fandata
Could not create a WikiPage Object from title ::id::..... Title is null.

;Here
No such slot: main

User:944f869b-8467-464e-95c7-903362952755/Test

2024-08-27T21:00:20Z

944f869b-8467-464e-95c7-903362952755:

Target: [[Json/RecipeTest]]

<form id="my-recipe-form--create" type="addToWiki" >
<_create id="create-page"
mwwrite="Json/RecipeTest"
mwtemplate="Base properties"
mwslot="ws-data"
mwfields="Class"
mwfollow="true" />
<_input type="hidden" name="Class" value="Test recipe" />
<_create id="sdfsdfsdfsdf"
mwwrite="::id::create-page"
mwformat="json"
mwtemplate="wsnone"
mwfields="title,ingredients"
/>

<div class="ff">
<label for="title">Title</label>
<input type="text" name="title" />
</div>

<_instance
name="ingredients"
format="json"
>
<div class="ff">
<label for="name">Name</label>
<input type="text" name="name" />
</div>
<div class="ff">
<label for="amount">Amount</label>
<input type="text" name="amount" />
</div>
<div class="ff">
<label for="unit">Unit</label>
<input type="text" name="unit" />
</div>
</_instance>

<input type="submit" value="Save" />

</form>

;Fandata
Could not create a WikiPage Object from title ::id::..... Title is null.

;Here
No such slot: main

User:944f869b-8467-464e-95c7-903362952755/Test

2024-08-27T20:58:37Z

944f869b-8467-464e-95c7-903362952755:

Target: [[Json:RecipeTest]]

<form id="my-recipe-form--create" type="addToWiki" >
<_create id="create-page"
mwwrite="Json:RecipeTest"
mwtemplate="Base properties"
mwslot="ws-data"
mwfields="Class"
mwfollow="true" />
<_input type="hidden" name="Class" value="Test recipe" />
<_create id="sdfsdfsdfsdf"
mwwrite="::id::create-page"
mwformat="json"
mwtemplate="wsnone"
mwfields="title,ingredients"
/>

<div class="ff">
<label for="title">Title</label>
<input type="text" name="title" />
</div>

<_instance
name="ingredients"
format="json"
>
<div class="ff">
<label for="name">Name</label>
<input type="text" name="name" />
</div>
<div class="ff">
<label for="amount">Amount</label>
<input type="text" name="amount" />
</div>
<div class="ff">
<label for="unit">Unit</label>
<input type="text" name="unit" />
</div>
</_instance>

<input type="submit" value="Save" />

</form>

;Fandata
Could not create a WikiPage Object from title ::id::..... Title is null.

;Here
No such slot: main

User:944f869b-8467-464e-95c7-903362952755/Test

2024-08-27T20:57:21Z

944f869b-8467-464e-95c7-903362952755: Created page with "Target: Json:RecipeTest <form id="my-recipe-form--create" type="addToWiki" > <_create id="create-page" mwwrite="Json:RecipeTest" mwtemplate="Base properties" mwslot="w..."

Target: [[Json:RecipeTest]]

<form id="my-recipe-form--create" type="addToWiki" >
<_create id="create-page"
mwwrite="Json:RecipeTest"
mwtemplate="Base properties"
mwslot="ws-data"
mwfields="Class"
mwfollow="true" />
<_input type="hidden" name="Class" value="Test recipe" />
<_create id="sdfsdfsdfsdf"
mwwrite="::id::create-page"
mwformat="json"
mwtemplate="wsnone"
mwfields="title,ingredients"
/>

<div class="ff">
<label for="title">Title</label>
<input type="text" name="title" />
</div>

<_instance
name="ingredients"
format="json"
>
<div class="ff">
<label for="name">Name</label>
<input type="text" name="name" />
</div>
<div class="ff">
<label for="amount">Amount</label>
<input type="text" name="amount" />
</div>
<div class="ff">
<label for="unit">Unit</label>
<input type="text" name="unit" />
</div>
</_instance>

<input type="submit" value="Save" />

</form>

Could not create a WikiPage Object from title ::id::..... Title is null.

DevOps:Doc/FlexForm/1.0/Error-messages

2024-06-11T11:47:16Z

944f869b-8467-464e-95c7-903362952755: /* Error messages in the browser's console */ h3

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|}

=== Error messages in the browser's console ===

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|-
| <code>SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line [...] column [...] of the JSON data</code> (FlexForm.general.js)
| This may happen if you have set your config options for debugging in such a way that any PHP warnings are printed, in turn mangling the JSON output expected by FlexForm. It is generally not a good idea to permanently use settings like <code>ini_set( 'display_errors', 1 ) </code> or <code>error_reporting( E_ALL )</code> in a live environment.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/1.0/Error-messages

2024-06-11T11:46:27Z

944f869b-8467-464e-95c7-903362952755: another one

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|}

== Error messages in the browser's console ==

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|-
| <code>SyntaxError: JSON.parse: unexpected non-whitespace character after JSON data at line [...] column [...] of the JSON data</code> (FlexForm.general.js)
| This may happen if you have set your config options for debugging in such a way that any PHP warnings are printed, in turn mangling the JSON output expected by FlexForm. It is generally not a good idea to permanently use settings like <code>ini_set( 'display_errors', 1 ) </code> or <code>error_reporting( E_ALL )</code> in a live environment.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/1.0/Error-messages

2024-06-09T19:05:58Z

944f869b-8467-464e-95c7-903362952755: /* Error messages in the browser's console */

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|}

== Error messages in the browser's console ==

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your LocalSettings.php file. Some features, such as instances, may not work without it.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/1.0/Error-messages

2024-06-09T19:01:15Z

944f869b-8467-464e-95c7-903362952755: add JavaScript errors

===Name===
Troubles and Error messages
===Type===
_form
===Synopsis===
Common behaviour and list of (error) messages that might occur
===Description===
Tag extensions, like FlexForm, cannot hold any html in its arguments.<syntaxhighlight lang="html">
<_input type="text" value="hello<br>how are you" />
</syntaxhighlight>The above example will simply not be rendered. This is how MediaWiki tags work.

You can use the following syntax, it at least will not break. It is another way of writing tag code.<syntaxhighlight lang="html">
{{#tag:_input||type=text|value=hello<br>how are you}}
</syntaxhighlight>The HTML will be filtered out. '''However, with the new Parsoid Parser that is introduced, do not use the <nowiki>{{#tag:}}</nowiki> method anymore.''' It will give unpredictable results as Parsoid renders these tags in no particular order.

Here's a list of common error messages that might occur, with a brief description of what the problem might be.
{| class="wikitable"
|+
!Message
!Type
!Why
!Possible solutions
|-
|Can not find template
|_email
|shown when the page mentioned in the template cannot be read or parse by the API
|check page name if it exists or not miss-spelled
|-
|not a secure form
|form
|shown when the sec option is set to true and the form has been manipulated after form submit
|
|-
|Secure fields not complete
|form
|shown when the sec option is set to true and files with type is secure (not to be manipulated with) are incomplete after a form submit
|
|-
|Did not receive a session token from the form
|form
|shown when a secure token that is generated by FlexForm did not come with a form submit
|
|-
|Form session expired
|form
|shown when the time between a form render and the actual submit has taken to long
|Change the config option '''form-timeout-limit''' to a higher number in seconds ( default 7200 secs = 120 mins = 2 hours )
|-
|No return found
|form
|shown when a form has been submitted but FlexForm cannot find a page to return to after handling the form
|
|-
|no captcha details
|reCaptcha
|shown when a form with a recaptcha has been submitted, but no recaptcha information can be found in the form
|
|-
|No requests
|form
|shown when a form has been submitted, but FlexForm could not find any valid request
|Usually this means the '''action''' parameter of a form is invalid.
|
|-
|Cannot find user to connect to file upload
|form
|
|-
|PHP move uploaded file error (file-handling)
|upload and canvas
|shown when a files or files are uploaded using FlexForm, but FlexForm cannot store them in the defined temp folder
|Make sure you set the FlexForm config : <code>$wgFlexFormConfig['file_temp_path'] = "";</code>
to a path where FlexForm has write rights. If you leave this empty, FlexForm will try to temporarily store the uploaded files in its own extension folder in the uploads folder. You can also check to see if this folder has write rights.
|}

== Error messages in the browser's console ==

{| class="table"
|-
| <code>Uncaught (in promise) ReferenceError: wgFlexFormSecure is not defined</code> (FlexForm.general.js)
| JavaScript error. This message may show if you forgot to set <code>$wgParserCacheType = CACHE_NONE;</code> in your settings. Some features, such as instances, may not work without this setting.
|-
| <code>Uncaught SyntaxError: redeclaration of let ffDecryptObj</code> (FlexForm.general.js)
| JavaScript error. Same as above.
|}

=== Discord ===
You might find a helping hand here as well : https://discord.gg/ehFrPmT

DevOps:Doc/FlexForm/2.0/input/signature

2023-12-08T13:55:51Z

944f869b-8467-464e-95c7-903362952755:

===Name===
signature
===Type===
input
===Synopsis===
How to render a signature field
===Description===
A signature field allows person to add a signature to a form.
===Parameters===
type="signature"

<nowiki>*</nowiki> = means required

'''name'''*

''type : text''

As with any input field, a name is mandatory

'''fname'''*

''type : text''

Name of the file to be placed in the Wiki

'''ftype'''*

''type : text''

Filetype. Either png, svg or jpg

'''pagecontent'''*

''type : text''

The (text-) content that goes on the page when saving to the wiki

'''parsecontent'''

''type : text''

''value : parsecontent''

Will force FlexForm to insert values from other form fields inside the pagecontent field. Use square brackets, like [fieldname], where values should be inserted.

'''template '''

''type : text''

If you want to store a template call inside the content of the File page, you can template=<name of your template> in combination with parsecontent. [flexform-template] inside your content field will be replaced by {{<name of your template and [/flexform-template] will be replaced by }}. See example 3 on the file/input examples page.

'''class'''

''type : text''

Adds an additional CSS class to the signature canvas.

By default the signature canvas will always get class: wsform-signature.

'''clearbuttonclass'''

''type : text''

Adds an additional CSS class to the clear button to clear the canvas.

By default the clear button will always get class: wsform-signature-clear.

'''clearbuttontext'''

''type : text''

Text to be placed in the clear button. Default to Clear.

'''background'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Background color for the signature field

'''drawcolor'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Color of the signature pen

'''thickness'''

''type : integer''

Thickness of the signature pen

'''notavailablemessage'''

''type : text''

When a browser does not support the signature canvas, this message will be displayed.

Default message : "Your browser doesn't support signing"

'''guideline'''

''type : text''

Show a horizontal line to guide when writing a signature.

Use guideline="true" is the only way to show the guideline.

Please note that the guideline will be saved together with the signature, unless you choose svg as file type.

Additional guideline option, available when guideline is set to true

- '''guidelineoffset'''

''type: integer''

Offset from the bottom of the canvas

- '''guidelineindent'''

''type: integer''

Margin left and right from the line to the side of the canvas

'''- guidelinecolor'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Color for the guideline

All other valid parameters for an input field are valid
===Example===
<syntaxhighlight lang="html">
<input type="signature" name="signature" fname="Signature-test" ftype="png" pagecontent="test" guideline="true" clearbuttonclass="btn btn-primary" />
</syntaxhighlight>
<input type="signature" name="signature" fname="Signature-test" ftype="png" pagecontent="test" guideline="true" clearbuttonclass="btn btn-primary" />

''Note that anonymous users may not see the signature field.''

===Note===
''Only one signature field per form is supported!''
===Links===

DevOps:Doc/FlexForm/2.0/input/signature

2023-12-08T13:48:43Z

944f869b-8467-464e-95c7-903362952755: /* Example */ add missing name parameter

===Name===
signature
===Type===
input
===Synopsis===
How to render a signature field
===Description===
A signature field allows person to add a signature to a form.
===Parameters===
type="signature"

<nowiki>*</nowiki> = means required

'''name'''*

''type : text''

As with any input field, a name is mandatory

'''fname'''*

''type : text''

Name of the file to be placed in the Wiki

'''ftype'''*

''type : text''

Filetype. Either png, svg or jpg

'''pagecontent'''*

''type : text''

The (text-) content that goes on the page when saving to the wiki

'''parsecontent'''

''type : text''

''value : parsecontent''

Will force FlexForm to insert values from other form fields inside the pagecontent field. Use square brackets, like [fieldname], where values should be inserted.

'''template '''

''type : text''

If you want to store a template call inside the content of the File page, you can template=<name of your template> in combination with parsecontent. [flexform-template] inside your content field will be replaced by {{<name of your template and [/flexform-template] will be replaced by }}. See example 3 on the file/input examples page.

'''class'''

''type : text''

Adds an additional CSS class to the signature canvas.

By default the signature canvas will always get class: wsform-signature.

'''clearbuttonclass'''

''type : text''

Adds an additional CSS class to the clear button to clear the canvas.

By default the clear button will always get class: wsform-signature-clear.

'''clearbuttontext'''

''type : text''

Text to be placed in the clear button. Default to Clear.

'''background'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Background color for the signature field

'''drawcolor'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Color of the signature pen

'''thickness'''

''type : integer''

Thickness of the signature pen

'''notavailablemessage'''

''type : text''

When a browser does not support the signature canvas, this message will be displayed.

Default message : "Your browser doesn't support signing"

'''guideline'''

''type : text''

Show a horizontal line to guide when writing a signature.

Use guideline="true" is the only way to show the guideline.

Please note that the guideline will be saved together with the signature, unless you choose svg as file type.

Additional guideline option, available when guideline is set to true

- '''guidelineoffset'''

''type: integer''

Offset from the bottom of the canvas

- '''guidelineindent'''

''type: integer''

Margin left and right from the line to the side of the canvas

'''- guidelinecolor'''

''type : color. Either hexadecimal, CSS color name or css rgb value''

Color for the guideline

All other valid parameters for an input field are valid
===Example===
<syntaxhighlight lang="html">
<input type="signature" name="signature" fname="Signature-test" ftype="png" pagecontent="test" guideline="true" clearbuttonclass="btn btn-primary" />
</syntaxhighlight>
<input type="signature" name="signature" fname="Signature-test" ftype="png" pagecontent="test" guideline="true" clearbuttonclass="btn btn-primary" />

===Note===
''Only one signature field per form is supported!''
===Links===

DevOps:Doc/FlexForm/2.0/input/number

2023-12-08T13:42:15Z

944f869b-8467-464e-95c7-903362952755: add restrictions="lifted" so anons can see the form

===Name===
number
===Type===
input
===Synopsis===
How to render a number only input field
===Description===
elements of type <code>'''"number"'''</code> are used to let the user enter a number. They include built-in validation to reject non-numerical entries. The browser may opt to provide stepper arrows to let the user increase and decrease the value using their mouse or by simply tapping with a fingertip.

By default, the up and down buttons provided for you to step the number up and down will step the value up and down by 1. You can change this by providing a <code>step</code> attribute, which takes as its value a number specifying the step amount.

You can use the <code>min</code> and <code>max</code> attributes to specify a minimum and maximum value that the field can have.

===Parameters===
input type="number"

As of version 1.1.37 there is an optional field you can use called '''calc'''. It allows you to do calculations with other input field of type="number".
The calc argument can hold a calculation and the other fields you want to use access them by there name field between square brackets. Like so : "5*[field1]+(20/[field2]".
See the second example. Currently for this to work, the number field with the calc argument must be in the same Form.

===Example===
This example accepts only a value between 0 and 10 with steps of 0.01 (e.g. 2.21)
<syntaxhighlight lang="html">
<input type="number" placeholder="1.0" step="0.01" min="0" max="10" />
</syntaxhighlight>
<input type="number" placeholder="1.0" step="0.01" min="0" max="10" />
<syntaxhighlight lang="html">
<form action="get">
field1: e.g. try 20 <input type="number" name="field1" /><br>
field2: e.g. try 5 <input type="number" name="field2" /><br>
Calculation( 5 * field1 / ( 20 + field2 ) ) would become '''5 X 20 / ( 20 + 5 )''' = 4<br> Result: <input type="number" name="total" calc="5*[field1]/(20+[field2])" />
</form>
</syntaxhighlight>
<form action="get" restrictions="lifted">
field1: e.g. try 20 <input type="number" name="field1" /><br>
field2: e.g. try 5 <input type="number" name="field2" /><br>
Calculation( 5 * field1 / ( 20 + field2 ) ) would become '''5 X 20 / ( 20 + 5 )''' = 4<br> Result: <input type="number" name="total" calc="5*[field1]/(20+[field2])" />
</form>
===Note===
If you are using the Calc function and you do not see any calculations, then you can have a look in the console of your browser. It will show you any mistakes you have made in the calculation.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/number

===PageSync===
If you have PageSync installed, you can install an example using Calc field with FlexForm.

'''Using Terminal'''

Go to the extensions/PageSync/maintenance folder

Type :
<syntaxhighlight>
php WSps.maintenance.php --user="You username" --install-shared-file="https://www.open-csp.org/docs/PageSync/FlexForm-examples/PageSync_09-10-2023-19-49-44_2-6-1.zip"
</syntaxhighlight>

'''Using PageSync 2.6 and above Special Page.'''

Use your browser and go to https://www.open-csp.org/docs/PageSync/FlexForm-examples/PageSync_09-10-2023-19-49-44_2-6-1.zip.
This will download the example file. Make sure you have set file upload in your wiki to allow .zip files. Upload the file.

Navigate to your wiki Special:PageSync Special page. Choose '''SHARE''', then at the bottom press the button '''INSTALL A SHARED FILE'''. The new page you get will have all your uploaded PageSync files at the top of the list. Choose the correct file and click on '''PREVIEW SHARED FILE''' to see all the details before you can actually install the example page.

DevOps:Doc/FlexForm/2.0/input/textarea

2023-09-22T08:22:55Z

944f869b-8467-464e-95c7-903362952755: /* Version note */

===Name===
textarea
===Type===
textarea
===Synopsis===
How to render a textarea input field
===Description===
textarea elements create larger text input fields that let the user enter a text.
It also differs from other input fields as there is no value you can set. Instead you use an opening input type and a closing one. The value will be in between. See example.
===Parameters===
<code><nowiki><textarea></textarea></nowiki></code>

For all supported argument have a look at the link at the links section.
===Example===
<syntaxhighlight lang="html">
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>
</syntaxhighlight>
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>

===Notes===
====VisualEditor====
If you have installed the [[mw:Extension:VisualEditor|VisualEditor]] and [[mw:Extension:VEForAll|VEForAll]] extensions, you can associate a textarea with the VisualEditor interface for rich text editing. To do so, just add <code>editor="ve"</code> to your textarea. You can have as many VE editors on a page as needed.

====Version note====
In earlier versions of FlexForm, you would use an <code>_input</code> with <code>type="textarea"</code>.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

DevOps:Doc/FlexForm/2.0/input/textarea

2023-09-22T08:22:22Z

944f869b-8467-464e-95c7-903362952755: /* Version note */

===Name===
textarea
===Type===
textarea
===Synopsis===
How to render a textarea input field
===Description===
textarea elements create larger text input fields that let the user enter a text.
It also differs from other input fields as there is no value you can set. Instead you use an opening input type and a closing one. The value will be in between. See example.
===Parameters===
<code><nowiki><textarea></textarea></nowiki></code>

For all supported argument have a look at the link at the links section.
===Example===
<syntaxhighlight lang="html">
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>
</syntaxhighlight>
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>

===Notes===
====VisualEditor====
If you have installed the [[mw:Extension:VisualEditor|VisualEditor]] and [[mw:Extension:VEForAll|VEForAll]] extensions, you can associate a textarea with the VisualEditor interface for rich text editing. To do so, just add <code>editor="ve"</code> to your textarea. You can have as many VE editors on a page as needed.

====Version note====
In earlier versions of FlexForm, you would use an <code>._input</code>. with <code>.type="textarea"</code>.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

DevOps:Doc/FlexForm/2.0/input/textarea

2023-09-22T08:21:03Z

944f869b-8467-464e-95c7-903362952755: /* VisualEditor */

===Name===
textarea
===Type===
textarea
===Synopsis===
How to render a textarea input field
===Description===
textarea elements create larger text input fields that let the user enter a text.
It also differs from other input fields as there is no value you can set. Instead you use an opening input type and a closing one. The value will be in between. See example.
===Parameters===
<code><nowiki><textarea></textarea></nowiki></code>

For all supported argument have a look at the link at the links section.
===Example===
<syntaxhighlight lang="html">
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>
</syntaxhighlight>
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>

===Notes===
====VisualEditor====
If you have installed the [[mw:Extension:VisualEditor|VisualEditor]] and [[mw:Extension:VEForAll|VEForAll]] extensions, you can associate a textarea with the VisualEditor interface for rich text editing. To do so, just add <code>editor="ve"</code> to your textarea. You can have as many VE editors on a page as needed.

====Version note====
In earlier versions of FlexForm, you would <code><_input type="textarea" /></code>.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

DevOps:Doc/FlexForm/2.0/input/textarea

2023-09-22T08:13:28Z

944f869b-8467-464e-95c7-903362952755: /* VisualEditor */

===Name===
textarea
===Type===
textarea
===Synopsis===
How to render a textarea input field
===Description===
textarea elements create larger text input fields that let the user enter a text.
It also differs from other input fields as there is no value you can set. Instead you use an opening input type and a closing one. The value will be in between. See example.
===Parameters===
<code><nowiki><textarea></textarea></nowiki></code>

For all supported argument have a look at the link at the links section.
===Example===
<syntaxhighlight lang="html">
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>
</syntaxhighlight>
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>

===Notes===
====VisualEditor====
If you have installed the [[mw:Extension:VisualEditor|VisualEditor]] and [[mw:Extension:VEForAll|VEForAll]] extensions, you can associate a textarea with the VisualEditor interface for rich text editing. To do so, just add <code>editor="ve"</code> to the <code>_input</code>. You can have as many VE editors on a page as needed.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

DevOps:Doc/FlexForm/2.0/input/textarea

2023-09-22T08:11:18Z

944f869b-8467-464e-95c7-903362952755:

===Name===
textarea
===Type===
textarea
===Synopsis===
How to render a textarea input field
===Description===
textarea elements create larger text input fields that let the user enter a text.
It also differs from other input fields as there is no value you can set. Instead you use an opening input type and a closing one. The value will be in between. See example.
===Parameters===
<code><nowiki><textarea></textarea></nowiki></code>

For all supported argument have a look at the link at the links section.
===Example===
<syntaxhighlight lang="html">
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>
</syntaxhighlight>
<textarea name="comment" placeholder="Type your comment" required="required">This is the text value</textarea>

===Notes===
====VisualEditor====
If you have installed the [[mw:Extension:VEForAll|VEForAll extension]], it lets you use a textarea with the VisualEditor interface for rich text editing. To associate a textarea with VisualEditor, add <code>editor="ve"</code>. You can have as many VE editors on a page as needed.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/textarea

User:Admin/Tests/Test1

2023-02-03T19:14:50Z

944f869b-8467-464e-95c7-903362952755:

==test 1==
Using the wiki tag version is used for _instance (#tag:_instance).
Target = [[User:Admin/Tests/2]]

<_form action="addToWiki" id="sdfsdfsdf2">
<_edit target="User:Admin/Tests/2" template="Log" formfield="Hours spent today" />

{{#tag:_instance
|<div class="">
Task:
<_input type="text" name="Task" placeholder="Task" />

Tokens:
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear></_token>
</div>
|template-parent=Log
|template=Hours spent
|name=Hours spent today
}}
<_input type="submit" class="btn btn-info" />
</_form>

User:Admin/Tests/Test1

2023-02-03T19:13:35Z

944f869b-8467-464e-95c7-903362952755:

==test 1==
Using the wiki tag version is used for _instance.
Target = [[User:Admin/Tests/2]]

<_form action="addToWiki" id="sdfsdfsdf2">
<_edit target="User:Admin/Tests/2" template="Log" formfield="Hours spent today" />

{{#tag:_instance
|<div class="">
Task:
<_input type="text" name="Task" placeholder="Task" />

Tokens:
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear></_token>
</div>
|template-parent=Log
|template=Hours spent
|name=Hours spent today
}}
<_input type="submit" class="btn btn-info" />
</_form>

User:Admin/Tests/Test1

2023-02-03T19:12:47Z

944f869b-8467-464e-95c7-903362952755:

==test 1==
Using the wiki tag version is used for _instance.
Target = [[{{FULLPAGENAME}}/2]]

<_form action="addToWiki" id="sdfsdfsdf2">
<_edit target="{{FULLPAGENAME}}/2" template="Log" formfield="Hours spent today" />

{{#tag:_instance
|<div class="">
Task:
<_input type="text" name="Task" placeholder="Task" />

Tokens:
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear></_token>
</div>
|template-parent=Log
|template=Hours spent
|name=Hours spent today
}}
<_input type="submit" class="btn btn-info" />
</_form>

User:Admin/Tests/Test1

2023-02-03T19:11:37Z

944f869b-8467-464e-95c7-903362952755:

==test 1==
Using the wiki tag version is used for _instance.

<_form action="addToWiki" id="sdfsdfsdf2">
<_edit target="{{FULLPAGENAME}}/2" template="Log" formfield="Hours spent today" />

{{#tag:_instance
|<div class="">
Task:
<_input type="text" name="Task" placeholder="Task" />

Tokens:
<_token name="tokenfield[]" id="tokener" query="[[Class::Doc]][[Title::!!!]](limit=99999)(returntext=Title)" placeholder="Search for Documentation Titles" multiple="multiple" allowclear>
</_token>
</div>
|template-parent=Log
|template=Hours spent
|name=Hours spent today
}}
<_input type="submit" class="btn btn-info" />
</_form>

DevOps:Doc/FlexForm/1.0/instance

2023-01-30T18:22:25Z

944f869b-8467-464e-95c7-903362952755: /* Example */ Again, without "restrictions=lifted" people won't be able to see this

===Name===
_instance
===Type===
_instance
===Synopsis===
Add or remove defined instances to a form
===Description===
With '''_instance''' you can define a part of a form as an instance that can be added or removed by the user (in a way add more rows to submit more information).

====== How it works ======
'''_instance''' holds a list of parameters that define the usage of the instance.

First you define what template on a page it needs to edit ('''template-parent''') and what parameter of that template needs to be edited ('''name''').

The idea is that the '''name''' attribute will hold multiple templates. That template is defined with the '''template''' parameter.

If you leave out anything else, FlexForm will render the instance based on the default Wikibase Solutions setup. (default settings listed with the parameters).

All the other parameters are described below.
===Parameters===
'''template-parent'''

Main template to edit on a page
<hr>
'''name'''

Name of the parameter to edit with the template-parent. Fields inside the instance cannot have the same name as this parameter.
<hr>
'''template'''

Name of the template to put inside parameter name.
<hr>
'''default-content'''

Allows to fill the instanced textarea with default content. Note: When a page contains text default content will always be overwritten.
<hr>
'''button-add'''

Main class for the button add instance. This is a class name that triggers the add instance.
default WSmultipleTemplateAddAbove
You can set this to none to not add this option at all
<hr>
'''button-add-extra'''

Extra class that can be added to the button for styling
default wsform-instance-add-btn
If you want no extra class then use button-add-extra="none"
<hr>
'''button-remove'''

Main class for the button remove instance. This is the class name that triggers the remove instance.

default '''WSmultipleTemplateDel'''

You can set this to none to not add this option at all
<hr>
'''button-remove-extra'''

Extra class that can be added to the button for styling

default '''wsform-instance-remove-btn'''

If you want no extra class then use button-remove-extra="none"
<hr>
'''button-move'''

Main class for the move instance button. This is the class name that trigger a move instance.

default '''ws-sortable-handles'''

You can set this to none to not add this option at all
<hr>
'''button-move-extra'''

Extra class that can be add to the button for styling

default '''wsform-instance-move-handle'''

If you want no extra class then use button-move-extra="none"
<hr>
'''add-button-on-bottom'''

Button below instance to add an add button. Value is text in the button

Use a value of "none" to disable this button

default '''empty'''
<hr>
'''button-on-bottom-class'''

Class for the button below the instance. Defaults to WSmultipleTemplateAddAbove
<hr>
'''wrapper-instance'''

div wrapper for the defined instance.

default '''WSmultipleTemplateMain'''
<hr>
'''wrapper-main'''

main div wrapper for all instances

default '''WSmultipleTemplateMain'''
<hr>
'''wrapper-main-extra'''

Extra class to add styling to the instances.

default '''wsform-instance-record'''
<hr>
'''instance-storage'''

class for the textarea to store instance information

default '''WSmultipleTemplateField'''
<hr>
'''instance-list'''

Class name for the wrapper for the list of instances

default '''WSmultipleTemplateList'''

===Example===
<syntaxhighlight lang="html">
<_form action="get" restrictions="lifted">
<_edit target="{{PAGEID}}" template="Log" formfield="Hours spent today" />
<_instance
template-parent="Log"
template="Hours spent"
name="Hours spent today"
>
<div class="test">
<_input type="text" name="Task" placeholder="Task" />
</div>
</_instance>
<_input type="submit" />
</_form>
</syntaxhighlight>
<_form action="get" restrictions="lifted" >

<_instance
template-parent="Log"
template="Hours spent"
name="Hours spent today"
>
<div class="test">
<_input type="text" name="Task" placeholder="Task" />
</div>
</_instance>

<_input type="submit" />
</_form>

'''Note:'''

'''Using instances default content together with Tokens and a SMW query'''

When using this combination, usually the value of a token has been saved and is put inside the default content. When rendering the instances, FlexForm will try to do a query to look-up the label that is attached to the value of the token.

Example : Say the Token-field is used to find certain pages with certain Semantic properties. In most cases the token visually shows the Display title of a query while the value of the token is the exact page Title and that is also the value that will be stored.

When rendering instances with previous saved page titles, FlexForm Tokens does not have the appropriate label to show for the token, in this case the Displaytitle. FlexForm will then analyze the SMW query attached to the token and try to get the SMW property as a label. In this case, the Displaytitle.

===Links===

Tutorial on Instances : https://wikibase-solutions.com/developer-logs/flexform-instances?WSLanguage=en

DevOps:Doc/FlexForm/1.0/input/date

2022-12-09T11:37:21Z

944f869b-8467-464e-95c7-903362952755: /* Note */

===Name===
date
===Type===
_input
===Synopsis===
How to render a date input field
===Description===
_input elements of type="date" create input fields that let the user enter a date, either with a textbox that validates the input or a special date picker interface.

The resulting value includes the year, month, and day, but not the time.

The date is formatted according to ISO8601, described in Format of a valid date string in Date and time formats used in HTML.
===Parameters===
type="date"

All other valid parameters for an input field are valid. Additionally you can use min, max and step.
===Example===
<syntaxhighlight lang="html">
<_input type="date" name="date" value="2022-03-01" min="2022-01-01" max="2022-12-31" />
</syntaxhighlight>
<_input type="date" name="date" value="2022-03-01" min="2022-01-01" max="2022-12-31" />
===Note===
When an incorrect date is entered, the browser will fall back to a text-input field. Read the link below how to handle these situations.

===Links===
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/input/date

DevOps:Doc/FlexForm/1.0/input/url

2022-11-29T17:48:25Z

944f869b-8467-464e-95c7-903362952755:

==Name==
url

==Example==
<syntaxhighlight lang="html">
<_form action="get" restrictions="lifted">
<_label for="yoururl">Your website: </_label>
<_input type="url" name="website-url" id="yoururl" pattern="https?://.*" size="30" value="https://" />
<_input type="submit" value="Go" />
</_form>
</syntaxhighlight>

<_form action="get" restrictions="lifted">
<_label for="yoururl">Your website: </_label>
<_input type="url" name="website-url" id="yoururl" pattern="https?://.*" size="30" value="https://" />
<_input type="submit" value="Go" />
</_form>

DevOps:Doc/FlexForm/1.0/input/week

2022-11-29T17:27:25Z

944f869b-8467-464e-95c7-903362952755:

==Name==
week

==Example==

<syntaxhighlight>
<_form restrictions="lifted">
<_label>Six weeks vacant: 30-35 (2022). Pick any</_label>

<_input type="week" name="hotel-week" id="hotel-week" min="2022-W30" max="2022-W35" value="2022-W34" />

<_input type="submit" />
</_form>
</syntaxhighlight>

<_form restrictions="lifted">
<_label>Six weeks vacant: 30-35 (2022). Pick any</_label>

<_input type="week" name="hotel-week" id="hotel-week" min="2022-W30" max="2022-W35" value="2022-W34" />

<_input type="submit" />
</_form>

DevOps:Doc/FlexForm/1.0/input/week

2022-11-29T17:27:02Z

944f869b-8467-464e-95c7-903362952755:

==Name==
week

==Example==

<syntaxhighlight>
<_form restrictions="lifted">
<_label>Six weeks vacant: 30-35 (2022). Pick any</_label>

<_input type="week" name="hotel-week" id="hotel-week" min="2022-W30" max="2022-W35" value="2022-W34" />

<_input type="submit">
</_form>
</syntaxhighlight>

<_form restrictions="lifted">
<_label>Six weeks vacant: 30-35 (2022). Pick any</_label>

<_input type="week" name="hotel-week" id="hotel-week" min="2022-W30" max="2022-W35" value="2022-W34" />

<_input type="submit">
</_form>

DevOps:Doc/FlexForm/1.0/input/time

2022-11-29T16:09:24Z

944f869b-8467-464e-95c7-903362952755:

==Name==
time

==Description==

==Example==
<syntaxhighlight>
<_form restrictions="lifted" >
<_label for="apptime">Pick a time between 9 AM and 5 PM.</_label>
<br>
<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />
<br>
<_input type="submit" />
</_form>
</syntaxhighlight>

<_form restrictions="lifted" >
<_label for="apptime">Pick a time between 9 AM and 5 PM.</_label>
<br>
<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />
<br>
<_input type="submit" />
</_form>

DevOps:Doc/FlexForm/1.0/input/time

2022-11-29T16:08:43Z

944f869b-8467-464e-95c7-903362952755:

==Name==
time

==Description==

==Example==
<syntaxhighlight>
<_form restrictions="lifted" >
<_label for="apptime">Pick a time between 9 AM and 5 PM.</_label>

<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />

<_input type="submit" />
</_form>
</syntaxhighlight>

<_form restrictions="lifted" >
<_label for="apptime">Pick a time between 9 AM and 5 PM.</_label>
<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />

<_input type="submit" />
</_form>

DevOps:Doc/FlexForm/1.0/input/time

2022-11-29T16:05:48Z

944f869b-8467-464e-95c7-903362952755:

==Name==
time

==Description==

==Example==
<syntaxhighlight>
<_label for="apptime">Pick a time between 9 AM and 5 PM.<_label>

<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />
</syntaxhighlight>

<_label for="apptime">Pick a time between 9 AM and 5 PM.<_label>

<_input type="time" id="apptime" name="appointment" min="09:00" max="17:00" value="10:00" />

DevOps:Doc/FlexForm/1.0/input/reset

2022-11-29T15:54:08Z

944f869b-8467-464e-95c7-903362952755:

==Name==
reset

==Description==
Input of type reset. Used to reset all form inputs to their initial values.

==Example==
<syntaxhighlight lang="html">
<_form action="get" restrictions="lifted">
<_input name="Title" type="text" value="Some initial value here" />
<br>
<_input name="Name" type="text" value="" />
<br>
<_input name="Description" type="textarea"></_input>

<_input type="reset" class="btn btn-secondary" value="Reset" />

</_form>
</syntaxhighlight>

<_form action="get" restrictions="lifted">
<_input name="Title" type="text" value="Some initial value here" />
<br>
<_input name="Name" type="text" value="" />
<br>
<_input name="Description" type="textarea"></_input>

<_input type="reset" class="btn btn-secondary" value="Reset" />

</_form>

DevOps:Doc/FlexForm/1.0/input/reset

2022-11-29T15:53:24Z

944f869b-8467-464e-95c7-903362952755:

==Name==
reset

==Description==
Input of type reset. Used to reset all form inputs to their initial values.

==Example==
{{#tag:syntaxhighlight|<_form action="get" restrictions="lifted">
<_input name="Title" type="text" value="Some initial value here" />
<br>
<_input name="Name" type="text" value="" />
<br>
<_input name="Description" type="textarea"></_input>

<_input type="reset" class="btn btn-secondary" value="Reset" />

</_form>
|lang=html
}}

<_form action="get" restrictions="lifted">
<_input name="Title" type="text" value="Some initial value here" />
<br>
<_input name="Name" type="text" value="" />
<br>
<_input name="Description" type="textarea"></_input>

<_input type="reset" class="btn btn-secondary" value="Reset" />

</_form>

DevOps:Doc/FlexForm/1.0/input/tel

2022-11-29T15:41:09Z

944f869b-8467-464e-95c7-903362952755: /* Example */

==Name==
tel

==Description==
Input type for telephone numbers.

==Example==
<syntaxhighlight lang="html">
<_form action="get" restrictions="lifted">
<_label for="call-me">Enter your phone number (Dutch format: +31 123456789 )</_label>
<br>
<_input type="tel" id="call-me" name="phone" pattern="(^\+[0-9]{2}|^\+[0-9]{2}$0$|^$\+[0-9]{2}$$0$|^00[0-9]{2}|^0)([0-9]{9}$|[0-9\-\s]{10}$)" value="+31 123456789" />
</_form>
</syntaxhighlight>

<_form action="get" restrictions="lifted">
<_label for="call-me">Enter your phone number (Dutch format: +31 123456789 )</_label>
<br>
<_input type="tel" id="call-me" name="phone" pattern="(^\+[0-9]{2}|^\+[0-9]{2}$0$|^$\+[0-9]{2}$$0$|^00[0-9]{2}|^0)([0-9]{9}$|[0-9\-\s]{10}$)" value="+31 123456789" />
</_form>