Deprecated: Joomla\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 41

Deprecated: Return type of Joomla\Input\Input::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /homepages/13/d380392445/htdocs/Jlive/libraries/vendor/joomla/input/src/Input.php on line 170

Deprecated: Joomla\CMS\Input\Input implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Input.php on line 31

Deprecated: Joomla\CMS\Input\Cookie implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Cookie.php on line 21

Deprecated: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Uri/Uri.php on line 141
IP Mapping :: Chapter 5. Cron tasks

Deprecated: F0FInput implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/f0f/input/input.php on line 35

Deprecated: Joomla\CMS\Input\Files implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in /homepages/13/d380392445/htdocs/Jlive/libraries/src/Input/Files.php on line 21

Chapter 5. Cron tasks

Cron is basically a time-based job scheduler that runs in the background on UNIX systems. Typically a task requiring repetitive actions to be carried out on a regular (pre-determined) basis would be ideal candidates for using cron.

Joomla systems can offer a number of different mechanisms to perform repetitive actions. The one that is best for any given site is very dependant upon the facilities offered by the hosting supplier.

Pseudo-cron

Plugin capture

It is possible to make use of a ‘bespoke’ plugin which can be invoked when someone accesses one or more pages upon a site and performs some predefined tasks. This is not really a 'real' cron since there is no possible way in which one can guarantee that there would be a site visitor at any predetermine time, and it has an unavoidable side effect of slowing the site access for the specific visitor that happen to visit the site at or immediately after the desired time. For this reason we have not implemented such a mechanism, however for some other ‘short’ running tasks it might be suitable, so although not suitable for our implementation it may in some circumstances provide a reasonable solution.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries