AppSuite:Configuring portal plugins - Revision history

Choeger at 06:03, 26 June 2018

2018-06-26T06:03:35Z

← Older revision		Revision as of 06:03, 26 June 2018
Line 157:		Line 157:
	The combination of making a tile both protected and disabling it makes it impossible for the user to enable it. From 7.6.0 on, this means it is not shown in the settings either. Before that, it was greyed out but still present.		The combination of making a tile both protected and disabling it makes it impossible for the user to enable it. From 7.6.0 on, this means it is not shown in the settings either. Before that, it was greyed out but still present.

	io.ox/portal/:		io.ox/portal/:
	widgets:		widgets:
	protected:		protected:
	quota_0:		quota_0:
	color: "red"		color: "red"
	id: "quota_0"		id: "quota_0"
	enabled: false		enabled: false
	index: 1		index: 1
	inverse: false		inverse: false
	plugin: "plugins/portal/quota/register"		plugin: "plugins/portal/quota/register"
	type: "quota"		type: "quota"

	[[Category:Backend]][[Category:AppSuite]]		[[Category:Backend]][[Category:AppSuite]]

Vitali.sjablow at 12:33, 9 February 2018

2018-02-09T12:33:40Z

← Older revision		Revision as of 12:33, 9 February 2018
Line 122:		Line 122:
	index: 6		index: 6

	And then modify this as wanted for your deployment		And then modify this as wanted for your deployment. Note, that LikedIn support was removed with version 7.10.

	== Forcing a tile ==		== Forcing a tile ==

Frank.paczynski at 10:30, 16 March 2017

2017-03-16T10:30:18Z

← Older revision		Revision as of 10:30, 16 March 2017
Line 169:		Line 169:
	type: "quota"		type: "quota"

	[[Category:UI]][[Category:AppSuite]]		[[Category:Backend]][[Category:AppSuite]]

	[[Category:Portal]]		[[Category:Portal]]

	[[Category:Administrator]][[Category:Developer]]		[[Category:Administrator]][[Category:Developer]]

John-david.henderson: /* Configuring the portal */

2016-04-15T13:59:24Z

Configuring the portal

← Older revision		Revision as of 13:59, 15 April 2016
Line 32:		Line 32:
	type: "birthdays"		type: "birthdays"

	In order to configure widgets on the backend we have o turn the above into a valid YAML structure:		In order to configure widgets on the backend we have to turn the above into a valid YAML structure:

	birthdays_0:		birthdays_0:

Frank.paczynski at 10:22, 9 February 2016

2016-02-09T10:22:59Z

← Older revision		Revision as of 10:22, 9 February 2016
Line 1:		Line 1:
			<!-- !!! -->
			<!-- PLEASE APPLY CHANGES ONLY TO THE NEW TECHNICAL DOCUMENTATION: wd/frontend/web/documentation -->
			<!-- !!! -->

	{{Stability-stable}}		{{Stability-stable}}
	{{VersionFrom\|7.4.0}}		{{VersionFrom\|7.4.0}}

Martin.schneider: US 97798972, remove everything related to facebook

2015-07-07T13:05:44Z

US 97798972, remove everything related to facebook

← Older revision		Revision as of 13:05, 7 July 2015
Line 105:		Line 105:
	plugin: 'plugins/portal/birthdays/register'		plugin: 'plugins/portal/birthdays/register'
	color: 'lightgreen'		color: 'lightgreen'
	~~enabled: true~~
	~~index: 4~~
	~~facebook_0:~~
	~~plugin: 'plugins/portal/facebook/register'~~
	~~color: 'blue'~~
	enabled: true		enabled: true
	index: 4		index: 4

Tierlieb: /* Disabling a tile completely */ Example howto: disabling the quota plugin

2014-06-13T09:22:01Z

Disabling a tile completely: Example howto: disabling the quota plugin

← Older revision		Revision as of 09:22, 13 June 2014
Line 154:		Line 154:

	One caveat in all this: After changing any of the above configuration, you will have to reload the UI twice, since App Suite uses read-through caching for the settings data.		One caveat in all this: After changing any of the above configuration, you will have to reload the UI twice, since App Suite uses read-through caching for the settings data.

			== Disabling a tile completely ==
			The combination of making a tile both protected and disabling it makes it impossible for the user to enable it. From 7.6.0 on, this means it is not shown in the settings either. Before that, it was greyed out but still present.

			io.ox/portal/:
			widgets:
			protected:
			quota_0:
			color: "red"
			id: "quota_0"
			enabled: false
			index: 1
			inverse: false
			plugin: "plugins/portal/quota/register"
			type: "quota"

	[[Category:UI]][[Category:AppSuite]]		[[Category:UI]][[Category:AppSuite]]

Tierlieb: added status

2014-06-12T11:34:39Z

added status

← Older revision		Revision as of 11:34, 12 June 2014
Line 1:		Line 1:
	~~= Configuring portal plugins (starting with~~ 7.4.0) =		{{Stability-stable}}
			{{VersionFrom\|7.4.0}}

			= Configuring portal plugins =

	''Synopsis:'' This article covers how to configure which plugins ("tiles") are shown, whether they are mandatory or just suggested to the user.		''Synopsis:'' This article covers how to configure which plugins ("tiles") are shown, whether they are mandatory or just suggested to the user.

Choeger at 11:55, 17 September 2013

2013-09-17T11:55:27Z

← Older revision		Revision as of 11:55, 17 September 2013
Line 1:		Line 1:
	~~<div class~~=~~"title">~~Configuring portal plugins~~</div>~~		= Configuring portal plugins (starting with 7.4.0) =

	''Synopsis:'' This article covers how to configure which plugins ("tiles") are shown, whether they are mandatory or just suggested to the user.		''Synopsis:'' This article covers how to configure which plugins ("tiles") are shown, whether they are mandatory or just suggested to the user.
Line 5:		Line 5:
	__TOC__		__TOC__

	== Configuring the portal ~~(starting with 7.4.0)~~ ==		== Configuring the portal ==

	When running OX AppSuite you may want to specify a starting configuration for which tiles the portal shows and whether certain tiles are mandatory or not. This is especially useful when you are introducing your own tile implementations. To make this possible, the portal consists of three types of tiles: User tiles, eager tiles and protected tiles. User tiles are tiles that the user added herself to the portal page, eager tiles are those suggested by the installation which can be removed and protected tiles are set by the backend.		When running OX AppSuite you may want to specify a starting configuration for which tiles the portal shows and whether certain tiles are mandatory or not. This is especially useful when you are introducing your own tile implementations. To make this possible, the portal consists of three types of tiles: User tiles, eager tiles and protected tiles. User tiles are tiles that the user added herself to the portal page, eager tiles are those suggested by the installation which can be removed and protected tiles are set by the backend.

Choeger at 11:54, 17 September 2013

2013-09-17T11:54:28Z

← Older revision		Revision as of 11:54, 17 September 2013
Line 5:		Line 5:
	__TOC__		__TOC__

	== Configuring the portal ==		== Configuring the portal (starting with 7.4.0) ==

	When running OX AppSuite you may want to specify a starting configuration for which tiles the portal shows and whether certain tiles are mandatory or not. This is especially useful when you are introducing your own tile implementations. To make this possible, the portal consists of three types of tiles: User tiles, eager tiles and protected tiles. User tiles are tiles that the user added herself to the portal page, eager tiles are those suggested by the installation which can be removed and protected tiles are set by the backend.		When running OX AppSuite you may want to specify a starting configuration for which tiles the portal shows and whether certain tiles are mandatory or not. This is especially useful when you are introducing your own tile implementations. To make this possible, the portal consists of three types of tiles: User tiles, eager tiles and protected tiles. User tiles are tiles that the user added herself to the portal page, eager tiles are those suggested by the installation which can be removed and protected tiles are set by the backend.