Using “_occasionsID” does not group the logs, they still show separately

Hello.

I wanted to follow up on this issue.

Any clues?

Thank you in advance.

Hey @ckaklamanos, I’m on vacation at the moment, but will take a look at this next week when I’m back.

@ckaklamanos What database server and version are you using on the website where it’s not working? MySQL or MariaDB? I have a theory that it may be related to some combination for server and version..

Hello and thank you very much for getting back.

Here is the information from WordPress health screen:

Database
Extension mysqli
Server version 10.3.35-MariaDB-1:10.3.35+maria~focal-log
Database collation utf8mb4_general_ci

Server
Web server Apache/2.4.41 (Ubuntu)
PHP version 8.0.26 (Supports 64bit values)

Thank you in avdance.

How do you add your entries to the log?

I did test this now, on both MySQL and MariaDB and it did work:

    $context = array(
        '_occasionsID' => 'my_custom_occasions_id',
    );

    // First occasion.
    SimpleLogger()->notice(
        'Custom message with custom occasions notice 1',
        $context
    );

    SimpleLogger()->notice(
        'Custom message with custom occasions, notice 2',
        $context
    );

In the history feed the above works and only the first message is shown for me, with an option to expand to show the second message.

Hello and again, thanks for getting back.

This is how I always do it, with the filter:

    // Simple History
    apply_filters(
        'simple_history_log',
        'XYZ: WP Cron Completed',
        [
            '_occasionsID' => 'xyz_wp_cron_completed_log',
        ],
        'debug'
    );

I am using the above filter in order to log the “WP Cron completed” task.

Also, I am running the above filter inside an MU plugin. However, this should not be relevant, because I have the same issue with using the same filter inside a standard plugin.

Thank you.

I just tried your code and it worked perfectly. I called it 10 times and this was the result:

Is there nothing else being logged between your cron events, like a user logging in or a post being edited or something? For the grouping to work there can’t be anything else being logged between.

Hello.

It looks like you are right. I was not aware of that.

Indeed, there are various log entries that are inserted in the time between the cron logs.

Thanks for help me with this and sorry for the misunderstanding of how this works.

No worries, just happy that we found out what was the cause of this.