Category: Logs (system & action)

Tiki v8.3

When attempting to sort the Tiki logs by either Id or Message, the lines do not sort as expected. The actual order appears to be random, regardless of the requested sort direction (ASC or DESC.)

This tracker is made to help filtering and sorting the features vs categories vs options we need to tag a bug/regression/wish with.

It happens, when multibyte strings is recording to database.
Function "substr" work incorrect with multibytes string.

System environment:
Tiki 6
Windows Server 2008 64bit
Apache x64 2.2.11
PHP x64 5.2.5 (lib/smarty/libs/internals/core.is_secure.php patched to make it work)

LDAP authentication against AD does work once configured properly
BUT
Debugging the configuration was hard because turning on logging caused errors!
When logging is off, all is well. When logging is on and line 346 of lib/auth/ldap.php is commented out, all is well.
It seems that when logging is active, "$filter->asString()" on that line causes an error on our system. The same call is made on line 262 with a simpler filter and works OK.

Perhaps when checking groups, asString is returning too much for the logging system to handle?

The function -+\UsersLib::assign_user_to_group+- currently does not log the group joining event (or leaving).

It should.

See other missing log events on the related wish.

I tested Trunk on my Ipad (IOS11 Safari).
The login popup for a default install is outside the screen (landscape and portrait).

If I select the option to use facebook as a login feature, and have Social Networks DISABLED, the facebook icon appears under the login popup box and when clicked fails in an error.

I would expect the checkbox under social networks "enable social networks" to disable sub-options, regardless of checked status.

After upgrading from 1.9.11 to 2.4 the links in last action log are all linking to tiki-index.php.

In the old system everything is working fine.

Most PHP errors are handled by initlib.php's tiki_error_handling(). This function was added by mose in {commit id=7041} (and completed in {commit id=7086}) to implement the "Show PHP error messages" button at the bottom of pages and have errors grouped rather than all over the place. Unfortunately, when a callback set with set_error_handler() does not return false, it also bypasses the default error handler, which may log errors. This means that no matter how PHP is configured, nor how Tiki is configured, errors triggered after lib/setup/error_reporting.php ran are not logged.

Pivottable allows to use activitystream as source data.

This offers the field modification date (day)
Pivottable usually wants to aggregate data for charts or tables to be meaningful, and that requires the aggregation of single data points overt common time frames: weeks, months, etc

It would be very useful if there was some way to let the user display activity stream data over weeks, months, etc.

With tracker data, you can do a workaround with a mathematical calculation field and using the Calculation syntax to get the week or month from a date field, etc. But with activity stream, I don't get how to achieve that.

This is going to be very useful for Tiki site admins to find insights on how their users are makeing use of their tiki sites over time.

Reproduced here:
http://xavi-9794-6803.show2.tikiwiki.org/tiki-index.php?page=Profile_Activity_Stream
u: admin
p: 12345

I am using Tiki v13 connected to LDAP

I logged in with testeinternet (new user from AD), and the Tiki user was successfully created after LDAP import.
I logged in with admin(tiki user)
added testeinternet to LAB group (here is the error the user that was logged for this action was testeinternet and not admin, as you can see in log id 685)

Logs from Action Logs
---
686 login 17:03 admin logged out 127.0.0.1 Mozilla/5.0 (Windows NT...
685 admingroups 17:03 testeinternet added testeinternet to LAB 127.0.0.1 Mozilla/5.0 (Windows NT...
684 admingroups 17:03 admin created group LAB 127.0.0.1 Mozilla/5.0 (Windows NT...
683 login 17:02 admin logged from http://localhost/tiki/tiki-index.php 127.0.0.1 Mozilla/5.0 (Windows NT...
682 login 17:02 testeinternet logged out 127.0.0.1 Mozilla/5.0 (Windows NT...
681 login 17:02 testeinternet logged from http://localhost/tiki/tiki-index.php 127.0.0.1 Mozilla/5.0 (Windows NT...
---

The action log is almost unusable so it needs a major revamp.

Ideally the log data should be indexed in the unified search index (or maybe a separate one like the prefs?) and the search should be something like a custom search page where you can filter by date range, user, category (section) etc.

Might be good for a medium-newbie dev as it couldn't really be much worse!

Also, the log calendar needs reinstating, probably (was disabled as became totally broken after full-calendar took over)

Record Calendar-related actions at the Action log

It's currently now possible through the ((doc:Action Log)) to display ((doc:Calendar)) actions, since they seem not to be recorded.

Calendar is buggy in some edge cases, and recods in the action log would help to find out when the issues happen.

If you want a tiki with calendars and action log setup already for your, see this:
http://xavi-9794-5877.show.tikiwiki.org/tiki-admin_actionlog.php
u: admin
p: 12345

{syntax type="tiki" editor="plain"}
At tiki-syslog.php it is possible to delete older logs by using the field "Clean logs older than".
This field is expecting a numeric value (the number of month) but it is possible to type anything, even text.

-+https://example.com/tiki-syslog.php?months=tikiwiki&clean=Clean+-
Then land on the "Please confirm action" dialog (without knowing what we confirm ?) and execute the action.

It should not be possible to type something else than a number and the user should be warned way ahead:
"You must enter a number of month..." or something like that.

{syntax type="tiki" editor="plain"}
When I go at my Tiki logs : tiki-syslog.php I have a lot of row for different user and different actions or IP.
There is a search (filter) field to help focus on what you are looking for.

IE:
|| Id |Type |Time | User | Message | IP | Client | Actions
5861|feature|2025-10-24 12:49:24|Bernard Sfez|enabled|xxx.129.xxx.xxx|Mozilla/5.0 (Macintosh;...
5860|feature|2025-10-24 xx:49:24|Bernard Sfez|enabled|xxx.129.xxx.xxx|Mozilla/5.0 (Macintosh;...
5854|login|2025-10-24 xx:49:24|Joe Doe|enabled|xxx.xxx.xxx.xxx|Mozilla/5.0 (Macintosh;...
5847|feature|2025-10-24 12:xx:24|Bernard Sfez|enabled|xxx.129.xxx.xxx|Mozilla/5.0 (Macintosh;...
5844|feature|2025-10-24 12:xx:24|Bernard Sfez|disable|xxx.129.xxx.xxx|Mozilla/5.0 (Macintosh;...
||

__Searching for a user__, I have a tons of "Bernard Sfez" however when I search for it I find only 2.
2 that I have "Bernard Sfez" in the Message field.

__Searching for a Type__, for exemple "login" it seems correct (login type for login and logout actions)

__Searching for an IP, no results, it doesn't work.

__Searching for a term in the message__, for exemple "disabled" it seems correct.

So Type and Message seems to be filtered but not User or IP 2 critical information to track the behavior of a specific user or track using an IP address.

It would be nice to have this two searchable.

{syntax type=tiki}
{syntax type="tiki" editor="plain"}
This is the ((Tracking system for Tiki issues)).
If this is your first time, please read: ((How to Submit a new item on the Wishlist))

tiki-syslog.php has a lot of useful info.

Sometimes, two actions happen on the same minute but the order is important (ex.: LDAP error messages)

Thus, sorting by actionid_desc is better than lastModif_desc

Thanks!

There are two mysqldump commands in the Tiki ecosystem:
https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trim/scripts/tiki/backup_database.php
https://sourceforge.net/p/tikiwiki/code/HEAD/tree/trunk/lib/core/Tiki/Command/BackupDBCommand.php

On a very large site, it can take quite some time from the start of the backup to the end. What happens if some data changes during this time? Could there be data inconsistency? Should we do anything to improve what we have?

There was a revamp of ((URL Rewriting Revamp)) in Tiki11, but after the revamp, we found edge cases.

Adding them to logs would be easy and make sure we find anything left.

Also, things like http://dev.tiki.org/abcdef.php should
* offer a nice error message
* be logged so we know about broken links
* Offer a search box (if search is activated) with content of the URL in it?

So we know which admin created a login...


We currently have a log entry when a user is assigned to a group, but not when he is unassigned.

Also, we have:
unassigned perm tiki_p_broadcast from group admin

but not:
assigned perm tiki_p_broadcast from group admin



Maybe adding failed login attempts would be good too...

((doc:Trackers)) are powerful. But there is no built-in version history like the wiki pages and the spreadsheet. A workaround is to watch the tracker and have the history in your inbox. You can also permit users to comment the tracker item instead of editing it.

A real history, accessible via the interface would be nice to have. Please see SourceForge trackers for an example.

Adding a field "Edit Summary" would be useful for this history.

Low-hanging fruit solution is to copy the diffs (that we already send by email but should be improved: [wish1982|Trackers :: email notifications of changes :: more emphasis on changes.]) to a new "history" tab.

More work would be an interface to revert to a previous value, which could be nice-to-have but too complex.

Related:
[wish953|Tracker field type: wiki page]

Please see ((WikiBlame)) and ((WikiTrust))