Version Pre 1.7.0 Build 6998 -- Reset Filter on Audit Logs

[Palmertree]

If an Administrator puts a filter on the audit logs, the filter will never go away unless you delete the session profile key in the database for the user. If the admin does a reset everything is shown. But, if the admin goes to another menu task and comes back to the audit menu the filter is back again. Even if the administrator applies an "ALL" filter it still comes back.

For example:

Goto

"Administration" -> "Audit"

Expand "Filter"
Action = "Add"
Resource = "User"

Select the "Filter" Button

Everything is filtered as designed.

Now, select the "Reset" button.

Everything is reset and shown as designed.

Go to "Administration" -> "Users"
Then go back to "Administration" -> "Audit" and the filter User and Add is back and will not go away.

[Aly]

Will check it, thank you.

[Palmertree]

Thanks.

[Aly]

Fixed in rev. 7008

[Palmertree]

Thank you for the quick fix. I will test and report my results.

[Palmertree]

Tried Revision 7008 and it seems to still be broken. I flushed my cache and everything.

Also, SDI debug info was still turned on for the audit.php page in revision 7008.

Thanks in advance.

[Aly]

Sorry for the Debug info But I don't see the problem any more.. Try deleting from profiles idx="web.audit.filter.action"

[Palmertree]

I truncated the profiles table and still see the issue. I will do some more debugging on my end. Probably something I am doing wrong.

[Palmertree]

This is strange. If I truncate the profiles table, then go to audit and put a filter on "Login" and "User" and then do a reset and leave audit and then come back it selects "Add" and "User". Must be something on my end. Here is my profile after doing all the above.

profileid                  userid                     idx                                 idx2   source   value_id  value_int  value_str   type
100100020111582    100000000000003    web.audit.filter.state    0        0    1        2
100100020111583    100000000000003    web.audit.filter.userid    0        0    0        1
100100020111584    100000000000003    web.audit.filter.action    0        0    0        2
100100020111585    100000000000003    web.audit.filter.resourcetype    0        0    0        2
100100020111586    100000000000003    web.audit.filter.timesince    0        0    0        2
100100020111587    100000000000003    web.audit.filter.timetill    0        0    0        2

[Palmertree]

Found the issue. It was a problem on my end. Wanted to report what I found incase anyone else has the same problem. My value_int and type was set to unassigned in the database schema so that everytime "-1" was trying to be inserted, 0 was. After, changing them to unassigned, Aly's code fixed work perfectly. Thanks Aly.

The schema in create/schema/mysql.sql is correct but for some reason my install had value_int and type unassigned integers.

Time for me to go and check the schema on the rest of my other tables for value type of intergers to be sure they are right as well.

create/schema/mysql.sql

CREATE TABLE profiles (
        profileid               bigint unsigned         DEFAULT '0'     NOT NULL,
        userid          bigint unsigned         DEFAULT '0'     NOT NULL,
        idx             varchar(96)             DEFAULT ''      NOT NULL,
        idx2            bigint unsigned         DEFAULT '0'     NOT NULL,
        value_id                bigint unsigned         DEFAULT '0'     NOT NULL,
        value_int               integer         DEFAULT '0'     NOT NULL,
        value_str               varchar(255)            DEFAULT ''      NOT NULL,
        source          varchar(96)             DEFAULT ''      NOT NULL,
        type            integer         DEFAULT '0'     NOT NULL,
        PRIMARY KEY (profileid)
) type=InnoDB;

[Aly]

You're welcome