• Resolved michaelpersch

    (@michaelpersch)


    Hello, some time after updating iThemes Security today I’ve got the following warning:

    id => 31858338
    module => file_change
    type => warning
    code => changes-found::16501,34636,0
    timestamp => 2023-07-20 21:48:32
    init_timestamp => 2023-07-20 21:48:31
    remote_ip => 87.111.111.111 (Some numbers replaced)
    user_id => [empty string]
    url => wp-cron
    memory_current => 98381656
    memory_peak => 100858096
    data => [Zu gro? zum Anzeigen]

    Thousands of files should be changed but I would have no idea why?

    “16501 added, 34636 deleted, 0 changed”

    Should I be concerned about that? All kind of files are included in this list, even htaccess files.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Support Shalom Taiwo

    (@shalomt)

    Hi @michaelpersch,

    Thank you for reaching out to us.

    Could you please check if the added/removed files are from recent backups//cache?

    Please let me know which version it was update from as well.

    Looking forward to your response.

    Best regards,
    Shalom

    Hello,
    I seem to have the same problem as @michaelpersch.
    For my part, regarding the Ithemes security update, I switched from the previous version to the new one. And I did indeed update some other plugins and clear my caches the day before the Ithemes security update. Could the file corruption be linked to my own updates?

    Regards,

    • This reply was modified 1 year, 8 months ago by therese3.

    Hi
    I also have the same problem on two of my sites since the last plugin update version 8.1.7. Affected files are due to plugin and WordPress updates as well. It would be nice if the developers of iThemes Security did not file alternately all the updates whether plugin and versions of WordPress.
    This would avoid confusion between good files and bad files, and not fill the databases with countless useless lines!
    Cordially,
    Isidore

    Plugin Support Ben Meredith

    (@benmeredithgmailcom)

    @michaelpersch @isidore1964 @therese3

    Thanks for the feedback here. With the impending rebrand to SolidWP, we’re taking a look at ways we can make things better or more useful, and this type of feedback is exactly what we need. I really appreciate it.

    Part of the problem (well, maybe “problem” is the wrong word… challenge?) of a product like a security plugin is that different hosts handle processes like updates differently. Some push updates that appear to us like totally new files, and others push updates that appear as file changes. So we have to find the path that is least confusing.

    If any of you are still having issues and want us to take a deeper look, please open a new forum post, for sure. I am marking this one as resolved, since it’s a bit old, and the notification system for these old posts makes them easy for me to miss.

    Your success and security online is our top priority!

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘File Change warning after update’ is closed to new replies.