No Code Attached Yet Information Required
avatar isidrobaq
isidrobaq
23 Dec 2021

After upgrading to Joomla! 3.10.3, banner component started logging every individual impression and click, instead of logging hourly impressions/clicks.

Steps to reproduce the issue

Publish a banner on the frontend
Enable "Track impressions" in Banner component settings
Navigate through the frontend for a while, so the banner is loaded a few times
Check Banner Tracks in Banner Component

Expected result

A single log per hour for each banner should be displayed in Banner tracks view.

Actual result

Several logs per hour are shown for each banner (check attached image). This causes _banner_tracks table to grow insanely fast (nearly 3 million records in barely 3 weeks), and make banner component hard to manage.

System information (as much as possible)

mysql - 5.6.40 - utf8_general_ci - utf8mb4_general_ci
PHP 7.4.27
Apache
fpm-fcgi
Joomla! 3.10.4 Stable [ Daraja ] 11-December-2021 15:02 GMT
Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT

The site was upgraded from an old 3.9.18 version to 3.10.3

Additional comments

Searching for any possible solution this PR came along

#24651

Apparently this was included again in 3.10, and this comment is related to my specific issue

#24651 (comment)

Actually, this comment is what made this PR appear in my search.

avatar isidrobaq isidrobaq - open - 23 Dec 2021
avatar isidrobaq isidrobaq - change - 23 Dec 2021
Labels Removed: ?
avatar joomla-cms-bot joomla-cms-bot - change - 23 Dec 2021
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 23 Dec 2021
avatar isidrobaq
isidrobaq - comment - 27 Dec 2021

Added screenshot.

screen shot 2021-12-27 at 09 07 09


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/36375.

avatar Quy
Quy - comment - 6 Jan 2022

Can you please test PR #24651 to confirm the fix? Thanks.

avatar isidrobaq
isidrobaq - comment - 6 Jan 2022

@Quy Thanks for your reply. That PR indicates DB should be posgreSQL, which is not my case. I only mentioned it because it was related, but apparently not the same issue. Am I missing anything?

avatar Quy
Quy - comment - 6 Jan 2022

It might fix your issue so please give it a test to confirm or rule it out.

avatar Quy Quy - change - 5 Feb 2022
Labels Added: Information Required
avatar Quy Quy - labeled - 5 Feb 2022
avatar Quy
Quy - comment - 6 Feb 2022

Fixed in #24651. Tested with MySQL.

avatar Quy Quy - change - 6 Feb 2022
Status New Closed
Closed_Date 0000-00-00 00:00:00 2022-02-06 21:47:32
Closed_By Quy
avatar Quy Quy - close - 6 Feb 2022

Add a Comment

Login with GitHub to post a comment