Input: [Method] DELETE [Safe] no [Reference] Section 5.3.5 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] GET [Safe] yes [Reference] Section 5.3.1 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] HEAD [Safe] yes [Reference] Section 5.3.2 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] OPTIONS [Safe] yes [Reference] Section 5.3.7 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] POST [Safe] no [Reference] Section 5.3.3 [Idempotent]

Output: no

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] PUT [Safe] no [Reference] Section 5.3.4 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Method] TRACE [Safe] yes [Reference] Section 5.3.8 [Idempotent]

Output: yes

Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content


Input: [Description] The name given by the provider [Keyword]

Output: %name


Input: [Description] The MuMuDVB channel number [Keyword]

Output: %number


Input: [Description] The channel primary language [Keyword]

Output: %lang


Input: [Description] The DVB card number [Keyword]

Output: %card


Input: [Description] The tuner number [Keyword]

Output: %tuner


Input: [Description] The server number specified by server_id or the command line [Keyword]

Output: %server


Input: [Description] The logical channel number (channel number given by the provider). Your provider have to stream the LCN. The LCN will be displayed with three digits including 0. Ex "002". If the LCN is not detected, %lcn will be replaced by an empty string. [Keyword]

Output: %lcn


Input: [Description] Same as above but with a two digits format [Keyword]

Output: %2lcn


Input: [Description] The channel service id (decimal for the port, hexadecimal for ipv6) [Keyword]

Output: %sid


Input: [Description] The channel service id. The two higher bits (between 0 and 255) [Keyword]

Output: %sid_hi


Input: [Description] The channel service id. The two lower bits (between 0 and 255) [Keyword]

Output: %sid_lo


Input: [ID] FR1 [Business Rule name] User details [Business Rule Description]

Output: It must be possible to specify the following details when creating a new user: First name Surname Birth date Address City Zip code Telephone Gender email

Use Case Specification Example - All About Requirements


Input: [ID] FR2 [Business Rule name] Specify related department [Business Rule Description]

Output: It must be possible to specify that the user to be created belongs to one of the following departments: Marketing Sales R&D IT Administration

Use Case Specification Example - All About Requirements


Input: [ID] FR3 [Business Rule name] Permissions [Business Rule Description]

Output: It must be possible to specify the following permissions to the system: Read only Read/write

Use Case Specification Example - All About Requirements


Input: [ID] FR4 [Business Rule name] Mandatory details [Business Rule Description]

Output: The following fields are mandatory and must be filled-in: First name Surname Address City Zip code Gender Department relation Permission type

Use Case Specification Example - All About Requirements


Input: [ID] FR5 [Business Rule name] No duplicates [Business Rule Description]

Output: It must be validated that the user with duplicate information (as specified in mandatory fields) does not exist.

Use Case Specification Example - All About Requirements


Input: [ID] FR6 [Business Rule name] Apply employee number [Business Rule Description]

Output: The user to be created must be created with a unique four digit employee number

Use Case Specification Example - All About Requirements


Input: [ID] FR7 [Business Rule name] Apply default password [Business Rule Description]

Output: The user to be created must be created with a default 8 character password

Use Case Specification Example - All About Requirements


Input: [ID] FR8 [Business Rule name] Grant permissions [Business Rule Description]

Output: The user to be created is granted the privileges as specified in FR3

Use Case Specification Example - All About Requirements


Input: [PRESS] CTRL+C [TO DO THIS]

Output: Copy

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+X [TO DO THIS]

Output: Cut

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+V [TO DO THIS]

Output: Paste

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+SHIFT+C [TO DO THIS]

Output: Copy formatting

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+SHIFT+V [TO DO THIS]

Output: Paste formatting

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+ALT+V [TO DO THIS]

Output: Paste special

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+Z [TO DO THIS]

Output: Undo

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+Y [TO DO THIS]

Output: Redo

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+P [TO DO THIS]

Output: Print

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+F [TO DO THIS]

Output: Find

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [PRESS] CTRL+S [TO DO THIS]

Output: Save

Microsoft Word 2010 common keyboard shortcuts | ITworld


Input: [Symbol Type] A [Description]

Output: The symbol's value is absolute, and will not be changed by further linking.

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Symbol Type] B [Description]

Output: Un-initialized data section

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Symbol Type] D [Description]

Output: Initialized data section

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Symbol Type] T [Description]

Output: Normal code section

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Symbol Type] U [Description]

Output: Undefined symbol used but not defined. Dependency on another library.

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Symbol Type] W [Description]

Output: Doubly defined symbol. If found, allow definition in another library to resolve dependency.

Linux Tutorial - Static, Shared Dynamic and Loadable Linux Libraries


Input: [Name] Data Control [Used to Create...] Not used to create anything. Serves as a container for the other objects. [Description]

Output: Represents a data control. You cannot use the data control itself to create UI components, but you can use any of the child objects listed under it. Depending on how your business services were defined, there may be more than one data control, each representing a logical grouping of data functions.


Input: [Name] Create Method [Used to Create...] Creation forms [Description]

Output: Represents a built-in method that creates a new instance of an object in a data collection. Create method icons are located in a folder named after the data collection to which they belong. These data collection folders are located in the Constructors folder under the data control. The Attributes folder, which appears as a child under a create method, contains all the attributes of the data collection in which the object will be created. If the objects in a collection contain an attribute from another collection (called a foreign key in relational databases), that attribute is represented by an accessor return icon. I this case, the accessor returns a single value and has no children. For more information about using constructors, see Section 10.7, "Creating an Input Form for a New Record".


Input: [Name] Method [Used to Create...] Command components For methods that accept parameters: command components and parameterized forms [Description]

Output: Represents a custom method on the data control that may accept parameters, perform some action or business logic, and return single values or data collections. If the method is a get method of a Map and returns a value or a collection, a method return icon appears as a child under it. If a method requires a parameter, a folder appears under the method, which lists the required parameters. For more information about using methods that accept parameters, see Section 10.6, "Creating a Form or Table Using a Method that Takes Parameters".


Input: [Name] Method Return [Used to Create...] For collections: forms, tables, trees, and range navigation components For single values: text fields and selection lists [Description]

Output: Represents an object that is returned by a custom method. The returned object may be a single value or a collection. A method return appears as a child under the method that returns it. The objects that appear as children under a method return may be attributes of the collection, accessor returns that represent collections related to the parent collection, other methods that perform actions related to the parent collection, and operations that can be performed on the parent collection.


Input: [Name] Accessor Return [Used to Create...] For collections: forms, tables, trees, range navigation components, and master-detail widgets For single objects: forms, master-detail widgets, and selection lists For single objects under a constructor: selection lists only [Description]

Output: Represents an object returned by an accessor method on the business service. An accessor method is used when the objects returned are JavaBeans. Accessor returns appear as children under method returns, other accessor returns, or in the Attributes folder under built-in create methods. Accessor returns are objects that are related to the current object in the parent collection. This relationship is usually based on a common unique attribute in both objects. For example, if a method returns a collection of users, an accessor return that is a child of that collection might be a collection of service requests that are assigned to a particular user. In ADF, the relationship between parent and child collections is called a master-detail relationship. For more information about accessor returns and master-detail objects, see Chapter 8, "Displaying Master-Detail Data". The children under an accessor return may be attributes of the object, other accessor returns, custom methods that return a value from the accessor return, and operations that can be performed on the accessor return.


Input: [Name] Attribute [Used to Create...] Label, text field, and selection list components. [Description]

Output: Represents a discrete data element in an object. Attributes appear as children under the method returns or accessor returns to which they belong.


Input: [Name] Operation [Used to Create...] UI actions such as buttons or links. [Description]

Output: Represents a built-in data control operation that performs actions on the parent object. Data control operations are located in an Operations folder under method returns or accessor returns and under the root data control node. The operations that are children of a particular method or accessor return operate on that return object only, while operations under the data control node operate on all the objects represented by the data control. If an operation requires one or more parameters, they are listed in a Parameters folder under the operation.


Input: [Name] Parameter [Used to Create...] Label, text, and selection list components. [Description]

Output: Represents a parameter value that is declared by the method or operation under which it appears. Parameters appear in the Parameters folder under a method or operation.


Input: [File] advanced-cache.php [Type of Dropin] Advanced or Alternative Cache [Context] Single Installation [Active since]

Output: Constant WP_CACHE is TRUE


Input: [File] db.php [Type of Dropin] Own database class [Context] Single installation [Active since]

Output: Always


Input: [File] db-error.php [Type of Dropin] Own database error alert [Context] Single installation [Active since]

Output: At DB Error


Input: [File] install.php [Type of Dropin] Own installation routine [Context] Single installation [Active since]

Output: At installation


Input: [File] maintenance.php [Type of Dropin] Own maintenance message [Context] Single installation [Active since]

Output: At updates, maintenance


Input: [File] object-cache.php [Type of Dropin] External Object Cache [Context] Single installation [Active since]

Output: Always


Input: [File] sunrise.php [Type of Dropin] Before the WP Multisite Installation gets loaded [Context] Multisite installation [Active since]

Output: If constant SUNRISE set


Input: [File] blog-deleted.php [Type of Dropin] Own message, when a blog gets deleted [Context] Multisite installation [Active since]

Output: If a blog gets deleted


Input: [File] blog-inactive.php [Type of Dropin] Own message, if a blog is set inactive [Context] Multisite installation [Active since]

Output: If a blog becomes inactive


Input: [File] blog-suspended.php [Type of Dropin] Own message, if a blog got suspended [Context] Multisite installation [Active since]

Output: When a blog gets marked as archive or spam


Input: [File] $locale.php [Type of Dropin] functions at active language key [Context] Single & multisite installation [Active since]

Output: When language key set in constant WP_LANG


Input: [Item] 0 [Value]

Output: true if copying gc, false if mark and sweep


Input: [Item] 1 [Value]

Output: number of active heaps


Input: [Item] 2 [Value]

Output: maximum number of heaps


Input: [Item] 3 [Value]

Output: number of objects per heap


Input: [Item] 4 [Value]

Output: amount of consing of objects before next gc


Input: [Item] 5 [Value]

Output: number of gcs so far


Input: [Make Target] empty [Description]

Output: build everything but no images


Input: [Make Target] all [Description]

Output: build everything including images


Input: [Make Target] all-conf [Description]

Output: build all configurations


Input: [Make Target] images [Description]

Output: create complete j2sdk and j2re images


Input: [Make Target] install [Description]

Output: install the generated images locally, typically in /usr/local


Input: [Make Target] clean [Description]

Output: remove all files generated by make, but not those generated by configure


Input: [Make Target] dist-clean [Description]

Output: remove all files generated by both and configure (basically killing the configuration)


Input: [Make Target] help [Description]

Output: give some help on using make, including some interesting make targets


Input: [Configuration Value] (Not Standard) [Configuration Element]

Output: Base DN

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] false [Configuration Element]

Output: User Subtree

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] posixAccount [Configuration Element]

Output: Object Class

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] sAMAccountName [Configuration Element]

Output: User ID Attribute

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] uid [Configuration Element]

Output: Real Name Attribute

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] mail [Configuration Element]

Output: E-Mail Attribute

Sonatype Nexus Documentation - Sonatype.com


Input: [Configuration Value] (Not Used) [Configuration Element]

Output: Password Attribute

Sonatype Nexus Documentation - Sonatype.com


Input: [#] 1 [Name]

Output: How to login and understand the interface


Input: [#] 2 [Name]

Output: How to send text messages individually


Input: [#] 3 [Name]

Output: How to send text messages to multiple recipients


Input: [#] 4 [Name]

Output: How to use SMS Chat


Input: [#] 5 [Name]

Output: How to schedule text messages to be sent at a later date


Input: [#] 6 [Name]

Output: How to set up and use lists


Input: [#] 7 [Name]

Output: How to add contacts individually


Input: [#] 8 [Name]

Output: How to import contacts


Input: [#] 9 [Name]

Output: How to use custom fields


Input: [#] 10 [Name]

Output: How to save time with text message templates


Input: [#] 11 [Name]

Output: How to send personalized SMS using tags


Input: [#] 12 [Name]

Output: How to use forms to expand your marketing database


Input: [#] 13 [Name]

Output: How to review sent and received text message data


Input: [Field] desktop_shortcut [Value] 1 or 0 [Explanation]

Output: 1: The Bomgar Button Profile will be deployed to the desktop as an Icon with a shortcut. 0: The Bomgar Button Profile will not be deployed to the desktop as an Icon with a shortcut.


Input: [Field] direct_access [Value] 1 or 0 [Explanation]

Output: 1: The customer can use the Bomgar Button to start a session, in the queue where the Button is displayed. 0: The customer cannot use the Bomgar Button to start a session, in the queue where the Button is deployed.


Input: [Field] id [Value] string [Explanation]

Output: The unique identifier of the Bomgar Button Profile.


Input: [Field] menu_shortcut [Value] 1 or 0 [Explanation]

Output: 1: The Bomgar Button Profile will be deployed to the customer’s system as a program available to select in the programs menu. 0: The Bomgar Button Profile will not be deployed to the customer’s system as a program available to select in the programs menu.


Input: [Field] name [Value] string [Explanation]

Output: The name of the Bomgar Button Profile.


Input: [Field] short_title [Value] string [Explanation]

Output: The short title of the Bomgar Button Profile.


Input: [Field] title [Value] string [Explanation]

Output: The title of the Bomgar Button Profile.


Input: [NAME] lccountry [TYPE] Session cookie [PURPOSE]

Output: Registers the country selected or related to the domain

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] lclanguage [TYPE] Session cookie [PURPOSE]

Output: Registers the language related to the chosen country

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] lcvariante [TYPE] Session cookie [PURPOSE]

Output: Specifies the user's language variant related to the chosen country

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] lclocale [TYPE] Session cookie [PURPOSE]

Output: ISO of the language and photograph

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] refresh2 [TYPE] Session cookie [PURPOSE]

Output: Selects content according to the country when browsing the international version of the page

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] PHPSESSID [TYPE] Session cookie [PURPOSE]

Output: Identifies the user session

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] __utma, __utmz, __utmb, _utmc [TYPE] Session cookie [PURPOSE]

Output: Statistical utility from Google Analytics

Pronovias | Wedding dresses and Cocktail dresses


Input: [NAME] CookiePolicy [TYPE] Temporary cookie, duration 3 months [PURPOSE]

Output: Reminds users that they have agreed with the cookie policy

Pronovias | Wedding dresses and Cocktail dresses


Input: [Verb] Collects [Purpose] to evaluate budget requests. [Object]

Output: financial data


Input: [Verb] Conducts [Purpose] to support financial planning. [Object]

Output: analytical studies


Input: [Verb] Compiles [Purpose] for distribution to administrators. [Object]

Output: enrollment data


Input: [Verb] Cleans [Purpose] in conformance with established schedules. [Object]

Output: computer equipment


Input: [Verb] Drives [Purpose] to job sites. [Object]

Output: pickup truck carrying motor fuels


Input: [Verb] Overhauls and repairs [Purpose] daily, or as needed. [Object]

Output: equipment


Input: [Element] name [Description]

Output: The name element contains the username of the user. This is a short, usually less than 16 character "handle" of the user, not the real, full name. This should be the same as the username parameter used when calling the function, and hence redundant.

The user information array


Input: [Element] passwd [Description]

Output: The passwd element contains the user's password in an encrypted format. Often, for example on a system employing "shadow" passwords, an asterisk is returned instead.

The user information array


Input: [Element] uid [Description]

Output: User ID of the user in numeric form.

The user information array


Input: [Element] gid [Description]

Output: The group ID of the user. Use the function posix_getgrgid() to resolve the group name and a list of its members.

The user information array


Input: [Element] gecos [Description]

Output: GECOS is an obsolete term that refers to the finger information field on a Honeywell batch processing system. The field, however, lives on, and its contents have been formalized by POSIX. The field contains a comma separated list containing the user's full name, office phone, office number, and home phone number. On most systems, only the user's full name is available.

The user information array


Input: [Element] dir [Description]

Output: This element contains the absolute path to the home directory of the user.

The user information array


Input: [Element] shell [Description]

Output: The shell element contains the absolute path to the executable of the user's default shell.

The user information array


Input: [Item] Full Name [Sensitivity]

Output: Low

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Address [Sensitivity]

Output: Low

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Phone Number [Sensitivity]

Output: Low

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Date of Birth [Sensitivity]

Output: Medium

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Birthplace [Sensitivity]

Output: Medium

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Mother's Maiden Name [Sensitivity]

Output: Medium

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Social Security Number [Sensitivity]

Output: High

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Bank Account Number [Sensitivity]

Output: High

The Ultimate Guide to Identity Theft Prevention


Input: [Item] Credit Card Number [Sensitivity]

Output: High

The Ultimate Guide to Identity Theft Prevention


Input: [Item] PIN or Password [Sensitivity]

Output: High

The Ultimate Guide to Identity Theft Prevention


Input: [Type] CDATA [Default] #IMPLIED [Comment] a character encoding; char encoding of linked resource [Name]

Output: charset

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [Type] ( defer ) [Default] #IMPLIED [Comment] UA may defer execution of script [Name]

Output: defer

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [Type] CDATA [Default] #IMPLIED [Comment] reserved for possible future use [Name]

Output: event

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [Type] CDATA [Default] #IMPLIED [Comment] Uniform Resource Identifier as per RFC2396; a Uniform Resource Locator (URL) is a URI; reserved for possible future use [Name]

Output: for

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [Type] CDATA [Default] #IMPLIED [Comment] Uniform Resource Identifier as per RFC2396; a Uniform Resource Locator (URL) is a URI; URI for an external script [Name]

Output: src

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [Type] CDATA [Default] #REQUIRED [Comment] media type; content type of script language [Name]

Output: type

SCRIPT script for user-document interaction HTML 4.01 Strict


Input: [PHP] __get [Python]

Output: __getattr__

Python: an introduction for PHP (and other) programmers


Input: [PHP] __set [Python]

Output: __setattr__

Python: an introduction for PHP (and other) programmers


Input: [PHP] __isset [Python]

Output: not available

Python: an introduction for PHP (and other) programmers


Input: [PHP] __unset [Python]

Output: __delattr__

Python: an introduction for PHP (and other) programmers


Input: [PHP] __call [Python]

Output: not available

Python: an introduction for PHP (and other) programmers


Input: [PHP] __construct [Python]

Output: __init__

Python: an introduction for PHP (and other) programmers


Input: [PHP] __destruct [Python]

Output: __del__

Python: an introduction for PHP (and other) programmers


Input: [PHP] __invoke [Python]

Output: __call__

Python: an introduction for PHP (and other) programmers


Input: [PHP] ArrayAccess::offsetGet [Python]

Output: __getitem__

Python: an introduction for PHP (and other) programmers


Input: [PHP] ArrayAccess::offsetSet [Python]

Output: __setitem__

Python: an introduction for PHP (and other) programmers


Input: [PHP] ArrayAccess::offsetExists [Python]

Output: not available

Python: an introduction for PHP (and other) programmers


Input: [PHP] ArrayAccess::offsetUnset [Python]

Output: __delitem__

Python: an introduction for PHP (and other) programmers


Input: [Command] File.OpenFile [Alias] open [Description]

Output: Opens the file specified as a parameter


Input: [Command] File.NewFile [Alias] nf [Description]

Output: Creates and opens a new file


Input: [Command] File.NewProject [Alias] np [Description]

Output: Creates and opens a new project


Input: [Command] File.AddNewProject [Alias] addProj [Description]

Output: Creates and adds a new project to the current solution


Input: [Command] File.SaveAll [Alias] SaveAll [Description]

Output: Saves all the currently open files


Input: [Command] File.Close [Alias] close [Description]

Output: Closes the selected file


Input: [Command] View.FullScreen [Alias] FullScreen [Description]

Output: Switches to full-screen mode in the IDE


Input: [Command] View.Toolbox [Alias] toolbox [Description]

Output: Shows the toolbox window


Input: [Command] View.PropertiesWindow [Alias] props [Description]

Output: Shows the properties window


Input: [Command] Edit.GotoBrace [Alias] GotoBrace [Description]

Output: Skips to the corresponding brace (e.g., the closing brace of an if statement)


Input: [Command] Edit.SelectAll [Description]

Output: Selects all the text in the current document


Input: [Command] Edit.Undo [Alias] undo [Description]

Output: Equivalent to Edit → Undo


Input: [Command] Edit.Redo [Alias] redo [Description]

Output: Equivalent to Edit → Redo


Input: [Command] Edit.NextBookmark [Alias] NextBook [Description]

Output: Jumps to the next bookmark


Input: [Command] Edit.PreviousBookmark [Alias] PrevBook [Description]

Output: Jumps back to the previous bookmark


Input: [Command] Edit.CollapsetoDefinitions [Alias] StopOutlining [Description]

Output: Collapses all collapsible section of code (classes, regions, etc.)


Input: [Command] Build.BuildSolution [Alias] build [Description]

Output: Builds the current solution


Input: [Command] Debug.Print [Alias] ? [Description]

Output: Shows the value of the variable passed in as a parameter


Input: [Command] Debug.QuickWatch [Alias] ?? [Description]

Output: Displays the quick watch dialog for the variables passed in as a parameter


Input: [Command] Tools.Alias [Alias] alias [Description]

Output: Lists all currently defined aliases or defines a new one


Input: [Cache-Control Directive] no-cache [Description] When present, forces a caching device to forward any subsequent requests for the same content to the server for revalidation. That is, the cache must check with the server to ensure that the cached data is still valid. Also see the Pragma header description, for an alternative way of accomplishing the same thing. [HTTP Message Type]

Output: Request or Response

Table 276: HTTP Cache-Control Directives


Input: [Cache-Control Directive] public [Description] Indicates that the response may be cached by any cache, including a shared one (a cache used by many clients). See the topic on caching for more details on shared caches. [HTTP Message Type]

Output: Response


Input: [Cache-Control Directive] private [Description] Specifies that the response is intended for only a particular user and should not be placed into a shared cache. [HTTP Message Type]

Output: Response


Input: [Cache-Control Directive] no-store [Description] Specifies that the entire request or response should not be stored in a cache. This is used sometimes to prevent the storing of sensitive documents in caches where unauthorized people might be able to access them. However, as the HTTP standard points out, this is really a very rudimentary security measure and should not be trusted a great deal (since a malicious cache operator could simply ignore the directive.) [HTTP Message Type]

Output: Request or Response


Input: [Cache-Control Directive] max-age [Description] In a request, indicates that the client is willing to accept a response whose age is no greater than the value specified. In a response, indicates the maximum age of the response before it is considered stalethis is an alternative to the use of the Expires header and takes precedence over it. [HTTP Message Type]

Output: Request or Response


Input: [Cache-Control Directive] s-maxage [Description] If present, this directive specifies the maximum age for shared caches receiving the response. Private caches (ones that serve only a single client) use the max-age value described just above. [HTTP Message Type]

Output: Response


Input: [Cache-Control Directive] min-fresh [Description] Specifies that the client wants a response that is not only not stale at the time the request is received, but that will remain fresh for the specified number of seconds. [HTTP Message Type]

Output: Request


Input: [Cache-Control Directive] max-stale [Description] If sent without a parameter, indicates that the client is willing to accept a stale reply (one that has expired). If a numeric parameter is included, it indicates how stale, in seconds, the response may be. [HTTP Message Type]

Output: Request


Input: [Cache-Control Directive] only-if-cached [Description] Used only in special circumstances, this directive forces the reply to come from a cache only; the content may not come from the actual specified HTTP server. [HTTP Message Type]

Output: Request


Input: [Cache-Control Directive] must-revalidate [Description] Instructs a cache to revalidate its cache entry for the given response with the original server after it becomes stale. This is used to prevent problems with certain types of transactions that can occur if stale cache entries are sent to a client (perhaps as a result of the client using the max-stale directive.) [HTTP Message Type]

Output: Response


Input: [Cache-Control Directive] proxy-revalidate [Description] Similar to must-revalidate, but applies only to proxies that service many users. Private caches, such as those on individual client computers, are not affected. [HTTP Message Type]

Output: Response


Input: [Cache-Control Directive] no-transform [Description] Some caches will, by default, change the form in which certain cached entries are stored, to save space or improve performance. In cases where this might cause problems, the client or server can use this directive to request that this transformation not be performed. [HTTP Message Type]

Output: Request or Response


Input: [Added Table] Direct Deposit [Query Name] DIRECT_DEPOSIT [Parent Table]

Output: Employment


Input: [Added Table] General Comments [Query Name] GENL_COMMENT [Parent Table]

Output: Personal Data


Input: [Added Table] Pay Check Earns [Query Name] PAY_CHECK_EARNS [Parent Table]

Output: Pay Check


Input: [Added Table] Pay Distribution [Query Name] PAY_DISTRIBUTN [Parent Table]

Output: Pay Check


Input: [Added Table] Pay Tax [Query Name] PAY_TAX [Parent Table]

Output: Pay Check


Input: [Added Table] Pay Tax Distribution [Query Name] PAY_TAX_DIST [Parent Table]

Output: Pay Tax


Input: [Added Table] Position History EE Entry Dates [Query Name] POSN_HISTORY [Parent Table]

Output: Job


Input: [File Name] $Mft [MFT Record] 0 [Purpose of the File] Contains one base file record for each file and folder on an NTFS volume. If the allocation information for a file or folder is too large to fit within a single record, other file records are allocated as well. [System File]

Output: Master file table


Input: [File Name] $MftMirr [MFT Record] 1 [Purpose of the File] A duplicate image of the first four records of the MFT. This file guarantees access to the MFT in case of a single-sector failure. [System File]

Output: Master file table 2


Input: [File Name] $LogFile [MFT Record] 2 [Purpose of the File] Contains a list of transaction steps used for NTFS recoverability. Log file size depends on the volume size and can be as large as 4 MB. It is used by Windows NT/2000 to restore consistency to NTFS after a system failure. [System File]

Output: Log file


Input: [File Name] $Volume [MFT Record] 3 [Purpose of the File] Contains information about the volume, such as the volume label and the volume version. [System File]

Output: Volume


Input: [File Name] $AttrDef [MFT Record] 4 [Purpose of the File] A table of attribute names, numbers, and descriptions. [System File]

Output: Attribute definitions


Input: [File Name] $ [MFT Record] 5 [Purpose of the File] The root folder. [System File]

Output: Root file name index


Input: [File Name] $Bitmap [MFT Record] 6 [Purpose of the File] A representation of the volume showing which clusters are in use. [System File]

Output: Cluster bitmap


Input: [File Name] $Boot [MFT Record] 7 [Purpose of the File] Includes the BPB used to mount the volume and additional bootstrap loader code used if the volume is bootable. [System File]

Output: Boot sector


Input: [File Name] $BadClus [MFT Record] 8 [Purpose of the File] Contains bad clusters for the volume. [System File]

Output: Bad cluster file


Input: [File Name] $Secure [MFT Record] 9 [Purpose of the File] Contains unique security descriptors for all files within a volume. [System File]

Output: Security file


Input: [File Name] $Upcase [MFT Record] 10 [Purpose of the File] Converts lowercase characters to matching Unicode uppercase characters. [System File]

Output: Upcase table


Input: [File Name] $Extend [MFT Record] 11 [Purpose of the File] Used for various optional extensions such as quotas, reparse point data, and object identifiers. [System File]

Output: NTFS extension file


Input: [File Name] $Quota [MFT Record] 24 [Purpose of the File] Contains user assigned quota limits on the volume space. [System File]

Output: Quota management file


Input: [File Name] $ObjId [MFT Record] 25 [Purpose of the File] Contains file object IDs. [System File]

Output: Object Id file


Input: [File Name] $Reparse [MFT Record] 26 [Purpose of the File] This file contains information about files and folders on the volume include reparse point data. [System File]

Output: Reparse point file


Input: [Updated commands] ACISOUT [How changed] Saves SAT files as Version 7.0. [Description]

Output: Exports solid objects to an ACIS file.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] ADCENTER [How changed] Updated to support Section View and Detail View styles. [Description]

Output: Manages content.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] ARRAY [How changed] Displays contextual tab during array creation. [Description]

Output: Creates multiple copies of objects in a pattern.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] ARRAYEDIT [How changed] Path array automatically calculates the item count based on the item spacing and length of path curve. [Description]

Output: Edits multiple copies of objects in a pattern.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] ATTACH [How changed] Now attaches point clouds files (PCG and ISG). [Description]

Output: Allows the user to insert various file types as attachments or underlays into a DWG file.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] -ATTACH [How changed] Now attaches point clouds files (PCG and ISG). [Description]

Output: Allows the user to insert various file types as attachments or underlays into a DWG file from the command prompt.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] CLIP [How changed] Now creates clipping boundaries for point clouds. [Description]

Output: Allows the user to clip viewports, xrefs, DWF, DWFx and DGN underlays, PDF underlays and point clouds.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] -HATCHEDIT [How changed] Now allows multiple-hatch selection. [Description]

Output: Modifies an existing hatch object from command line.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] LIST [How changed] If the command window is not docked, displays object information in the extended command history. If the command window is docked, information is displayed in the text screen. [Description]

Output: Displays property data for selected objects.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] MLEADER [How changed] Now supports strikethrough formatting. [Description]

Output: Creates a line that connects annotation to a feature.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] MOVE [How changed] Now supports section view and detail view types. [Description]

Output: Displaces objects a specified distance in a specified direction.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] MTEDIT [How changed] Text style drop-down list display changed to show more options. [Description]

Output: Edits multiline text.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] MTEXT [How changed] Text style drop-down list display changed to show more options. [Description]

Output: Creates multiline text.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] POINTCLOUDINDEX [How changed] Supports additional types of scan files. [Description]

Output: Creates a point cloud (PCG or ISD) file from a scan file.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] PRESSPULL [How changed] Provides additional visual display support for the presspull operation. [Description]

Output: Dynamically modifies objects by extrusion and offset.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] PURGE [How changed] Now purges Detail View styles and Section View styles. [Description]

Output: Removes unused named items, such as block definitions and layers, from the drawing.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] -PURGE [How changed] Now purges Detail View styles and Section View styles. [Description]

Output: Removes unused named items, such as block definitions and layers, from the drawing.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] RENAME [How changed] Now supports renaming of Detail View styles and Section View styles. [Description]

Output: Changes the names of objects

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] -RENAME [How changed] Now supports renaming of Detail View styles and Section View styles. [Description]

Output: Changes the names of objects from command line.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] ROTATE [How changed] Now supports rotation of section views and detail views. [Description]

Output: Moves objects about a base point.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] STYLE [How changed] Text style drop-down list display changed to show more options. [Description]

Output: Creates named styles.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] TABLE [Description]

Output: Creates an empty table object in a drawing.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] TEXT [Description]

Output: Displays text on screen as it is entered.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] TEXTTOFRONT [How changed] Now supports leaders. [Description]

Output: Brings text and dimensions in front of all other objects in the drawing.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] UNDO [Description]

Output: Reverses the effect of commands.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] VIEWBASE [How changed] Supports the creation of drawing view objects from model space or Inventor models within a layout (paper space). [Description]

Output: Creates a base drawing view from model space or Autodesk Inventor models.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] VIEWEDIT [How changed] Supports the editing of drawing view objects regardless of type: base, projected, section and detail views. [Description]

Output: Edits an existing drawing view.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] VIEWPROJ [How changed] Now supports section and detail drawing view object types. [Description]

Output: Creates a projected view from an existing drawing view.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] VIEWSTD [Description]

Output: Configures the drafting standard used by new drawing views.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Updated commands] VIEWUPDATE [Description]

Output: Updates selected drawing views that have become out of date because the source model has changed.

JTB World Blog: AutoCAD 2013 Updated Commands


Input: [Unix] FILE [Description] The files to modify. [PowerShell]

Output: -filespec


Input: [Unix] -d [Description] Parse STRING and use it instead of current time. [PowerShell]

Output: -datetime


Input: [Unix] -F [Description] Modify the time by going forward SECONDS seconds. [PowerShell]

Output: -forward


Input: [Unix] -r [Description] Use this file as a reference instead of the current time. [PowerShell]

Output: -reference


Input: [Unix] -m [Description] Change only the modification time. [PowerShell]

Output: -only_modification


Input: [Unix] -a [Description] Change only the access time. [PowerShell]

Output: -only_access


Input: [Option] Message List [Description]

Output: Click Message List to return to the message folder last viewed when viewing different email page.


Input: [Option] Compose [Description]

Output: Click Compose to create and send emails.


Input: [Option] Refresh [Description]

Output: Click Refresh to reload this page and check for new emails.


Input: [Option] Folder Management [Description]

Output: The Folder Management icon takes you to a page where you can sort the messages you receive by saving them in folders you have created and organized.


Input: [Option] Settings [Description]

Output: Click Settings to open a page where you can customize your email, display, and forwarding options. From here you can also see and edit your IMAP information, if applicable.


Input: [Option] Switch to IMAP*/ Desire2Learn Mail (*IMAP-compliant systems) [Description]

Output: Use the Switch to IMAP icon to access your email from an IMAP server integrated with another email application.


Input: [Option] EPAL_NONE [Description]

Output: No locking to an axis.


Input: [Option] EPAL_X [Description]

Output: Lock the mesh X-axis facing towards +X.


Input: [Option] EPAL_Y [Description]

Output: Lock the mesh X-axis facing towards +Y.


Input: [Option] EPAL_Z [Description]

Output: Lock the mesh X-axis facing towards +Z.


Input: [Option] EPAL_NEGATIVE_X [Description]

Output: Lock the mesh X-axis facing towards -X.


Input: [Option] EPAL_NEGATIVE_Y [Description]

Output: Lock the mesh X-axis facing towards -Y.


Input: [Option] EPAL_NEGATIVE_Z [Description]

Output: Lock the mesh X-axis facing towards -Z.


Input: [Option] EPAL_ROTATE_X [Description]

Output: Ignored for mesh emitters. Treated as EPAL_NONE.


Input: [Option] EPAL_ROTATE_Y [Description]

Output: Ignored for mesh emitters. Treated as EPAL_NONE.


Input: [Option] EPAL_ROTATE_Z [Description]

Output: Ignored for mesh emitters. Treated as EPAL_NONE.


Input: [min] 00:00 [video details]

Output: video tutorial footer element HTML5


Input: [min] 00:01 [video details]

Output: footer element allows you to mark up a footer in your HTML5 document


Input: [min] 00:09 [video details]

Output: it can be the footer of your whole document IF the nearest ancestor of the footer element is the body element


Input: [min] 00:19 [video details]

Output: the footer of the whole document


Input: [min] 00:32 [video details]

Output: that's an article in page


Input: [min] 00:38 [video details]

Output: and that's the footer of the article the nearest ancestor of the footer element in this case is the article element


Input: [Description] Holds an entry [Class name]

Output: Entry


Input: [Description] Holds Entry objects [Class name]

Output: EntryCollection


Input: [Description] Represents a single user [Class name]

Output: Person


Input: [Description] Represents a group of users [Class name]

Output: Group


Input: [Description] Interface to abstract Person and Group [Class name]

Output: User


Input: [Description] Enumeration of the different user types [Class name]

Output: UserType


Input: [Description] Holds people who are included/excluded from viewing the entry [Class name]

Output: Permissions


Input: [Description] Just a method to implement that will return the XML format of the object [Class name]

Output: XMLAble


Input: [1] Enter [2]

Output: Select a group or object / move to location

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Backspace [2]

Output: Select previous group

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Tab [2]

Output: Focus on next dialogue element

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] SHIFT+Tab [2]

Output: Focus on previous dialogue element

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Esc [2]

Output: Quit moving towards destination / close dialogue

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F1 [2]

Output: Invoke online documentation for CityGuide-DMS

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F2 [2]

Output: Advanced object search

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F3 [2]

Output: Toggle fullscreen on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] CTRL+F3 [2]

Output: Toggle quickbar on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F4 [2]

Output: Save program preferences

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] CTRL+F4 [2]

Output: Reset program preferences

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F5 [2]

Output: Call the information for the current object (hyperlink)

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F6 [2]

Output: Display symbol functions

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F7 [2]

Output: Jump to target on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] SHIFT+F7 [2]

Output: Toggle elevation profile on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] CTRL+F7 [2]

Output: Jump to waypoint on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F8 [2]

Output: Display legend for current map

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F9 [2]

Output: Generate object-link for your personal homepage

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] CTRL+F9 [2]

Output: Send meeting point coordinates

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F11 [2]

Output: Toggle overview window on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] F12 [2]

Output: Memory-display on the map window on / off

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Left Arrow [2]

Output: Go West

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Right Arrow [2]

Output: Go East

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Up Arrow [2]

Output: Go North

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Down Arrow [2]

Output: Go South

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Page Up [2]

Output: Go North (Fast)

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Page Down [2]

Output: Go South (Fast)

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Pos 1 [2]

Output: Go West (Fast)

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] End [2]

Output: Go East (Fast)

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Plus (+) [2]

Output: Zoom in

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] Minus (-) [2]

Output: Zoom out

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] CTRL (+/-) [2]

Output: Select next/previous measuring function

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [1] SHIFT (+/-) [2]

Output: Select next/previous coordinate function

CityGuide DMS - Documentation - Keyboard & Mouse


Input: [Member Name] addField [Description]

Output: Adds a new INPUT field to the end of the form with the given attributes.

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] addValueArray [Description]

Output: This takes an array of strings and adds hidden elements for each one of them. Unlike setValue, it makes no attempt to find and modify existing elements in the form to the new values.

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] getField [Description]

Output: Gets the actual elements with the given name

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] getLabel [Description]

Output: Grabs the with the given for tag, if there is one.

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] getPostableData [Description]

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] getValue [Description]

Output: Gets the value of the field; what would be given if it submitted right now. (so it handles select boxes and radio buttons too). For checkboxes, if a value isn't given, but it is checked, it returns "checked", since null and "" are indistinguishable

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] removeField [Description]

Output: Removes the given field from the form. It finds the element and knocks it right out.

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Member Name] setValue [Description]

Output: Set's the form field's value. For input boxes, this sets the value attribute. For textareas, it sets the innerText. For radio boxes and select boxes, it removes the checked/selected attribute from all, and adds it to the one matching the value. For checkboxes, if the value is non-null and not empty, it checks the box. If you set a value that doesn't exist, it throws an exception if makeNew is false. Otherwise, it makes a new input with type=hidden to keep the value.

arsd.dom - D Programming Language - Digital Mars

Member Quick Reference


Input: [Name] AOUTL [Description]

Output: Left Lineout Amplifier

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] AOUTR [Description]

Output: Right Lineout Amplifier

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] SP [Description]

Output: Speaker Amplifier

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] BEEP [Description]

Output: Beep Signal Input

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] LMIC [Description]

Output: Left Microphone Input or Digital Microphone Input 1

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] RMIC [Description]

Output: Right Microphone Input or Digital Microphone Input 2

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Name] MICBIAS [Description]

Output: Bias Voltage for Electret Microphone

ADAU1781 Sound CODEC Linux Driver [Analog Devices Wiki]


Input: [Code] 200 [Text] OK [Description]

Output: Success!

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 400 [Text] Bad Request [Description]

Output: The request was invalid. In API v2.0, a request with invalid URL, invalid format or wrong parameter is considered invalid and you will get this response.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 401 [Text] Unauthorized [Description]

Output: API key is incorrect or is not activated.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 402 [Text] Payment Required [Description]

Output: Returned when user reached limit of scan requests quota. In order to continue using scan API a new key must be purchased.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 403 [Text] Forbidden [Description]

Output: The request is understood, but it has been refused or access is not allowed. In example it is returned when user with blacklisting plan privileges tries to scan a domain or delete the scan report.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 404 [Text] Not Found [Description]

Output: The URI requested is invalid or the resource requested, such as URL or Investigation Report does not exist.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 429 [Text] Too Many Requests [Description]

Output: Returned in API v2.0 when a request cannot be served due to the daily rate limit having been reached for the API key. Contact us for API Plans and Pricing.

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Code] 500 [Text] Internal Server Error [Description]

Output: Something is broken. Please post to the group or email the support

FREE Online Website Malware Scanner | Website Security Monitoring & Malware Removal | Quttera


Input: [Parameter] name [Explanation]

Output: Required. Unique identifier for the question

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] question [Explanation]

Output: Required. Question given interactively to a user when generating structure

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] default [Default] None [Explanation]

Output: Default value when no answer is given. Can be a dotted notation

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] required [Default] False [Explanation]

Output: Specify if question must be answered

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] command_prompt [Default] raw_input() [Explanation]

Output: Function that accepts a question and asks user for the answer

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] help [Default] “” [Explanation]

Output: Extra help returned when user inputs a question mark

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] pre_ask_question [Default] None [Explanation]

Output: dotted notation function to run before asking the question

Writing your own template — mr.bob 0.1a6 documentation


Input: [Parameter] post_ask_question [Default] None [Explanation]

Output: dotted notation function to run after asking the question (also does validation)

Writing your own template — mr.bob 0.1a6 documentation


Input: [Function] Auto-Litter turned on [Rake/Action] 1 complete sweep cycle [LED Response]

Output: Green Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Auto-Litter is on and idle [Rake/Action] In Home position [LED Response]

Output: Green Solid

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Detection sensors activate [Rake/Action] Not sweeping, not in Home position [LED Response]

Output: Red Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Obstruction detected [Rake/Action] Moving toward Home position (will sweep 6 times to dear) [LED Response]

Output: Red Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Obstruction detected, can not be deared by rake [Rake/Action] Home position. Turn the unit off, clear the obstruction, and turn the unit back on. [LED Response]

Output: Red On/Green On

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Cat detected in the box [Rake/Action] Not sweeping, in home position. Rake will sweep in 10 minutes. [LED Response]

Output: Green Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Performing standard sweep cycle [Rake/Action] Sweeping [LED Response]

Output: Green Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Function] Manual button [Rake/Action] 1 complete sweep cycle [LED Response]

Output: Green Flashing

Product Support for SweepOne™ Advanced Auto-Cleaning Litter Box System PAL00-13950 | PetSafe


Input: [Field Name] ID [Associated Filter] (none) [Description]

Output: An integer that will be used for updating an existing user.

Function Reference/wp update user « WordPress Codex

The $userdata array can contain the following fields


Input: [Field Name] user_pass [Associated Filter] pre_user_pass [Description]

Output: A string that contains the plain text password for the user.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] user_login [Associated Filter] pre_user_login [Description]

Output: A string that contains the user's username for logging in. Please note that the function cannot alter this field, since WordPress does not allow usernames to be changed.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] user_nicename [Associated Filter] pre_user_nicename [Description]

Output: A string that contains a URL-friendly name for the user. The default is the user's username.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] user_url [Associated Filter] pre_user_url [Description]

Output: A string containing the user's URL for the user's web site.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] user_email [Associated Filter] pre_user_email [Description]

Output: A string containing the user's email address.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] display_name [Associated Filter] pre_user_display_name [Description]

Output: A string that will be shown on the site. Defaults to user's username. It is likely that you will want to change this, for both appearance and security through obscurity (that is if you dont use and delete the default admin user).

Function Reference/wp update user « WordPress Codex


Input: [Field Name] nickname [Associated Filter] pre_user_nickname [Description]

Output: The user's nickname, defaults to the user's username.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] first_name [Associated Filter] pre_user_first_name [Description]

Output: The user's first name.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] last_name [Associated Filter] pre_user_last_name [Description]

Output: The user's last name.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] description [Associated Filter] pre_user_description [Description]

Output: A string containing content about the user.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] rich_editing [Associated Filter] (none) [Description]

Output: A string for whether to enable the rich editor or not. False if not empty.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] user_registered [Associated Filter] (none) [Description]

Output: The date the user registered. Format is Y-m-d H:i:s.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] role [Associated Filter] (none) [Description]

Output: A string used to set the user's role.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] jabber [Associated Filter] (none) [Description]

Output: User's Jabber account.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] aim [Associated Filter] (none) [Description]

Output: User's AOL IM account.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] yim [Associated Filter] (none) [Description]

Output: User's Yahoo IM account.

Function Reference/wp update user « WordPress Codex


Input: [Field Name] show_admin_bar_front [Associated Filter] (none) [Description]

Output: Show the WP admin bar on the front-end.

Function Reference/wp update user « WordPress Codex


Input: [File/Folder] config\database.yml [Purpose]

Output: This file is a YAML (stands for – YAML Ain’t a Markup Language) file. It contains details about your DBMS provider and the authentication details for your DBMS.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] config\routes.rb [Purpose]

Output: This is a ruby file. It allows you to configure how HTTP requests will be routed.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] app\controllers\ [Purpose]

Output: Contains controller files. Controllers are ruby files.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] app\helpers\ [Purpose]

Output: Contains helper files. Helper files are ruby files which are used to define logic which doesn’t belong in the model but is too long-winded to be embeded in the view.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] app\models\ [Purpose]

Output: Contains model files. Model files are ruby files. They inherit most of there functionality from ActiveRecord but you can also build upon this functionality by writing your own methods.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] app\views\ [Purpose]

Output: Contains a sub folder for each controller file that exists. For instance, if there is a controller called “posts_contoller.rb” there will be a view sub-folder called “posts”.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] public\images\ [Purpose]

Output: Contains any image files that belong to your website.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] public\javascripts\ [Purpose]

Output: Contains any javascript files that are used by your website.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] public\stylesheets\ [Purpose]

Output: Contains any CSS files that belong to your website.

How to Create a Blog from Scratch Using Ruby on Rails


Input: [File/Folder] db\migrate [Purpose]

Output: Contains “migration” files, used to migrate a database from one state to another (more on this later)

How to Create a Blog from Scratch Using Ruby on Rails


Input: [Value] CDATA [Explanation]

Output: The value is character data


Input: [Value] (eval|eval|..) [Explanation]

Output: The value must be an enumerated value


Input: [Value] ID [Explanation]

Output: The value is an unique id


Input: [Value] IDREF [Explanation]

Output: The value is the id of another element


Input: [Value] IDREFS [Explanation]

Output: The value is a list of other ids


Input: [Value] NMTOKEN [Explanation]

Output: The value is a valid XML name


Input: [Value] NMTOKENS [Explanation]

Output: The value is a list of valid XML names


Input: [Value] ENTITY [Explanation]

Output: The value is an entity


Input: [Value] ENTITIES [Explanation]

Output: The value is a list of entities


Input: [Value] NOTATION [Explanation]

Output: The value is a name of a notation


Input: [Value] xml: [Explanation]

Output: The value is predefined


Input: [Directory] / [Contents]

Output: Root directory—the starting point of the directory tree.


Input: [Directory] /bin [Contents]

Output: Essential binary files, such as commands that are needed by both the system administrator and normal users. Usually also contains the shells, such as Bash.


Input: [Directory] /boot [Contents]

Output: Static files of the boot loader.


Input: [Directory] /dev [Contents]

Output: Files needed to access host-specific devices.


Input: [Directory] /etc [Contents]

Output: Host-specific system configuration files.


Input: [Directory] /home [Contents]

Output: Holds the home directories of all users who have an account on the system. Only root's home directory is not located in /home but in /root.


Input: [Directory] /lib [Contents]

Output: Essential shared libraries and kernel modules.


Input: [Directory] /media [Contents]

Output: Mount points for removable media.


Input: [Directory] /mnt [Contents]

Output: Mount point for temporarily mounting a file system.


Input: [Directory] /opt [Contents]

Output: Add-on application software packages.


Input: [Directory] /root [Contents]

Output: Home directory for the superuser root.


Input: [Directory] /sbin [Contents]

Output: Essential system binaries.


Input: [Directory] /srv [Contents]

Output: Data for services provided by the system.


Input: [Directory] /tmp [Contents]

Output: Temporary files.


Input: [Directory] /usr [Contents]

Output: Secondary hierarchy with read-only data.


Input: [Directory] /var [Contents]

Output: Variable data such as log files.


Input: [Directory] /windows [Contents]

Output: Only available if you have both Microsoft Windows* and Linux installed on your system. Contains the Windows data.


Input: [Value] BOOL [Description] Yes: Send the route's advice (i.e. step by step instructions). Default: no [Mandatory] NO [Name]

Output: advice

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] BOOL [Description] Yes: Send the route's geometry as a list of GPS coordinates. Default: no [Mandatory] NO [Name]

Output: points

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] BOOL [Description] Yes: Send the list of countries traversed by the route. Each country is identified by its code: http://en.wikipedia.org/wiki/ISO_3166-1_alpha-2 Default: no [Mandatory] NO [Name]

Output: countries

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] TEXT [Description] The type of via points. All the via points will have the same type. Possible values: exact (default) – the via point's exact coordinate is used (i.e. the point is mapped on the street network, and the route will go through the position where the via points is mapped) [Mandatory] NO [Name]

Output: viaType

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] POINT [Description] GPS positions of via points: v0, v1, ..., v10. They are are read and used in the order of their number. The numbers do not have to be contiguous. For example there can be only v3 and v7, meaning that v3 is the first via point and v7 the second. Format: Latitude,Longitude. [Mandatory] NO [Name]

Output: v#

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] POINT [Description] Mercator positions of via points: vM0, vM1, ..., vM10. Same rules as for GPS via points. The combination of the two styles (GPS – mercator) is supported. However, if a via point number appears in both versions, the mercator version have priority. Format: Longitude, Latitude (aka X,Y), which is reversed when compared with v#! [Mandatory] NO [Name]

Output: vM#

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Value] BOOL [Description] Yes: Compute up to two alternates. Default: no [Mandatory] NO [Name]

Output: alternates

skobbler | SDK Web | Powerful maps technology based on OpenStreetMap | OSM


Input: [Option] domain [Default] Website domain [Description]

Output: Website hostname as added to Woopra


Input: [Option] cookie_name [Default] wooTracker [Description]

Output: Name of the cookie used to identify the visitor


Input: [Option] cookie_domain [Default] Website domain [Description]

Output: Domain scope of the Woopra cookie


Input: [Option] cookie_path [Default] / [Description]

Output: Directory scope of the Woopra cookie


Input: [Option] cookie_expire [Default] 2 years from last action [Description]

Output: Expiration date (Date object) of the Woopra cookie


Input: [Option] ping [Default] true [Description]

Output: Ping woopra servers to ensure that the visitor is still on the webpage


Input: [Option] ping_interval [Default] 12000 [Description]

Output: Time interval in milliseconds between each ping


Input: [Option] idle_timeout [Default] 300000 [Description]

Output: Idle time after which the user is considered offline


Input: [Option] download_tracking [Default] false [Description]

Output: Track downloads on the web page


Input: [Option] outgoing_tracking [Default] false [Description]

Output: Track external links clicks on the web page


Input: [Option] outgoing_ignore_subdomain [Default] true [Description]

Output: Do not include links to subdomains as outgoing links


Input: [Option] download_pause [Default] 200 [Description]

Output: Time in millisecond to pause the browser to ensure that the event is tracked when visitor clicks on a download url.


Input: [Option] outgoing_pause [Default] 400 [Description]

Output: Time in millisecond to pause the browser to ensure that the event is tracked when visitor clicks on an outgoing url.


Input: [Option] ignore_query_url [Default] true [Description]

Output: Ignores the query part of the url when the standard pageviews tracking function track()


Input: [Option] hide_campaign [Default] false [Description]

Output: Enabling this option will remove campaign properties from the URL when they’re captured (using HTML5 pushState).


Input: [Command] HELO (now EHLO) [Example] EHLO 193.56.47.125 [Description]

Output: Identification using the IP address or domain name of the originator computer

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Command] MAIL FROM: [Example] MAIL FROM: originator@domain.com [Description]

Output: Identification of the originator's address

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Command] RCPT TO: [Example] RCPT TO: recipient@domain.com [Description]

Output: Identification of the recipient's address

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Command] DATA [Example] DATA message [Description]

Output: Email body

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Command] QUIT [Example] QUIT [Description]

Output: Exit the SMTP server

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Command] HELP [Example] HELP [Description]

Output: List of SMTP commands supported by the server

Messaging protocols (SMTP,POP3 and IMAP4)


Input: [Name] clearText [Type] string [Default] 'Clear' [Comments]

Output: The text to display for the link to clear the input field and close the datepicker. Use the mandatory setting to control the link's presence.


Input: [Name] clearStatus [Type] string [Default] 'Erase the current date' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] closeText [Type] string [Default] 'Close' [Comments]

Output: The text to display for the link to close the datepicker without changing the field value.


Input: [Name] closeStatus [Type] string [Default] 'Close without change' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] prevText [Type] string [Default] ' [Comments]

Output: The text to display for the link to move to the previous month. Use the stepMonths setting to specify how many months to move at one time.


Input: [Name] prevStatus [Type] string [Default] 'Show the previous month' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] prevBigText [Type] string [Default] '<<' [Comments]

Output: The text to display for the link to move to the previous year. Use the stepBigMonths setting to specify how many months to move at one time and the showBigPrevNext setting to control its presence.


Input: [Name] prevBigStatus [Type] string [Default] 'Show the previous year' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] nextText [Type] string [Default] 'Next>' [Comments]

Output: The text to display for the link to move to the next month. Use the stepMonths setting to specify how many months to move at one time.


Input: [Name] nextStatus [Type] string [Default] 'Show the next month' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] nextBigText [Type] string [Default] '>>' [Comments]

Output: The text to display for the link to move to the next year. Use the stepBigMonths setting to specify how many months to move at one time and the showBigPrevNext setting to control its presence.


Input: [Name] nextBigStatus [Type] string [Default] 'Show the next year' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] currentText [Type] string [Default] 'Today' [Comments]

Output: The text to display for the link to show the month containing today. Use the gotoCurrent setting to show the month of the current selection instead.


Input: [Name] currentStatus [Type] string [Default] 'Show the current month' [Comments]

Output: The text to display in the datepicker's status bar for the above link.


Input: [Name] monthNames [Type] string[12] [Default] ['January', 'February', 'March', 'April', 'May', 'June', 'July', 'August', 'September', 'October', 'November', 'December'] [Comments]

Output: The names of the months. These are used for display in the month selection drop-down, as well as for formatting and parsing dates.


Input: [Name] monthNamesShort [Type] string[12] [Default] ['Jan', 'Feb', 'Mar', 'Apr', 'May', 'Jun', 'Jul', 'Aug', 'Sep', 'Oct', 'Nov', 'Dec'] [Comments]

Output: The abbreviated names of the months for formatting and parsing dates.


Input: [Name] monthStatus [Type] string [Default] 'Show a different month' [Comments]

Output: The text to display in the datepicker's status bar for the month selection drop-down. Use the changeMonth setting to allow the month to be changed with this drop-down.


Input: [Name] yearStatus [Type] string [Default] 'Show a different year' [Comments]

Output: The text to display in the datepicker's status bar for the year selection drop-down. Use the changeYear setting to allow the year to be changed with this drop-down.


Input: [Name] weekHeader [Type] string [Default] 'Wk' [Comments]

Output: The text to display in the header for the week-of-the-year column. Use the showWeeks setting to control this column's presence.


Input: [Name] weekStatus [Type] string [Default] 'Week of the year' [Comments]

Output: The text to display in the datepicker's status bar for the week-of-the-year column.


Input: [Name] dayNames [Type] string[7] [Default] ['Sunday', 'Monday', 'Tuesday', 'Wednesday', 'Thursday', 'Friday', 'Saturday'] [Comments]

Output: The names of the days, starting at Sunday. These are used for formatting and parsing dates and in various status bar messages.


Input: [Name] dayNamesShort [Type] string[7] [Default] ['Sun', 'Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat'] [Comments]

Output: The abbreviated names of the days, starting at Sunday. These are used for formatting and parsing dates and in various status bar messages.


Input: [Name] dayNamesMin [Type] string[7] [Default] ['Su','Mo','Tu','We','Th','Fr','Sa'] [Comments]

Output: The minimal names of the days for display as column headings. Use the firstDay setting to specify the first day of the week and the changeFirstDay setting to allow the user to change it themselves.


Input: [Name] dayStatus [Type] string [Default] 'Set DD as first week day' [Comments]

Output: The text to display in the datepicker's status bar for the day column headers. 'D' is replaced by the abbreviated day name and 'DD' is replaced by the full day name.


Input: [Name] dateStatus [Type] string [Default] 'Select DD, M d' [Comments]

Output: The text to display in the datepicker's status bar for the selectable days in a month. The formatDate function is applied to the text before display. This setting is used by the standard implementation (dateStatus) of the statusForDate callback.


Input: [Name] dateFormat [Type] string [Default] 'mm/dd/yy' [Comments]

Output: The format in which dates are presented in the input field. See the formatting possibilities in the formatDate function.


Input: [Name] firstDay [Type] number [Default] 0 [Comments]

Output: The first day of the week: 0 is Sunday, 1 is Monday, through to 6 is Saturday.


Input: [Name] initStatus [Type] string [Default] 'Select a date' [Comments]

Output: The text to display in the datepicker's status bar when no other status bar message applies.


Input: [Name] isRTL [Type] boolean [Default] false [Comments]

Output: Set to true to indicate that this localisation's language reads right-to-left. This affects the positioning of various elements as well as the text itself.


Input: [Name] showMonthAfterYear [Type] boolean [Default] false [Comments]

Output: Indicate whether the month drop-down should appear after (true) the year drop-down, or before it (false). Since 3.5.2 - moved to localisation settings.


Input: [Name] yearSuffix [Type] string [Default] '' [Comments]

Output: Text to append to the year in each month's header. Since 3.5.2.


Input: [Flag] passthrough [Default] N/A [Default Group*] All [Type] State [Description]

Output: Use allow to have this region treated as a region that doesn't check build permission (use this to make simple no-PVP, etc. zones).

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] build [Default] N/A [Default Group*] Non-Members [Type] State [Description]

Output: All members and owners will be able to build normally without changing this flag, do not change it. This flag overrides all region build checks. Deny always takes precedence over allow. If you simply want to protect a region, you don't have to touch this flag. By default no one can build in a region until you use addowner/addmember to add a player to the region.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] construct [Default] Members [Default Group*] N/A [Type] Group [Description]

Output: Deprecated. Don't use this flag at all. It's broken and should be considered deprecated.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] pvp [Default] Allowed [Default Group*] All [Type] State [Description]

Output: Allow or block PvP.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] mob-damage [Default] Allowed [Default Group*] All [Type] State [Description]

Output: Allow or block mob damage on players.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] entity-item-frame-destroy [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block non-player entities from destroying item-frames.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] entity-painting-destroy [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block non-player entities from destroying paintings.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] exp-drop [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block experience orbs from dropping.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] item-drop [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block items from being able to be dropped.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] mob-spawning [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or deny mobs spawning

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] creeper-explosion [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block creeper damage to terrain and players.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] other-explosion [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block all other explosions to terrain and players.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] enderman-grief [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or prevent endermen from picking up or placing blocks.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] enderpearl [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or prevent players from teleporting to or from regions using enderpearls.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] enderdragon-block-damage [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or prevent enderdragon damage to blocks.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] ghast-fireball [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block fireballs damage to terrain and players.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] sleep [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or block players from entering beds.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] tnt [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block TNT.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] lighter [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or block flint and steel.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] fire-spread [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block the spread of fire (requires high frequency flags to be on in configuration)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] lava-fire [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block whether lava can start fires (requires high frequency flags to be on in configuration)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] lightning [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block lightning striking at all in a region

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] chest-access [Default] Deny [Default Group*] Non-Members [Type] State [Description]

Output: Allow or block the player from opening chests, furnaces, and other containers in a region

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] pistons [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block piston activation

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] water-flow [Default] Allowed [Default Group*] State [Description]

Output: Allow or block flow of water. (requires high frequency flags to be on in configuration)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] lava-flow [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block flow of lava. (requires high frequency flags to be on in configuration)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] use [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or block the ability to use doors, buttons, pressure plates, levers, etc

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] vehicle-place [Default] Denied [Default Group*] Non-Members [Type] State [Description]

Output: Allow or block the ability to place vehicles

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] vehicle-destroy [Default] Denied [Default Group*] Non-Members [Type] State [Description]

Output: Allow or block the ability to remove vehicles

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] snow-fall [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block snow from forming in an area. Note that this will not block weather altogether, that can be done in the config.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] snow-melt [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block snow from melting in an area.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] ice-form [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block ice from forming in an area.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] ice-melt [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block ice from melting in an area.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] mushroom-growth [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block mushrooms from growing in an area.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] leaf-decay [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block leaves from decaying.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] grass-growth [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block grass from spreading to dirt.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] mycelium-spread [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block mycelium from spreading to dirt.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] vine-growth [Default] Allowed [Default Group*] N/A [Type] State [Description]

Output: Allow or block vines from growing.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] invincible [Default] None [Default Group*] All [Type] State [Description]

Output: Sets a temporary godmode on the player. This will also disable /god-mode if set to deny, unless the player has the worldguard.god.override-regions permission.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] entry [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or deny a group of players to enter an area

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] entry-group [Default] Non-members [Default Group*] N/A [Type] Group [Description]

Output: Removed. There is no longer a separate "entry-group" flag in new versions of WorldGuard. See Setting Groups for the replacement. In previous versions, this flag would set which players the entry flag applied to.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] exit [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or deny a group of players to leave an area

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] exit-group [Default] Non-members [Default Group*] N/A [Type] Group [Description]

Output: Removed. There is no longer a separate "exit-group" flag in new versions of WorldGuard. See Setting Groups for the replacement. In previous versions, this flag would set which players the exit flag applied to.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] greeting [Default] unset [Default Group*] All [Type] String [Description]

Output: Message to show a player when they enter a region. See String flag below for formatting.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] farewell [Default] unset [Default Group*] All [Type] String [Description]

Output: Message to show a player when they leave a region. See String flag below for formatting.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] notify-enter [Default] False [Default Group*] All [Type] Boolean [Description]

Output: Sends a message to players with the worldguard.notify permission when a player enters a region.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] notify-leave [Default] False [Default Group*] All [Type] Boolean [Description]

Output: Sends a message to players with the worldguard.notify permission when a player leaves a region.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] deny-spawn [Default] unset [Default Group*] N/A [Type] List [Description]

Output: Set mobs that can't spawn within the region. From console or ingame: /region flag [id] denyspawn Skeleton,Zombie,Creeper,etc . In config file: deny-spawn: [SKELETON, CREEPER, ZOMBIE, ETC]

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] heal-delay [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Set the time in seconds between heal-amount triggering

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] heal-amount [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Set the amount per heal time (see heal-delay)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] heal-min-health [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Minimum health the heal flags will drop a player to.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] heal-max-health [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Maximum health the heal flags will raise a player to. (a full bar is 20 hearts)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] feed-delay [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Set the time in seconds between feed-amount triggering

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] feed-amount [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Set the amount per hunger regen time (see feed-delay)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] feed-min-hunger [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Minimum hunger the feed flags will drop a player to.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] feed-max-hunger [Default] unset [Default Group*] N/A [Type] Integer [Description]

Output: Maximum hunger the feed flags will raise a player to. (a full bar is 20 food)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] teleport [Default] unset [Default Group*] N/A [Type] Location [Description]

Output: Defines the location /region teleport teleports you to.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] spawn [Default] unset [Default Group*] N/A [Type] Location [Description]

Output: Define the spawn of the region, use /region flag region x y z

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] price [Default] False [Default Group*] N/A [Type] Boolean [Description]

Output: Not Yet Implemented.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] buyable [Default] False [Default Group*] N/A [Type] Boolean [Description]

Output: Not Yet Implemented.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] allow-shop [Default] false [Default Group*] N/A [Type] State [Description]

Output: Sets a Region for ChestShop (dev.bukkit.org/bukkit-plugins/chestshop/)

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] blocked-cmds [Default] unset [Default Group*] N/A [Type] List [Description]

Output: Sets the commands that will be blocked inside the region

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] allowed-cmds [Default] unset [Default Group*] N/A [Type] List [Description]

Output: Sets the commands allowed in the region. If this is set (not empty) it will act like a whitelist and ONLY commands from this list will be allowed.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] send-chat [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Sets whether or not a player can send chat inside the region

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] receive-chat [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Sets whether or not a player can receive chat inside the region.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] game-mode [Default] unset [Default Group*] All [Type] Custom [Description]

Output: Sets the gamemode when a player enters a region. Can either be SURVIVAL, CREATIVE or ADVENTURE.

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Flag] potion-splash [Default] Allowed [Default Group*] Non-Members* [Type] State [Description]

Output: Allow or block splash effect from potion

WorldGuard/Regions/Flags - EngineHub.org Wiki


Input: [Symbol] node( ) [Matches]

Output: Any node


Input: [Symbol] text( ) [Matches]

Output: A text node


Input: [Symbol] element::foo [Matches]

Output: An element named foo


Input: [Symbol] foo [Matches]

Output: An element named foo


Input: [Symbol] attribute::foo [Matches]

Output: An attribute named foo


Input: [Symbol] @foo [Matches]

Output: An attribute named foo


Input: [Symbol] @* [Matches]

Output: Any attribute


Input: [Symbol] * [Matches]

Output: Any element


Input: [Symbol] . [Matches]

Output: This element


Input: [Symbol] .. [Matches]

Output: The parent element


Input: [Symbol] / [Matches]

Output: The root node


Input: [Symbol] /* [Matches]

Output: The root element


Input: [Symbol] //foo [Matches]

Output: An element foo at any level


Input: [Mouse] Mouse movement [Keyboard] Cursor arrows [Action]

Output: Move ship

Scum of the Universe - space shooter and strategy game


Input: [Mouse] Left mouse button [Keyboard] Space [Action]

Output: Vertical proton fire

Scum of the Universe - space shooter and strategy game


Input: [Mouse] Right mouse button [Keyboard] Left CTRL [Action]

Output: Spread proton fire

Scum of the Universe - space shooter and strategy game


Input: [Mouse] Middle mouse button [Keyboard] Left ALT [Action]

Output: Plasma wave

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] D [Action]

Output: Space grenade

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] F [Action]

Output: Stinger rocket

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] H [Action]

Output: Hyperspace Jump

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] ESC [Action]

Output: Show galaxy map while in game

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] TAB [Action]

Output: Toggle in-game stats

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] P [Action]

Output: Pause game

Scum of the Universe - space shooter and strategy game


Input: [Mouse] - [Keyboard] F12 [Action]

Output: Screenshot

Scum of the Universe - space shooter and strategy game


Input: [Tag Name] assetic.asset [Usage]

Output: Register an asset to the current asset manager

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.factory_worker [Usage]

Output: Add a factory worker

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.filter [Usage]

Output: Register a filter

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.formula_loader [Usage]

Output: Add a formula loader to the current asset manager

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.formula_resource [Usage]

Output: Adds a resource to the current asset manager

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.templating.php [Usage]

Output: Remove this service if PHP templating is disabled

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] assetic.templating.twig [Usage]

Output: Remove this service if Twig templating is disabled

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] auto_alias [Usage]

Output: Define aliases based on the value of container parameters

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] console.command [Usage]

Output: Add a command

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] data_collector [Usage]

Output: Create a class that collects custom data for the profiler

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] doctrine.event_listener [Usage]

Output: Add a Doctrine event listener

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] doctrine.event_subscriber [Usage]

Output: Add a Doctrine event subscriber

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] form.type [Usage]

Output: Create a custom form field type

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] form.type_extension [Usage]

Output: Create a custom "form extension"

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] form.type_guesser [Usage]

Output: Add your own logic for "form type guessing"

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] kernel.cache_clearer [Usage]

Output: Register your service to be called during the cache clearing process

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] kernel.cache_warmer [Usage]

Output: Register your service to be called during the cache warming process

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] kernel.event_listener [Usage]

Output: Listen to different events/hooks in Symfony

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] kernel.event_subscriber [Usage]

Output: To subscribe to a set of different events/hooks in Symfony

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] kernel.fragment_renderer [Usage]

Output: Add new HTTP content rendering strategies

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] monolog.logger [Usage]

Output: Logging with a custom logging channel

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] monolog.processor [Usage]

Output: Add a custom processor for logging

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] routing.loader [Usage]

Output: Register a custom service that loads routes

The Dependency Injection Tags (The Symfony Reference)


Input: [Tag Name] routing.expression_language_provider [Usage]

Output: Register a provider for expression language functions in routing

The Dependency Injection Tags (The Symfony Reference)