Chapter 6. Notes

FAQ - Frequently Asked Questions

There is a FAQ article upon the website that should contain the answers to the most common questions that one might have about Macrotone Joomla Audit and it's usage. If you cannot find what you seek here you may contact us by raising a forum entry. In addition this document is presented as Web pages and as a downloadable PDF file.

We produce a few of the expected common question below:

  • How does Change History know when my data has been changed?

    The feature captures the information passed to the database when the record is inserted, updated or deleted from the database. The specific trigger performs the action without any other involvement.

  • What versions of Joomla! are supported?

    Currently release version 1.1.0 is thoroughly tested on Joomla! versions 3.4.3. Joomla 3.4.3 or above recommended.

  • What versions of database are supported?

    Currently only MySQL databases are supported, which is the most commonly used Joomla database.

  • Do I have to make any changes to my version of Joomla to make the feature work?

    The component options provided enable one to control which tables and which triggers it is required to create for the specified table. Configuration consists of creating the triggers and apply them from the Triggers panel within the administration component.

  • What information is captured by the feature?

    Change History captures information for each row that is inserted, updated, or deleted. For each table field that is audited, the before and after values of the column are stored, as well as:

    The username of the person who made the change. (Where determinable.)

    The date and time of the change.

    The alias of the record (if present).

    The primary key (row id) in the SQL query form.

    After values are present only for update and insert operations.

    Before values are present only for update and delete operations.

  • Where is the change history data stored?

    Change History data is stored within a specific table created by the component. This table is installed in the same database being used by Joomla itself. This table is fully queryable via SQL or other data access tools.

    Macrotone Joomla Audit provides an administrator (back end) display view which makes it easy for an administrator to look through the audit log records. One can filter and sort the change history records by audited table and change type.

  • I don't want to audit everything in my database, just certain selected areas. What control do I have over what is audited?

    You have complete control over which tables are audited. One would be wise to carefully consider your specific audit requirements, because the more tables that are audited, the more space your change history table will occupy and the more activity the database server will have to bear to perform the auditing.

  • In some cases, I only care about changes to existing data, not new data or deleted data. Do I have to audit all transactions on a given table?

    No. You can choose any combination of the insert, update, or delete operations, and you can change this selection table-by-table. For example, some tables might audit all three operations while others may only audit update operations.

Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries