Pro Feature Missing – Detailed Download Log / Reporting No Longer Accessible

Posted by: TEFL

23rd February 2026, 12:06 pm

TEFL

@TEFL

23 Feb 2026
12:06 pm

Hi there,

We are Pro users of Free Downloads WooCommerce and recently updated to the latest version. Since updating, the detailed downloadable log table that previously allowed searching and filtering by customer email is no longer accessible in the admin interface.

Your feature description for Pro includes:

“Download tracking with reporting: Keep a record of every free download showing the product, variation (if applicable), date, user, email address and IP address.”
While we can see that tracking is still enabled and recent downloads are being recorded, the ability to:

Search by customer email
Filter by product
View a full download history per user
Monitor high-volume downloading activity directly in the dashboard
appears to have been removed.

For our site (64,000+ free members), this functionality is essential. We regularly use the detailed log view to:

Investigate customer support queries and refund cases
Monitor excessive downloading or potential abuse
Check compliance with download limits
Identify unusual activity patterns
Exporting CSV files is not a practical replacement for real-time searchable reporting within WordPress admin.

Could you please clarify:

Has the detailed searchable log view been moved to another location in the new version?
If it has been removed, is this temporary?
Is there a plan to restore full reporting access for Pro users in an upcoming update?
This feature was a key reason for choosing and renewing the Pro version, so we would appreciate clarification on how Pro users are now expected to access detailed reporting.

Thank you for your assistance, and we look forward to your response.

Kind regards,
Wendy Morris
TEFL Lessons

Last modified: 23rd February 2026, 9:54 pm by Peter Wilkinson

  • Forum Moderator
    Peter Wilkinson

    @wpenhanced

    23 Feb 2026
    9:56 pm

    Hi Wendy

    Thanks for the message - this was an oversight on us, we forgot to do it.

    I have implemented it and released it - please update to 3.6.1 and let me know

    It will look like this