Please update readme compatability info

  • Resolved Hendrik57

    (@hendrik57)


    4 years ago

    We use “Better Plugin Compatibility Control” to allert us on plugins that are no longer maintained. That uses the info in the readme file.
    The current plugin seems to be valid up to WP 4.9. But that info is wrong. According to the plugin info it should say 5.9.3.
    Please update this file.

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author apasionados

    (@apasionados)

    4 years ago

    Hi @hendrik57,

    The readme.txt file on the SVG WordPress server is correct. You can view it here: readme.txt.
    There you can see that the plugin has been tested up to version 5.9 which is also the info WordPress shows on the plugin page: Server IP & Memory Usage Display (because WordPress get this info from the readme.txt file).

    Maybe the “Better Plugin Compatibility Control” get’s the version control from the readme.txt file of the plugin you have installed on the server. Could you try to deactivate, delete and reinstall the plugin from the repository? This should fix the version number issue.

    Let us know if this hasn’t helped.

    Best regards from Spain.

    Thread Starter Hendrik57

    (@hendrik57)

    4 years ago

    I see what happens. The plugin on all sites is dated 20-11-2020, Version: 2.1.0 it says in the dashboard. It is the same as current.

    The readme.txt says:

    Tags: memory, memory-limit, ip, ips, admin, adress, php, server, info
Requires at least: 3.0.1
Tested up to: 4.9
Requires PHP: 5.3
Stable tag: 2.1.0

    And that 4.9 is used to verify compatability with the WordPress release.

    The header of the installed 2.1.0 version says:

    Plugin Name: Server IP & Memory Usage Display
Plugin URI: http://apasionados.es/#utm_source=wpadmin&utm_medium=plugin&utm_campaign=server-ip-memory-usage-plugin
Description: Show the memory limit, current memory usage and IP address in the admin footer.
Version: 2.1.0
Author: Apasionados, Apasionados del Marketing
Author URI: http://apasionados.es
Text Domain: server-ip-memory-usage

    But indeed. The download version 2.1.0 has a language folder and a correct readme.txt file. That is not the same 2.1.0 release!

    I wil replace all instances. How this could have hapenend?

    • This reply was modified 4 years ago by Hendrik57. Reason: correct now
    • This reply was modified 4 years ago by Hendrik57.
    Plugin Author apasionados

    (@apasionados)

    4 years ago

    Hi @hendrik57,

    We think that this has to do with the WordPress Plugin Directory policy to update the readme.txt file to reflect compatibility with new WordPress versions and commit this change not releasing a new version of the plugin.

    This is the official instruction:

    For each compatible plugin, you do not need to release a new version — simply update the stable version’s “Tested up to” value to 6.0 in your readme file.

    Plugin version remains the same and only readme.txt file is updated. We think that this cpuld be the problem here.

    Best regards from Spain.

    Thread Starter Hendrik57

    (@hendrik57)

    4 years ago

    Strange, because updates are as far as I know always initiated by a new and higher version number. I’ve not seen that individual plugin files are updated.
    I think that ‘official instruction’ is wrong. It doesn’t work that way as I’ve proven for > 60 sites.
    I your case, I’d create a 2.1.1 version, or a 2.1.0.1 release to force the updates.

    As far as I understand the ‘official instruction’ is only used for the notice displayed on the WordPress.org plugin page noting that the plugin may no longer be maintained or supported. The readme is not used in the update signalisation process.

    Plugin Author apasionados

    (@apasionados)

    4 years ago

    Hi @hendrik57,

    As we understand, now it’s against the rules to raise plugin version to reflect compatibility. Nevertheless we will seek for clarification.

    Best regards from Spain.

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

The topic ‘Please update readme compatability info’ is closed to new replies.