• Resolved Tom

    (@esilverstrike)


    Thanks for creating the plugin!

    I have a feature request. I plan on using this plugin on most of my sites and don’t want to go in after plugin updates and mark file changes for the specific plugin. This will take a lot of time.

    Is there a way after WordPress, theme, or plugin is updated File Monitor can re-scan the its directory and use that as the new base line for file changes?

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

    (@lucianwpwhite)

    Hello there @esilverstrike !

    Thank you for reaching out today!

    From what I understand, and correctly me if I am wrong but you would like to exclude certain folders from being part of the scan is that correct? e.g. certain plugins. If that’s the case, this is something our plugin is already designed to do and you can read more about how to do so here where everything is explained in detail.

    I really hope this helps, and let me know if you have additional questions!

    Thread Starter Tom

    (@esilverstrike)

    Yup I saw that feature but it’s not exactly what I am talking about.

    I want plugin files to be monitored at all times in case of a hack etc…

    What I want is a feature that allows plugins to be updated by certain users (or User Roles or if it happens through something like MainWP) and File Monitor will not report these file changes since they are tied to a plugin update by an appropriate user account. It’s understood that file changes will happen here and they should be ignored just in this case. Of course if file changes happen by some other means then they need to be reported.

    I maintain a large number of websites and it’s time consuming after legitimate plugin updates to go into each website and mark these type of events as read.

    Does that make sense?

    Plugin Support Lucian Padureanu

    (@lucianwpwhite)

    Hello there @esilverstrike !

    Thank you for clarifying, that makes perfect sense now! To be honest, this goes beyond what the plugin currently supports, but we have taken note of it and it will definitely be part of our future brainstorming sessions as we think about how to make File Monitor more practical for power users and agencies like yourself.

    Thanks again for the detailed explanation and for taking the time to share this – feedback like this is genuinely useful for shaping where the plugin goes next!

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.