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
Issue Tracker Guide :: Checked Out State

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

Checked Out State

Issue Tracker makes use of the ability of Joomla to control multi-user access on records. In our component we control all of the records types (issues, people, projects, priorities, statuses, issue types and roles). When a User edit an item, Joomla! changes the item's status to Checked Out (represented by the padlock icon). The record is locked and only the User who has checked it out can modify it. This is a safety/security feature that prevents two Users from editing an Item at the same time, thus preventing the loss of any data upon saving.

An Issue Tracker Item remains "Checked Out" until the User clicks Apply, Save, or Cancel while editing it. Once saved, the Issue Tracker Item is Checked In. However, if there's a connection error, such as when the User presses the browser's Back icon, or they choose another Issue Tracker Item without saving or cancelling the work in progress, the Issue Tracker Item remains Checked Out. This means no one else can edit it.

Using the Global Checkin can be used to unlock all Items that are currently Checked Out, or depending on the items marked only the specific item groups, across the whole site. It can only be performed by a Super administrator. The action commences as soon as the Issue Tracker Item is clicked.

WARNING:  Performing a Global Checkin while Issue Tracker items are open for editing will result in data loss. All Checked Out Items will be checked in, and any unsaved changes will be lost.

When an issue is editing within the front end of the site, it also will create a ‘lock’ upon the issue so that it is evident in the back end that it is being edited. In the normal course of events where the issue is saved or cancelled the lock is automatically released. Occasionally situations may occur where a lock is retained even when the user editing the session is no longer logged into the system. In these rare situations the lock can be released either with the Issue Tracker issue list or from the Global Checkin.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries