Changed files alert AGAIN

Note that some developers do not follow the official guidelines that WordPress provides for plugin developers, and will modify a “tag” or a version of their plugin that has already been released by adding new code to an existing release – for example, fixing a bug or correcting a typo. It may be a case of a developer who is not managing their code correctly.
In this case, you can send the developer a note asking them to not check code into existing “tags” or releases.

Not sure what I am doing wrong here. If you direct me to the relevant link that could explain the correct way of doing things, would be able to figure what’s wrong.

You’ve fixed it now, as you have just released an update.
These alerts are generated by Wordfence comparing the files on my website with those in the WordPress repository. If you make changes without an accompanying release, then the files will not be in sync, hence the alert. I’m no expert, I’m just quoting what the Wordfence documentation says.

Of course, I never change files without a release. That’s the most basic thing about pushing changes for a live plugin. I know that ??
Next time WordFence send you this warning, give me the link of those CSS files at your website so that I could what changes are introduced in those files and how.

Here you go:
https://photos.app.goo.gl/1JQ2FHyHas2xwWQA7

I need url of your website to check how the CSS file there is different from that comes with the plugin. You can send it to support[at]heateor[dot]com if you don’t want to post here.

https://www.mpba.org.uk

If you compare the original CSS file in the plugin https://plugins.trac.www.ads-software.com/browser/sassy-social-share/trunk/admin/css/sassy-social-share-default-svg-vertical.css with the same CSS file at your website https://www.mpba.org.uk/wp-content/plugins/sassy-social-share/admin/css/sassy-social-share-default-svg-vertical.css, you will see there is no difference. Can you write to WordFence asking for the explanation about the warning you are receiving?

Yes, because I eventually rolled the changes back to the versions in the repository pending the next release from you. Thought you might check it a bit quicker and I wasn’t prepared to leave the potentially invalid files live.

• This reply was modified 5 years, 7 months ago by mpbaweb.
• This reply was modified 5 years, 7 months ago by mpbaweb.
• This reply was modified 5 years, 7 months ago by mpbaweb.

Sorry, but until you send me those files you received the warning for, wouldn’t be able to identify what the issue was.

Ok, here we go again. Another modified file alert:
https://photos.app.goo.gl/QbfHEThbwE8XvMfF8
https://photos.app.goo.gl/wetWLrZdMUNwQFWx8

Same 3 files again

• This reply was modified 5 years, 7 months ago by mpbaweb.

If you compare the original CSS file in the plugin https://plugins.trac.www.ads-software.com/browser/sassy-social-share/trunk/admin/css/sassy-social-share-default-svg-vertical.css with the same CSS file at your website https://www.mpba.org.uk/wp-content/plugins/sassy-social-share/admin/css/sassy-social-share-default-svg-vertical.css, you will see there is difference. Are you making any changes in the CSS files manually?

No, I am not doing anything.

I will just revert the files to the repository version I think. Life’s too short to keep worrying about this.

It’s okay. You will revert the files back. But you should check why the CSS files are different from the original files at plugin repository.