WordPress.org

Ready to get started?Download WordPress

Forums

WP-DBManager
[resolved] Please add changelog to the Changelog page (7 posts)

  1. GermanKiwi
    Member
    Posted 3 months ago #

    Hi Lester, could you kindly add the full changelog of your plugin to the Changelog page at http://wordpress.org/plugins/wp-dbmanager/changelog/ for us please?

    It's very helpful, if not essential, for us to be able to see what has changed from version to version there on that page - especially as WordPress automatically displays the content of that Changelog page when you click the 'View Details' link on the Plugins page and the Dashboard Updates page in your site back-end.

    Thanks!

    https://wordpress.org/plugins/wp-dbmanager/

  2. Lester Chan
    Member
    Plugin Author

    Posted 3 months ago #

    Hey There,

    It is my bad, the markup is wrong, it went to other notes http://wordpress.org/plugins/wp-dbmanager/other_notes/. I will fix it

    EDIT: Fixed https://wordpress.org/plugins/wp-dbmanager/changelog/

  3. GermanKiwi
    Member
    Posted 3 months ago #

    Ah, so it did - I didn't see it there.

    Thanks for fixing! :)

  4. toggerybob
    Member
    Posted 3 months ago #

    I assume this is related to the following warning from WordFence: Wordfence found the following new issues on "Cimarron Development".

    Alert generated at Friday 18th of April 2014 at 10:25:19 AM

    Warnings:

    * Modified plugin file: wp-content/plugins/wp-dbmanager/readme.txt
    ------------
    I really love your plugin, I do, but would you mind terribly to start using the WP update process to modify/update your plugin. When you don't, those of us that are running viable security applications get a TON of alarms on our sites when authors update this plugin remotely using what I am guessing is an executable script within your plugin.

    Many, many thanks for all you do!

  5. GermanKiwi
    Member
    Posted 3 months ago #

    @toggerybob, the error you're seeing from Wordfence (which I use myself) is unrelated to the topic in this thread. Also, this plugin does already use the standard WP update process for updating itself via the WordPress repository.

    The error you've received is caused by Wordfence's settings. You have enabled the Wordfence option "Scan plugin files against repository versions for changes" which causes Wordfence to trigger an alert even when the readme.txt file in the plugin repository is changed by a single character. This is overzealousness on the part of Wordfence, and it's not an indication of the DBManager plugin developer doing anything wrong.

    In short: plugin developers like Lester often need to update their readme.txt file to make a small and insignificant change to it - eg. to correct a typo, or to add support for the latest version of WordPress - but where the plugin code itself has not been modified at all - for that reason, it doesn't warrent releasing a new version of the plugin. Only the readme.txt file has changed. However, Wordfence detects this change and issues an "alert" for it, which makes it sound like something bad.

    You can either ignore the alert from Wordfence, or you could perhaps add "readme.txt" to the Wordfence option called "Exclude files from scan that match these wildcard patterns".

  6. Lester Chan
    Member
    Plugin Author

    Posted 3 months ago #

    Wow thanks GermanKiwi for the explanation. I really appreciate it =)

  7. GermanKiwi
    Member
    Posted 3 months ago #

    No prob! :)

Reply

You must log in to post.

About this Plugin

About this Topic

Tags

No tags yet.