• WP Activity Log appeared to record the previous Divi version (5.12.1) as the “new version” after WordPress successfully auto-updated the theme to 5.13. I’ve attached screenshots showing the incorrect activity-log entry and the actual installed theme version.

    Steps to Reproduce

    1. Install and activate a theme with an available update. In my case, I was on Divi 5.12.1, and then Divi 5.13 became available.
    2. Enable WordPress automatic updates for the theme.
    3. Allow WordPress to perform its normal scheduled automatic update.
    4. After the update completes, check WP Activity Log Event 5031 — “User updated a theme.”
    5. Compare the version reported by Event 5031 with the version actually installed.

    Expected Result: New version in the text shows the new version, 5.13 in my case

    Actual Result: New version shows the OLD version, 5.12.1 in my case

    I also verified the installed version independently with WP-CLI:

    wp theme get Divi --field=version

    which returns:

    5.13

    The Event 5031 “More details” data contains:

    Theme:
    Name: Divi
    Version: 5.12.1
    
    ThemeStatus: Active
    Object: theme
    EventType: updated
    UserAgent: WordPress/6.9.7; [site URL]
    Username: Unknown User

    • WordPress: 6.9.7
    • WP Activity Log: 5.6.6
    • Theme: Updated to Divi 5.13
    • Theme auto-updates: Enabled in WordPress

    Additional context / possible cause — AI generated

    I investigated this with AI assistance, and it may be related to theme metadata caching during automatic updates.

    Event 5031 reads the updated theme version using wp_get_theme() during upgrader_process_complete. WordPress automatic theme updates use clear_update_cache => false, so it seems possible that WP Activity Log may be reading the cached pre-update theme version before WordPress refreshes the theme cache.

    That could explain why Event 5031 recorded 5.12.1, while the installed theme and subsequent checks report 5.13.

    Are you able to take a look and advise?

Viewing 1 replies (of 1 total)
  • Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello there @sfgiantswporg!

    Thank you for reporting this!

    I’ve opened an internal ticket with our development team, and we’ll run some tests to see if we can reproduce the issue and determine whether there’s anything we can tweak on our side.

    If there’s anything else you’d like to add, please feel free to do so. We’ll definitely take your feedback into consideration when working on the next maintenance update of the plugin.

    Many thanks!

Viewing 1 replies (of 1 total)

You must be logged in to reply to this topic.