No Tracking Record

7 years 9 months ago #1 by infollec
No Tracking Record was created by infollec
Hi,

I just discovered this extension and installed it.

After installation, I tried to modify some menu item title and article contents. But it shows no tracking records when I checked the tracking page after those modifications. Any possible configuration steps I've been missing?

Thank you.

Please Log in or Create an account to join the conversation.

7 years 9 months ago - 7 years 9 months ago #2 by chrisc
Replied by chrisc on topic No Tracking Record
You have not provided me with much information to go on, so forgive me if this seems simplistic. I will assume that you have read and understand the documentation on the extension provided on this web site.

Having installed the extension, did you create one (or more) triggers upon the underlying database Joomla menu tables? Auditing is not used automatically since it can in extreme cases generate a heavy load upon the database. Usually the need is to audit one (or possibly more) specific tables for change activity, hence the need to create the specific database triggers you need on the tables of interest. Some database knowledge is of course required.

You mention modifying a menu item (and an article), so can I assume that you have created 'UPDATE' triggers?
Is the trigger monitoring all of the table columns or more specifically the columns modified by your menu item update, and article update?
Having created the trigger is it enabled? If it is not enabled it will not have been created in the database.
If enabled can you please confirm whether the trigger exists in the database upon the 'menu and article (contents) tables' using 'phpmyadmin' (or similar)?

My suspicion based on the little information provided is that: an UPDATE trigger has not been generated or enabled upon the database Joomla menu and content tables..

System information, particularly MySQL version would possible also be useful.

Regards

If you are using our extensions please leave a review at the JED: IP Mapping | Issue Tracker | JAudit | Password Control

Please Log in or Create an account to join the conversation.

7 years 9 months ago #3 by infollec
Replied by infollec on topic No Tracking Record
Hi chrisc,

Thank you for your very quick, detail and concerning reply.

I think the main cause is I didn't create the triggers. Can you show me how to do that? Again thanks a lot.

Please Log in or Create an account to join the conversation.

7 years 9 months ago - 7 years 9 months ago #4 by chrisc
Replied by chrisc on topic No Tracking Record
The best place to start is as described in the documentation.

Basically you need to go into the back end and into the Triggers view to start creating a trigger. You select the table to create the trigger upon and the type of trigger required. There are three possible types, INSERT, UPDATE and DELETE and all work upon where the appropriate type of action occurs in the database. All three may exist upon a table, depending upon your audit requirements. When you initially create a trigger it create the trigger code assuming all table columns are to be 'audited'. You can modify these after the initial trigger creation and you then need to enable it for it to get created in the database. Once initially created a few additional fields will be visible in the trigger view for the trigger to be easily modified.

Any database table can have each of the three trigger types and these can be used either BEFORE the database change occurs or AFTER the database change occurs. This has auditing implications the first showing changes before they are changed in the database, and the later after they have occurred in the database. One cannot assume that a BEFORE trigger audit record has actually occurred in the database!. This is because some other database condition may have prevented the action occurring. i.e. a bad value trying to be inserted. The audit record is only reported what is being 'saved/changed' it is not checking in any way that the values are correct, which is obviously something that the 'other component' is determining. This is all standard 'database stuff' which you may be already aware of.

The component does assume that you have some database knowledge to understand the concept of database triggers, but simplifies the creation of the triggers. Disabling the trigger removes it from the database. This because MySQL does not allow disabled triggers in the database.

One warning though, it is important that you consider which tables and columns you wish to audit, since there will be a lot of audit records created if the tables being audited are heavily used and the database can grow very quickly, which if this is a 'hosted' site may cause storage problems. Use with discretion. I strongly suggest you study the documentation since it is a quite specialised component used for a very specific 'auditing' purpose. i.e. Who is changing what and when in the database. Often it will report that it is the 'Joomla' system user that is making the change, since the database will not have been provided with details of the user that the Joomla component is making the change for. This is not a problem with the component but as a result of the way in which Joomla components are designed. If the database has a means of knowing the 'information' it will report it.

Regards

If you are using our extensions please leave a review at the JED: IP Mapping | Issue Tracker | JAudit | Password Control
The following user(s) said Thank You: infollec

Please Log in or Create an account to join the conversation.

7 years 9 months ago #5 by infollec
Replied by infollec on topic No Tracking Record
Yes! Your explanation very detail and helpful!

Please Log in or Create an account to join the conversation.

7 years 9 months ago #6 by infollec
Replied by infollec on topic No Tracking Record
Solved

Please Log in or Create an account to join the conversation.

Time to create page: 0.738 seconds
Go To Top

Joomla! Debug Console

Session

Profile Information

Memory Usage

Database Queries