Extension Installer V2 (5 Viewers)

[seco]

I think MPEI really needs to have a feature where it checks that update files are really update XML files and not binary or other (perhaps) large files.

See https://forum.team-mediaportal.com/threads/mp-extension-installer-large-update.113009/#post-923983

 

[infinite.loop]

I think MPEI really needs to have a feature where it checks that update files are really update XML files and not binary or other (perhaps) large files.

See https://forum.team-mediaportal.com/threads/mp-extension-installer-large-update.113009/#post-923983

Actually I have been working on a document that means more a less a complete rewrite of MPEI and major changes to the repository and MP itselfe to allow installation/upgrades inside the MPUI without running into UAC.

Trouble I have is to find dedicated developers willing to do that.

 

[seco]

I think MPEI really needs to have a feature where it checks that update files are really update XML files and not binary or other (perhaps) large files.

See https://forum.team-mediaportal.com/threads/mp-extension-installer-large-update.113009/#post-923983

Actually I have been working on a document that means more a less a complete rewrite of MPEI and major changes to the repository and MP itselfe to allow installation/upgrades inside the MPUI without running into UAC.

Trouble I have is to find dedicated developers willing to do that.

Sounds interesting. Is this document available anywhere for developer review & comments?

 

[infinite.loop]

I think MPEI really needs to have a feature where it checks that update files are really update XML files and not binary or other (perhaps) large files.

See https://forum.team-mediaportal.com/threads/mp-extension-installer-large-update.113009/#post-923983

Actually I have been working on a document that means more a less a complete rewrite of MPEI and major changes to the repository and MP itselfe to allow installation/upgrades inside the MPUI without running into UAC.

Trouble I have is to find dedicated developers willing to do that.

Sounds interesting. Is this document available anywhere for developer review & comments?

Not yet. I need to polish it a bit further.

I will then move it to the wiki and have a news article about that idea - calling for interested developers in the community.

 

[seco]

Does anyone know how installing old versions of MPEI packages should work with Extension Installer? I'm asking because a user had a problem installing Rockstar 2.1.7 where 2.2 is the latest version.

I tested this myself and when I choose older version (2.1.7) from installer it actually tries to install 2.2. In a way this makes sense since the download link I use always points to latest version (here 2.2) and the older version is not available anymore so there is no place where Extension Installer could download 2.1.7 unless it is cached somewhere in MediaPortal servers.

Does this only work when download link is unique per plugin version? Should installation be aborted & user notified if the actual version he is trying to install is not available?

@offbyone ?

 

[seco]

Ok, I'm blind. The installer already warns the user if downloaded version is different than user selected.

 

[kesar]

Ok, I'm blind. The installer already warns the user if downloaded version is different than user selected.

Sorry, seco but it's not completely true. From my side it looks like this: I update plugin list and then, since I have show compatible versions only, I should see a list of Rockstar versions untill 2.1.8, right? Unfortunately I see full list including 2.2.0 (without 2.1.8) which is weird cause 2.2 isn't compatible with my MP 1.2.3. So when I try to install any (I mean any of those) version of the plugin, I get dependency error, which I described in another topic. I don't get any kind of warning.

 

[offbyone]

If you have a static link to the mpe file and always update the filew "behnd" that link - MPE Installer tool cannot know that - it thinks it downloads an older version but actually gets a newer - and should warn at install.
In this scenario, only way to install an old version is by explicitly opening a mpe file with double clicking in explorer.

 

[seco]

Sorry, seco but it's not completely true. From my side it looks like this: I update plugin list and then, since I have show compatible versions only, I should see a list of Rockstar versions untill 2.1.8, right? Unfortunately I see full list including 2.2.0 (without 2.1.8) which is weird cause 2.2 isn't compatible with my MP 1.2.3. So when I try to install any (I mean any of those) version of the plugin, I get dependency error, which I described in another topic. I don't get any kind of warning.

Well, yes and no. I've now tested this with both MP 1.2.3 and MP 1.3.0.

For both applies what offbyone said above:

The version that is actually installed is the version where download link points to, for Rockstar always latest, in this case 2.2, no matter what you select in Extension installer.

MP 1.2.3

I don't know why 2.2 is listed since I guess it should not be. But even if you select 2.1.7 it downloads 2.2 like I said above. Since 2.2 is not compatible with MP 1.2.3 you get "DEPENDENCY CHECK ERROR". Sad thing here is that nothing says that 2.2 is actually trying to be installed.

MP 1.3.0

Again, if you select 2.1.7 still 2.2 is downloaded. However now the installer warns the user that the downloaded version is not what user selected.

 

[kesar]

The version that is actually installed is the version where download link points to, for Rockstar always latest, in this case 2.2, no matter what you select in Extension installer.

Ok, I get it, although I don't see any logic in this. Why post all version numbers when all point to the same file? Doesn't make sense to me. Not mentioning the incompatible ones, which might be selected for install. MPEI seems flawed a little.