Search results
Create the page "Webdav for Infostore" on this wiki! See also the search results found.
- =Open-Xchange FAQ for Users= '''Q: Which Browsers are recommended for the use with the Open-Xchange web front-end?'''<BR>11 KB (1,953 words) - 09:15, 10 January 2020
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:297 KB (40,685 words) - 10:14, 13 June 2017
- ;Context: In Open-Xchange, a Context is a container for one or more users. Usually one Context contains one domain.. # Add the plan/subscription for the Open-Xchange Service to your cart.27 KB (3,970 words) - 06:25, 1 September 2016
- ''Note: This represents the state of OX6 and AppSuite until v7.4.1. For the newer implementation, see [[AppSuite: Permission Level]].'' * '''PIM + InfoStore''' adds private InfoStore functionality to the PIM level13 KB (1,802 words) - 08:19, 8 February 2018
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...in which file are found. This does not apply to core configuration files. For these, you cannot re-define the value in another file:231 KB (31,767 words) - 10:27, 19 April 2013
- |response timeout in seconds for reading response from the backend (default 0s; infinite) '''Available with ...ntacts, calendar & tasks) attachments, etc. Thus even if you don't use the Infostore/Drive, you should always set an appropriate amount so users can e.g. store19 KB (2,719 words) - 09:19, 10 January 2020
- You write a new UI app or plugin (chat module, for example) and in addition, you want to make sure that only a specific set of First, disable it for everyone as default (or enable it for everyone, depending on what your aim is).5 KB (645 words) - 15:55, 26 February 2020
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:300 KB (41,181 words) - 07:10, 9 July 2015
- |response timeout in seconds for reading response from the backend (default 0s; infinite) '''Available with |Given name for the user35 KB (5,130 words) - 09:22, 10 January 2020
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:271 KB (37,062 words) - 13:43, 1 July 2015
- |Cannot find mail account with identifier %1$s for user %2$s in context %3$s. |Found two mail accounts with same identifier %1$s for user %2$s in context %3$s.213 KB (27,569 words) - 14:38, 15 August 2013
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...in which file are found. This does not apply to core configuration files. For these, you cannot re-define the value in another file:231 KB (31,760 words) - 11:29, 16 April 2013
- |Username for the new context admin user |Displayname for the new context admin user19 KB (2,693 words) - 13:57, 2 December 2016
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...in which file are found. This does not apply to core configuration files. For these, you cannot re-define the value in another file:247 KB (33,845 words) - 11:37, 16 August 2013
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...in which file are found. This does not apply to core configuration files. For these, you cannot re-define the value in another file:268 KB (37,155 words) - 12:16, 21 October 2015
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:351 KB (48,276 words) - 15:48, 31 January 2017
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:280 KB (38,131 words) - 21:26, 5 March 2014
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:347 KB (47,794 words) - 13:34, 31 January 2017
- ....4.2 on, a new concept named capabilities has been introduced. This allows for a more granular control of access to features. This article has not yet bee * '''PIM + InfoStore''' adds private InfoStore functionality to the PIM level13 KB (1,817 words) - 13:42, 26 November 2018
- This is an overview of all configuration parameters for the AppSuite backend. By default, this list is sorted by the .properties fi ...pply to some core configuration files which are explicitly loaded by name. For these, you cannot re-define the value in another file:366 KB (50,420 words) - 07:11, 29 September 2017