Simple Membership Plugin › Forums › Simple Membership Plugin › Severity Warning for Simple Membersip
- This topic has 1 reply, 2 voices, and was last updated 10 years, 9 months ago by
mbrsolution.
-
AuthorPosts
-
December 8, 2015 at 8:45 pm #4406
sunnyday
ParticipantHi,
I haven’t done anything yet about these 2 warnings I rec’d today. Waiting to hear back from you.
Thanks!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~SEVERITY ISSUE
Modified plugin file: wp-content/plugins/simple-membership/log.txt
Filename: wp-content/plugins/simple-membership/log.txt
File type: Plugin
Issue first detected: 17 hours 27 mins ago.
Severity: Warning
Status New
This file belongs to plugin “Simple WordPress Membership” version “3.1.4” and has been modified from the file that is distributed by WordPress.org for this version. Please use the link to see how the file has changed. If you have modified this file yourself, you can safely ignore this warning. If you see a lot of changed files in a plugin that have been made by the author, then try uninstalling and reinstalling the plugin to force an upgrade. Doing this is a workaround for plugin authors who don’t manage their code correctly. [See our FAQ on http://www.wordfence.com for more info]
Tools:View the file. Restore the original version of this file. See how the file has changed.
Select for bulk repair
Resolve:I have fixed this issue Ignore until the file changes. Always ignore this file.Modified plugin file: wp-content/plugins/simple-membership/log-auth.txt
Filename: wp-content/plugins/simple-membership/log-auth.txt
File type: Plugin
Issue first detected: 17 hours 27 mins ago.
Severity: Warning
Status New
This file belongs to plugin “Simple WordPress Membership” version “3.1.4” and has been modified from the file that is distributed by WordPress.org for this version. Please use the link to see how the file has changed. If you have modified this file yourself, you can safely ignore this warning. If you see a lot of changed files in a plugin that have been made by the author, then try uninstalling and reinstalling the plugin to force an upgrade. Doing this is a workaround for plugin authors who don’t manage their code correctly. [See our FAQ on http://www.wordfence.com for more info]
Tools:View the file. Restore the original version of this file. See how the file has changed.
Select for bulk repair
Resolve:I have fixed this issue Ignore until the file changes. Always ignore this file.December 8, 2015 at 10:49 pm #4415mbrsolution
ModeratorHi, did you receive these warnings using wordfence security plugin? Did you update the plugin at any time before these warnings?
-
AuthorPosts
- You must be logged in to reply to this topic.