Support » Plugin: Shortcodes Ultimate » Wordfence Notice on 5.4.1

  • Resolved tjalexander70

    (@tjalexander70)


    Today, I received a Wordfence notice that 4 files in my installation do not match the files in the repository. Those are…

    • wp-content/plugins/shortcodes-ultimate/admin/class-shortcodes-ultimate-admin.php
    • wp-content/plugins/shortcodes-ultimate/admin/partials/pages/shortcodes-list.php
    • wp-content/plugins/shortcodes-ultimate/includes/functions-helpers.php
    • wp-content/plugins/shortcodes-ultimate/admin/class-shortcodes-ultimate-admin-shortcodes.php

    The notice is…

    This file belongs to plugin “Shortcodes Ultimate” version “5.4.1” 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]

    An example from wp-content/plugins/shortcodes-ultimate/admin/class-shortcodes-ultimate-admin-shortcodes.php is…

    line 93 of the “original” is public function get_shortcode_code( $args ) {

    line 93 of my file is protected function get_shortcode_code( $args ) {

    line 185 of the “original” is public function get_available_shortcodes() {

    line 185 of my file is protected function get_available_shortcodes() {

    It goes on from there.

    Should I keep what I have or switch to what is shown to be in the WordPress repository?

    • This topic was modified 2 months, 3 weeks ago by tjalexander70.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Same here.

    I updated from v5.3.0 => v5.4.1 on 26 August 19 and today it gives me this notice.

    On the plugin development tab it says the plugin was just (13 minutes ago). Has that been done without changing the version number?

    Plugin Author Vladimir

    (@gn_themes)

    I’ve added some minor changes to the plugin (a few times), but didn’t changed the version number to not bother users with daily updates. That’s why the repo version differ from yours.

    Just reinstall the plugin from within dashboard.

    You should never change and publish something without changing the version number.

    Agree with jpnl. There are millions of Wordfence users, and every one of them who also uses your plugin is now having to take the time to research this and figure out if it’s a real issue. Or if they are less tech savvy and simply delete the apparently infected files, it could severely and irretrievably impact their websites. There are procedures for a reason. What saves you a few minutes can cost countless hours, headaches and expenses for end users.

    Sorry but need to add my 2 cents worth. I’ve lost time trying to see if this is a problem. Could you please update the version number on future updates? It would have saved me time this go-round. Thanks.

    • This reply was modified 2 months, 2 weeks ago by daphnetalbot.
Viewing 5 replies - 1 through 5 (of 5 total)
  • You must be logged in to reply to this topic.