Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter Gal Baras

    (@galbaras)

    I see what the problem is. The plugin is scanning readme.txt files on the local server, but compatibility information is changed on the plugin repository without releasing a new version.

    This means a lot of work checking plugins in the repo manually.

    Can you please get the information from the authoritative source, instead of local files?

    I have the same problem, or rather I was wondering about it too. Your explanation makes sense, querying the “tested up to”-parameter over the official API would be best.

    The parameters ‘compatibility’ and/or ‘tested’ look good there
    https://developer.www.ads-software.com/reference/functions/plugins_api/

    • This reply was modified 3 years, 8 months ago by napster2k19.

    Same here!
    Please fix ASAP!
    Thanks!

    Hi again!
    Is this plugin still maintained?
    In the meantime I thought about this issue a bit deeper.
    To me it seems as if the intention of the developer was to display the compatibility information not on the latest version, but on the installed version of a plugin – which is an important information, too.
    If this is true (is it?), it indeed makes sense to scan the readme.txt files on the local server.
    Nevertheless this plugin is lacking of the very important information on the compatibility of the latest available version of a plugin with – to fully know “at a glance if a plugin is compatible with the current WP version” (quotation from the plugin description). This even would point out, whether the latest versions of all plugins would be compatible with a newer available WP version than the one currently being installed.
    So, dear Oliver, could you please make also the second half way to the designated meaning of you plugin, showing also the compatibility of the latest available plugin version?
    Thank you very much in advance!
    Kind regards,
    Gerald

    Thread Starter Gal Baras

    (@galbaras)

    The compatibility is with the WordPress core version, and that is sometimes stated differently in the repository and the readme file, with the repository being more up-to-date > authoritative.

    It’s a good idea to show the latest update information when that’s not the version on the website, because this helps plan things that may not be possible now due to dependencies. I haven’t been in this situation, so not sure what the plugin does now, but if that’s not a feature, it’ll be good to have.

    Hi Oliver!
    Do you still maintain your plugin or not?

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Incorrect maximum version listed’ is closed to new replies.