Update Sourceforge links in Extensions list (1 Viewer)

[Edalex]

Hi!
In file MPEI Installer is using for getting update info (http://install.team-mediaportal.com/MPEI/extensions.txt)
we have many links like http://mp-plugins.svn.sourceforge.n...k/plugins/File Explorer/MpeRelease/update.xml
Calling such link will result in HTTP 302 redirect to main repo page not actual xml file.
Changing link to http://svn.code.sf.net/p/mp-plugins/code/trunk/plugins/File Explorer/MpeRelease/update.xml fixes the problem.
So it is possible to batch replace mp-plugins.svn.sourceforge.net/viewvc/mp-plugins with svn.code.sf.net/p/mp-plugins/code?
@high @Dadeo ?
Thanks!
P.s. and a personal request: changing http://mediaportal-russian-logos.googlecode.com/svn/trunk/LogosManager/LogosManager/update.xml to http://mediaportal-russian-logos.googlecode.com/svn/trunk/LogoManager/LogoManager/update.xml

 

[high]

thanks for reporting, replaced a few old ones and changed russian logos

 

[BassFan]

missing ..
Audio Vis Package in to extensions.txt
is necessary for 1.6 Final..

i can only load on the Homepage under plugin not with MPEI Installer

greets

 

[Edalex]

In order to see anything in MPEI Installer you need to push "Publish" button in MPEI Maker first.
Did you do that?

 

[BassFan]

In order to see anything in MPEI Installer you need to push "Publish" button in MPEI Maker first.
Did you do that?

no.. sorry which URL is required before push the Publish Button?

greets

 

[Edalex]

http://wiki.team-mediaportal.com/1_...s/Extensions_Installer/Publish_your_Extension

 

[BassFan]

http://wiki.team-mediaportal.com/1_...s/Extensions_Installer/Publish_your_Extension

Visualisation Packages is listening and now? and added by @hwahrmann
Should add this link to the Urllist for published button?


greets

 

[Edalex]

Hi again.
Updating sourceforge link was not enough since I found out that MPEI is not able to replace update urls with new ones if they changed. So I started to make patch which will do this for local packages. But I encountered that update url in Extensions.txt could be not unique which will make my efforts completely useless if I update pack with bad old links. So here is the list of duplicate entries. I can't say for mp website links but we could analyze links to different repos. So it looks like sometimes repo is moving to another location and dev should hit plublish button for uploading new link.
What about implementing check by plugin guid existence in submit.php so plugin entry will be updated not added new one. I don't know how submitting is look like from website view ofc.
But for other cases what if plugin devs don't know about hitting "Publish" once once per plugin life?
Tagging gurus for discussion @high @Dadeo @offbyone
Thanks!

 

[Edalex]

Sorry for being annoying and tagging @high @Dadeo @offbyone again to get comments

 

[high]

sorry, forgot to answer...it should be possible to replace by ID if someone want to update the submit.php. As a workaround I can remove double IDs manualy, not that much additional work to run a quick search for IDs.
Will clean the actual txt tonight based on your list, thx.