DevOps:Doc/FlexForm/1.1/edit/json - Revision history

81d56153-9868-4094-90a0-df1700ff7090: Text replacement - "{{Doc properties" to "{{Csp class properties"

2025-07-15T08:59:07Z

Text replacement - "{{Doc properties" to "{{Csp class properties"

ws-class-props
← Older revision		Revision as of 10:59, 15 July 2025
Line 1:		Line 1:
	{{~~Doc~~ properties		{{Csp class properties
	\|Subject version=1.1		\|Subject version=1.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm

Charlot at 11:09, 23 November 2022

2022-11-23T11:09:06Z

← Older revision		Revision as of 13:09, 23 November 2022
Line 19:		Line 19:
	'''template ''' = This argument has been kept to keep editing a template wiki page and editing a JSON page similar to each other.		'''template ''' = 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.		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 tell 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.		*'''json''' : When you create a JSON page with _create, every new named array will also get a unique id, called '''ffID'''. The following example tell 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:		Example JSON:
Line 44:		Line 44:
	</syntaxhighlight>		</syntaxhighlight>

	*jsonk : This option lets you traverse down a JSON manually. You tell FlexForm exactly what part of the JSON you want to edit and what value of a form input field to use. 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.		*'''jsonk''' : This option lets you traverse down a JSON manually. You tell FlexForm exactly what part of the JSON you want to edit and what value of a form input field to use. 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">		<syntaxhighlight lang="php">
	<_edit target="Json_test_result" format="json" template="jsonk\|Coats.Title" formfield="Title" />		<_edit target="Json_test_result" format="json" template="jsonk\|Coats.Title" formfield="Title" />

Charlot at 11:07, 23 November 2022

2022-11-23T11:07:48Z

← Older revision		Revision as of 13:07, 23 November 2022
Line 4:		Line 4:
	_edit		_edit
	===Synopsis===		===Synopsis===
	Using a form to edit pages that have content with JSON.		'''Introduced in FlexForm version 1.1.43'''. Using a form to edit pages that have content with JSON.
	===Description===		===Description===
	How to edit JSON content pages in the wiki with FlexForm.		How to edit JSON content pages in the wiki with FlexForm.

Charlot at 11:06, 23 November 2022

2022-11-23T11:06:57Z

← Older revision		Revision as of 13:06, 23 November 2022
Line 19:		Line 19:
	'''template ''' = This argument has been kept to keep editing a template wiki page and editing a JSON page similar to each other.		'''template ''' = 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.		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 tell 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.		*json : When you create a JSON page with _create, every new named array will also get a unique id, called '''ffID'''. The following example tell 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:		Example JSON:
Line 38:		Line 38:
	<syntaxhighlight lang="php">		<syntaxhighlight lang="php">
	<_edit target="Json_test_result" format="json" template="json\|ffID=1669192355" formfield="Title" />		<_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>		</syntaxhighlight>

	'''formfield''' = Name of the ~~field~~ in the template~~. Field~~ in the form should have the same name		*jsonk : This option lets you traverse down a JSON manually. You tell FlexForm exactly what part of the JSON you want to edit and what value of a form input field to use. 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		'''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		'''mwslot''' = [optional] Name of content slot to use. Defaults to main content slot

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

	===Note===		===Note===

	* You can have multiple _edit's in a form all doing different tasks.		* You can have multiple _edit's in a form all doing different tasks.
	* If you have more than 5 edits to one singe 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).		* If you omit value, then the value of the form will be used (so what a user has filled in).
	===Links===		===Links===
	https://www.mediawiki.org/wiki/Multi-Content_Revisions		https://www.mediawiki.org/wiki/Multi-Content_Revisions

Charlot at 10:54, 23 November 2022

2022-11-23T10:54:14Z

← Older revision	Revision as of 12:54, 23 November 2022
Line 1:	Line 1:
		===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

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

		'''template ''' = 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 tell 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>

		'''formfield''' = Name of the field in the template. Field 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

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

		===Note===

		* You can have multiple _edit's in a form all doing different tasks.
		* If you have more than 5 edits to one singe 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

Charlot: User:Charlot

2022-11-23T10:43:03Z

User:Charlot

ws-base-props
← Older revision		Revision as of 12:43, 23 November 2022
Line 1:		Line 1:
	{{Base properties		{{Base properties
	\|Title=~~edit/~~json		\|Title=json
	\|Class=Doc		\|Class=Doc
	}}		}}

Charlot: User:Charlot

2022-11-23T10:42:49Z

User:Charlot

ws-class-props
← Older revision		Revision as of 12:42, 23 November 2022
Line 2:		Line 2:
	\|Subject version=1.1		\|Subject version=1.1
	\|Doc subject=DevOps:Doc/FlexForm		\|Doc subject=DevOps:Doc/FlexForm
			\|Doc synopsis=Edit JSON content
			\|Doc parent=DevOps:Doc/FlexForm/1.0/edit
			\|Doc sort order=10
			\|Doc target group=User
	}}		}}

Charlot: User:Charlot

2022-11-23T10:42:03Z

User:Charlot

New page