Source for file interface.php
Documentation is available at interface.php
* @package FrameworkOnFramework
* @copyright Copyright (C) 2010 - 2012 Akeeba Ltd. All rights reserved.
* @license GNU General Public License version 2 or later; see LICENSE.txt
// Protect from unauthorized access
* Part of the FOF Platform Abstraction Layer. It implements everything that
* depends on the platform FOF is running under, e.g. the Joomla! CMS front-end,
* the Joomla! CMS back-end, a CLI Joomla! Platform app, a bespoke Joomla!
* Platform / Framework web application and so on.
* This is the abstract class implementing some basic housekeeping functionality
* and provides the static interface to get the appropriate Platform object for
* use in the rest of the framework.
* @package FrameworkOnFramework
* Set the error Handling, if possible
* @param integer $level PHP error level (E_ALL)
* @param string $log_level What to do with the error (ignore, callback)
* @param array $options Options for the error handler
* Returns the ordering of the platform class. Files with a lower ordering
* number will be loaded first.
* Is this platform enabled? This is used for automatic platform detection.
* If the environment we're currently running in doesn't seem to be your
* platform return false. If many classes return true, the one with the
* lowest order will be picked by FOFPlatform.
* Returns the base (root) directories for a given component. The
* "component" is used in the sense of what we call "component" in Joomla!,
* "plugin" in WordPress and "module" in Drupal, i.e. an application which
* is running inside our main application (CMS).
* The return is a table with the following keys:
* * main The normal location of component files. For a back-end Joomla!
* component this is the administrator/components/com_example
* * alt The alternate location of component files. For a back-end
* Joomla! component this is the front-end directory, e.g.
* * site The location of the component files serving the public part of
* * admin The location of the component files serving the administrative
* part of the application.
* All paths MUST be absolute. All four paths MAY be the same if the
* platform doesn't make a distinction between public and private parts,
* or when the component does not provide both a public and private part.
* All of the directories MUST be defined and non-empty.
* @param string $component The name of the component. For Joomla! this
* is something like "com_example"
* @return array A hash array with keys main, alt, site and admin.
* Return a list of the view template paths for this component. The paths
* are in the format site:/component_name/view_name/layout_name or
* admin:/component_name/view_name/layout_name
* The list of paths returned is a prioritised list. If a file is
* found in the first path the other paths will not be scanned.
* @param string $component The name of the component. For Joomla! this
* is something like "com_example"
* @param string $view The name of the view you're looking a
* @param string $layout The layout name to load, e.g. 'default'
* @param string $tpl The sub-template name to load (null by default)
* @param boolean $strict If true, only the specified layout will be
* searched for. Otherwise we'll fall back to
* the 'default' layout if the specified layout
public function getViewTemplatePaths($component, $view, $layout =
'default', $tpl =
null, $strict =
false);
* Get application-specific suffixes to use with template paths. This allows
* you to look for view template overrides based on the application version.
* @return array A plain array of suffixes to try in template names
* Return the absolute path to the application's template overrides
* directory for a specific component. We will use it to look for template
* files instead of the regular component directorues. If the application
* does not have such a thing as template overrides return an empty string.
* @param string $component The name of the component for which to fetch the overrides
* @param boolean $absolute Should I return an absolute or relative path?
* @return string The path to the template overrides directory
* Load the translation files for a given component. The
* "component" is used in the sense of what we call "component" in Joomla!,
* "plugin" in WordPress and "module" in Drupal, i.e. an application which
* is running inside our main application (CMS).
* @param string $component The name of the component. For Joomla! this
* is something like "com_example"
* By default FOF will only use the Controller's onBefore* methods to
* perform user authorisation. In some cases, like the Joomla! back-end,
* you alos need to perform component-wide user authorisation in the
* Dispatcher. This method MUST implement this authorisation check. If you
* do not need this in your platform, please always return true.
* @param string $component The name of the component.
* @return boolean True to allow loading the component, false to halt loading
* This method will try retrieving a variable from the request (input) data.
* If it doesn't exist it will be loaded from the user state, typically
* stored in the session. If it doesn't exist there either, the $default
* value will be used. If $setUserState is set to true, the retrieved
* variable will be stored in the user session.
* @param string $key The user state key for the variable
* @param string $request The request variable name for the variable
* @param FOFInput $input The FOFInput object with the request (input) data
* @param mixed $default The default value. Default: null
* @param string $type The filter type for the variable data. Default: none (no filtering)
* @param boolean $setUserState Should I set the user state with the fetched value?
* @return mixed The value of the variable
public function getUserStateFromRequest($key, $request, $input, $default =
null, $type =
'none', $setUserState =
true);
* Load plugins of a specific type. Obviously this seems to only be required
* @param string $type The type of the plugins to be loaded
* Execute plugins (system-level triggers) and fetch back an array with
* @param string $event The event (trigger) name, e.g. onBeforeScratchMyEar
* @param array $data A hash array of data sent to the plugins as part of the trigger
* @return array A simple array containing the resutls of the plugins triggered
* Perform an ACL check. Please note that FOF uses by default the Joomla!
* CMS convention for ACL privileges, e.g core.edit for the edit privilege.
* If your platform uses different conventions you'll have to override the
* FOF defaults using fof.xml or by specialising the controller.
* @param string $action The ACL privilege to check, e.g. core.edit
* @param string $assetname The asset name to check, typically the component's name
* @return boolean True if the user is allowed this action
public function authorise($action, $assetname);
* @param integer $id The user ID to load. Skip or use null to retrieve
* the object for the currently logged in user.
* @return JUser The JUser object for the specified user
public function getUser($id =
null);
* Returns the JDocument object which handles this component's response. You
* may also return null and FOF will a. try to figure out the output type by
* examining the "format" input parameter (or fall back to "html") and b.
* FOF will not attempt to load CSS and Javascript files (as it doesn't make
* sense if there's no JDocument to handle them).
* Is this the administrative section of the component?
* Is this the public section of the component?
* Is this a component running in a CLI application?
* Is AJAX re-ordering supported? This is 100% Joomla!-CMS specific. All
* other platforms should return false and never ask why.
* Performs a check between two versions. Use this function instead of PHP version_compare
* so we can mock it while testing
* @param string $version1 First version number
* @param string $version2 Second version number
* @param string $operator Operator (see version_compare for valid operators)
public function checkVersion($version1, $version2, $operator);
* Saves something to the cache. This is supposed to be used for system-wide
* FOF data, not application data.
* @param string $key The key of the data to save
* @param string $content The actual data to save
* @return boolean True on success
public function setCache($key, $content);
* Retrieves data from the cache. This is supposed to be used for system-side
* FOF data, not application data.
* @param string $key The key of the data to retrieve
* @param string $default The default value to return if the key is not found or the cache is not populated
* @return string The cached value
public function getCache($key, $default =
null);
* Clears the cache of system-wide FOF data. You are supposed to call this in
* your components' installation script post-installation and post-upgrade
* methods or whenever you are modifying the structure of database tables
* accessed by FOF. Please note that FOF's cache never expires and is not
* purged by Joomla!. You MUST use this method to manually purge the cache.
* @return boolean True on success
* Is the global FOF cache enabled?
* @param array $authInfo authentification information
* @return boolean True on success
* @return boolean True on success
Documentation generated on Tue, 19 Nov 2013 15:05:49 +0100 by phpDocumentor 1.4.3