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
Joomla Audit :: Determining who changed a record.

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

Determining who changed a record.

The way in which it is possible to determine who changed a record is very dependant upon the structure of the specific table. Some Joomla tables possess specific fields to hold this information. These fields are typically named 'created_by' and 'modified_by'. If a table has these fields, which can be determined from inspection of the drop down columns when the trigger is created, it is advantageous to select these columns along with other monitors columns to capture the information they contain.

Another mechanism used by some Joomla table is the 'checked_out' field. When present, when a table is modified the table is first 'checked out' when the record is changed and then 'checked in' when the record is saved.

[Note]Note

When a Joomla table makes use of the checkin/checkout feature additional records will be created in the change history table if these columns are monitored. The reason is that immediately before an record is edited, the record is 'checked out' from the database this triggering a record change. The user then edits the record and saves the result, triggering another database change record being created. Then Joomla itself performs a 'check in' operation in turn triggering another record being created in the change history table.

[Important]Important

Some Joomla tables do not contain any information that enables an easy way to determine who has made a change. Attempts to determine whether a link exists between the information contained within the Joomla session table and the database (MySQL) session information has not indicated that the information is stored in a conveniently accessible manner.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries