Reply to thread

Message: <blockquote data-quote="Dadeo" data-source="post: 994948" data-attributes="member: 27204">On another note, before I forget, you mentioned wanting feedback from extension devs. I am not an expert, but I do use MPEI for aMPed skin and help Guzzi with My Films, and as Docs Mgr I have received MANY questions via forum and PMs from various extension devs confused about MPEI. In my experience the two biggest issues are:<ol> <li data-xf-list-type="ol">Publishing your extension - currently there is a separate process to actually submit your extension (which adds it to <a href="http://install.team-mediaportal.com/MPEI/extensions.txt" target="_blank">http://install.team-mediaportal.com/MPEI/extensions.txt</a>) which is hideous because it does not remove old extensions, remove duplicates, etc. etc. Many times devs do not understand why their package does not display in MPEI for users.</li> <li data-xf-list-type="ol">Compatibility - extensions often retain previous versions for compatibility with previous versions of MP because not all users update right away. Currently when you create a new update.xml in MPE Maker it just adds the new extension and keeps the old listings, even though the links may no longer work! There is no easy way to 'choose' which versions to keep other than manually editing the update.xml which is less than desirable imo. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" /> If you delete the update.xml and start fresh, you lose all the previous versions. As a result, some extensions just use a new update.xml (in a new location or with a new name) for each version - hence some of the duplication you will see in extensions.txt.</li> </ol>I realize you are planning a whole new process which will hopefully avoid these and other issues. But I wanted to give you the feedback just in case it is relevant.</blockquote>

Verification