View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0018500 | MMW 5 | Extensions framework | public | 2021-11-02 19:39 | 2024-04-08 11:57 |
| Reporter | drakinite | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | N/A |
| Status | closed | Resolution | reopened | ||
| Product Version | 5.0.2 | ||||
| Target Version | 5.0.3 | Fixed in Version | 5.0.3 | ||
| Summary | 0018500: Check for Addon Updates: Compatibility field is ignored | ||||
| Description | With multiple versions of MM5 out, new addons may depend on methods that have been added in 5.0.2+, such as getAllValues and setLessVariables. If a user hits Check for Updates and there is a new version of an addon whose Compatibility field is higher than the installed MediaMonkey version, it will still display as available and will install without notifying the user of possible incompatibility. Proposed new functionality: If a new addon version is available, but its "minimum compatible version" is higher than the currently installed MediaMonkey version, two things should occur: 1. Next to the "Update available (x.x.x)", to the left of the download button, a "⚠️" symbol should appear, with the tooltip "This addon version may be incompatible with MediaMonkey version ((installed version)). Addon is compatible with MediaMonkey version ((minimum version)) to ((maximum version))." 2. If the user downloads it anyway, in the Product Installation dialog, another warning should appear at the top, with the same message. Optionally, there could be a link to open the addon's page on the website, with the text "Find other versions here" This wouldn't help users who have MM5.0.0 and 5.0.1 installed, but it would help moving forward. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 2623 | ||||
| related to | 0013903 | feedback | jiri | MMW 5 | Extensions: MM5 Extension Tweaks |
| related to | 0018825 | resolved | drakinite | MMW 5 | Addons: There is no support for custom Update URL |
| related to | 0019062 | closed | drakinite | MMW 5 | app.utils.getApplicationVersion(3) returns four digits instead of three |
| related to | 0019832 | closed | rusty | MMW 5 | Manual Image lookup fail if search term contain spaces. |
| related to | 0019633 | resolved | peke | Addons (external) | Publish "Mark Played" addon |
| related to | 0020819 | closed | Ludek | MMW 5 | Addons: Add maxAppVersion compatibility field |
|
|
I think that there could be just indication of minimum version and the install shouldn't be possible at all (if the minimum version is higher than current MM5 version). Assigning to Rusty as it requires new strings to include/review before translation. |
|
|
Strings: 1. "Update available (x.x.x)". I suppose you're referring to the existing "Update available" string? 2. Suggested Tooltip/Full warning message strings: String 1: This update is compatible with %%. String 2: The addon may not work correctly with %%. e.g. This update is compatible with MediaMonkey 5.2-5.9. The addon may not work correctly with MediaMonkey 5.1. Re.: "Find other versions here", couldn't we just make addons that appear on the site hyperlinked? |
|
|
1. Yep. Re hyperlinking: That *could* be possible, but I think that would require quite a bit of extra coding (To my knowledge, there's no way of determining whether an addon came from the site without pinging the addons API.) Alternatively: If we put the hyperlink close to the version warning, we could get away with "Choose alternate". (It would have to be physically close to the warning, such as in the same line, so that the user understands the context.) Does that sound ok? |
|
|
Sounds good. |
|
|
As discussed offline, currently the addon's site does not return the minimum supported version although the addon's submitter fills this info. e.g. https://www.mediamonkey.com/addons/update.php?id=refreshSkinShortcut returns just XML with the addon's version. i.e. the minimum supported MM version needs to be added Assigned to Jiri to add this info. EDIT1: I still believe that the minimum compatible MM version should be also part of the MMIP itself. For the cases when someone installs the update manually from the downloaded MMIP EDIT2: The code with these two new strings is backed up in SVN: 'This addon is incompatible with current version of MediaMonkey' 'Please update to MediaMonkey %s or higher.' |
|
|
Assigned back to me to support minAppVersion in info.json for 5.0.2 To be assigned back to Jiri for the server site support (post 5.0.3) |
|
|
Fixed in 2516. i.e. - added minAppVersion support in info.json (part of MMIP) and added it to all scripts from the SampleScripts folder - added minAppVersion support for both XML and JSON variant of the updateURL info i.e. in case of https://www.mediamonkey.com/addons/update.php?id=refreshSkinShortcut the XML should look like <VersionMajor>1</VersionMajor> <VersionMinor>0</VersionMinor> <VersionRelease>2</VersionRelease> <VersionBuild>0</VersionBuild> <MinAppVersion>5.0.2</MinAppVersion> in case of JSON the JSON should look like: { "version": "1.0.2", "minAppVersion": "5.0.2" } The format can be either "5.0.2" or "5.0.2.2513" |
|
|
Verified 2516 Please triage for further progress by @jiri |
|
|
OK, so assigned to Jiri to implement the server side. |
|
|
Fixed, update.php now returns <minAppVersion>. |
|
|
The "Please update to MediaMonkey %s or higher." field currently displays "Please update to MediaMonkey or higher." instead of the appropriate minAppVersion string. |
|
|
Fixed in 2623. |
|
|
Verified 2624 |
